ClearPath Hours
Security overview

How ClearPath protects your records.

ClearPath Hours keeps the records that pre-licensure clinicians submit to state boards. This page explains, in plain language, how we protect those records, which outside services we use, what we do not claim, and how to reach us if you find a security issue.

TLS in transit, AES-256 at restRow-level security on every workspace tableExplicit supervisor relationships, no shared workspacesNo advertising tag on your records

Plain-language summary

Sign-in, encryption and records locked to your account.

Every record in ClearPath is protected by Postgres row-level security tied to the signed-in user. Data is encrypted with TLS in transit and AES-256 at rest. The supervisor flow grants exactly the access the clinician approved, and nothing else. Our advertising tag runs on our public pages and on the sign-up and password reset pages. In the app it loads only to count a first hour or an upgrade to Pro, and it never runs on the pages that hold your records. If you are checking ClearPath against an employer or program requirement, this is the page to share.

Please note

ClearPath does not give clinical, legal or licensing advice.

ClearPath helps you keep your hours, check them against your state's rules and prepare the forms your board asks for. Decisions about your license, and what you submit to your board, stay with you, your supervisor and your state board.

Questions about this page can go to support@clearpathhours.com.

Authentication & Account Access

ClearPath uses Supabase Auth for sign-in. Passwords are hashed with bcrypt-class algorithms server-side; the cleartext value never reaches the application database. Your session is kept in cookies holding a signed access token (a JWT) that expires and is renewed while you stay signed in. Signing out ends your sessions on every device and clears the cookies in this browser. An access token issued before then stays valid until it expires. Email confirmation is required on signup, and password resets land at a single-use link that expires.

You can delete your account yourself in Settings, under Account, or by writing to support@clearpathhours.com. Deletion happens right away: it cancels any paid subscription, then removes your records, any files you uploaded and your sign-in. Stripe keeps its record of your past payments and invoices, and backups age out on the standard cloud-vendor schedule.

Encryption

All traffic to clearpathhours.com is served over TLS 1.2+, and the site tells browsers to connect to it only over HTTPS (HSTS). Data at rest in Supabase Postgres is encrypted with AES-256, and so are Supabase's scheduled backups. The same applies to files you upload, such as a copy of a signed log. Filled board forms and exports are created when you ask for them and are not stored.

Calls between our services (Vercel and Supabase, Stripe webhooks, Resend email) use TLS the whole way. Our logs keep what we need to run them, such as whether a call worked and the IDs involved, not the records or emails they carry. When a call fails, the error we log can include part of what was sent, such as a value the database refused.

Authorization (Row-Level Security)

Every workspace table in ClearPath has Postgres row-level security policies that restrict reads and writes to the authenticated user who owns the row, plus the explicitly-granted supervisor relationships they accept. Cross-user reads only happen through the supervisor flow: when a supervisor accepts an invitation, a relationship row is created that grants them visibility into the supervisee's submitted hours and nothing else.

Server routes that need to bypass RLS (admin self-heal, supervisor accept) use a separately-scoped service-role connection and pass the validated authenticated user id from the session to every write. The service-role key never reaches the browser.

Clinical Privacy

ClearPath is an hour-tracking and licensure-evidence product, not a clinical record system. We strongly encourage clinicians to log hours without identifiable client information, and the entry forms are structured around session metadata (date, duration, category, setting type) rather than clinical content.

We do not currently hold a formal HIPAA certification and we do not market ClearPath as a HIPAA-covered platform. If your employer or supervisor program requires a Business Associate Agreement, please contact us at support@clearpathhours.com before signing up so we can confirm whether your specific use case is appropriate for the product today.

Advertising and Cookies

ClearPath advertises on Google. To measure which ads bring people to ClearPath, we use the Google Ads tag on our public pages, such as the home page, pricing, articles, state pages and this page, and on the sign-up and password reset pages. The tag tells Google when someone arrives from one of our ads or campaign links, opens the sign-up form or sends us a request through a form on those pages, and it counts three steps: creating an account, logging a first hour and starting a Pro trial. Google may also use visits to these pages to show ClearPath ads to people who have been to our site.

In the app, including the setup steps after sign-up, the tag runs only at the moment one of those steps happens: when you save your first hour during setup, and when Stripe confirms a Pro trial started, during setup or on the billing tab in Settings. It loads then with page views turned off, so it does not record which pages you visit. Google is told which step happened, on which page, and, for a trial, the plan and how often it is billed. It is not told what you entered. The next page you open reloads without it.

The tag never runs on the pages where you keep your records: the dashboard, your hours, board forms, the audit, supervision, and the setup steps where you import hours or add your supervisor. It never receives your hours, client details, supervision records or forms.

Where it runs, the tag sends Google the page you are on, the codes in the link that brought you, such as the ad campaign or an offer code, and the website that sent you, such as google.com, with the page you came from there if that website shares it. It does not send the rest of the web address, and when you come from one of our own pages it sends only clearpathhours.com as the website that sent you. For a later positive subscription payment attributed to an ad, ClearPath may send Google only the ad click identifier, payment time, actual amount and currency, and Stripe invoice identifier used to prevent duplicates. It does not send the ClearPath user ID, name, email or clinical records. It sets advertising cookies: _gcl_au on clearpathhours.com, and Google's own cookies on Google's domains, such as doubleclick.net. You can block them in your browser settings or with a content blocker, and ClearPath works the same without them.

Subprocessors

ClearPath relies on a small set of vendors to operate the service: Supabase (managed Postgres and sign-in, hosted on AWS), Vercel (application hosting), Stripe (billing), Resend (transactional email), Sentry (error reports) and Cloudflare (DNS and email routing). Each is selected for SOC 2 compliance and an established security program. The full list, the data each receives, and the region they store it in is available on request.

We also use Google Ads to measure our advertising, as described under Advertising and Cookies. Google does not receive your records.

Optional AI review (audit assist) and the AI chat about your hours send a limited part of your records to a third-party AI provider acting on our instructions. AI review sends the audit's findings and your most recent entries; the chat sends your question and a short summary of your hours, such as totals by category, not your individual entries. The state-rules audit remains the primary compliance answer; the AI does not change your records on its own.

Disclosure & Reporting

If you believe you've found a security issue affecting ClearPath Hours, please email support@clearpathhours.com with the words 'Security' in the subject line and as much detail as you can share (a reproduction, the affected URL, and the impact you observed). We aim to acknowledge inbound security reports within one business day.

We do not currently run a paid bug bounty. We will, however, credit researchers who report issues responsibly in writing on this page once the issue is patched, with their permission.

What ClearPath Does Not Do

ClearPath does not sell or rent your data, ever. It does not put advertising tags on the pages that hold your records, and it never gives your hours, client details, supervision records or forms to advertisers. It does not silently change your hour records on your behalf. Every audit and AI suggestion is an explicit prompt that you review and approve.

ClearPath is not a substitute for your state board's authority. The product shows you the rules and prepares the same forms boards publish, but the licensure decision is theirs and the responsibility for what you submit is yours.