Privacy Policy
Effective 1 October 2026 · Last updated 12 October 2026
This policy explains what chERP OCD (“chERP”, “we”, “us”) collects through this website and the chERP app, why, and who we share it with.
The short version
- This website sets analytics cookies only if you say yes in the cookie banner. The chERP app has no analytics at all.
- Client health information belongs to the practice that entered it. We hold it for them under a Business Associate Agreement and HIPAA.
- We don’t sell personal information, use it for advertising, or use client information to train AI.
- If you’re a client with a question about your records, ask your practice first. They decide who sees them.
- Your practice may show its own name and logo in the client portal and its emails instead of ours. chERP still keeps your records for the practice, and a short line naming chERP says so (section 4).
- If you try chERP in the sandbox, use only the invented sample client. What you do and tell us there is deleted automatically 90 days after your visit starts (section 4).
1. Two kinds of information
Client health information. Practices use chERP to keep their clients’ clinical records. That information belongs to the practice. We handle it only on the practice’s behalf, as its business associate under HIPAA. Section 2 covers it.
Everything else. This covers people who visit this website, write to us, book a demo or try chERP in the sandbox, and the practice staff who hold chERP accounts. We’re responsible for this information ourselves. The rest of this policy covers it.
2. Client health information
Before a practice enters any client information, it signs a Business Associate Agreement (BAA) with us. That agreement, HIPAA, and the practice’s own Notice of Privacy Practices govern what happens to it. In short:
- We use it only to run chERP for that practice, to keep it secure, and as the law requires.
- We don’t sell it, use it for marketing, or use it for analytics, research, product development or training AI models without the practice’s written permission.
- Each practice’s records are kept separate from every other practice’s. That includes its audit log: a practice’s supervisors see their own practice’s entries and no one else’s.
- Inside a practice, clinicians see only their own clients, unless the practice has set up supervision or group access. Every look at a chart is recorded in an audit log.
- Our own staff don’t browse client records. If we ever need to see one to fix a problem, it happens at the practice’s request, and it’s logged.
- Our Security Official reviews the audit log across all practices, to keep chERP secure. Each practice can see, in its own audit log, what our staff do to its account, such as changes to its agreement, its settings, its staff and its invitations.
If you’re a client: requests to see, correct or get a copy of your records go to your practice, which decides how to respond. If you contact us, we’ll pass your request to your practice and help them answer it.
3. This website
- Analytics. This website uses Google Analytics, loaded through Google Tag Manager, to count visits and see which pages help practices decide. Both load on every page of this website.
- Before you choose, or if you decline. No analytics cookies are set and nothing is stored on your device. Google still receives basic signals without cookies, such as that a page was loaded, which it uses to estimate traffic.
- If you choose “Accept”. Google Analytics sets cookies (section 7) so it can tell a returning visit from a new one. It collects the pages you view, the page you came from, your device and browser type, and your approximate location (city level). Google Analytics doesn’t log or store IP addresses.
- No advertising. Advertising signals stay switched off whatever you choose, and there are no ad pixels on this site.
- Never in the app. Neither tool runs anywhere in the chERP app, where practices and clients sign in.
- Hosting. The site is served by Cloudflare. Like any web host, Cloudflare processes basic request data such as your IP address and browser type to deliver pages and block attacks.
- Fonts. Our typefaces are served by this website and the chERP app themselves. Loading them doesn’t contact Google or any other font service.
- Email. If you email us, for example to book a demo, we keep your message and contact details to reply and follow up.
The “Time saved” calculator runs entirely in your browser. The numbers you enter aren’t sent anywhere.
4. Using the chERP app
For practice staff with accounts, we collect:
- Account details: name, work email, role and practice. If you sign in with Google, we receive your name and email address from Google.
- Sign-in security: a securely hashed version of your password (we never store the password itself), and your second step: the secret for your authenticator app, a passkey, or both. For a passkey we keep only its public key, an ID, the name you gave it, the kind of device it’s on, and when it was added and last used. The private key never leaves your device. Recovery codes are stored hashed.
- Activity: an audit log of sign-ins and of what each account viewed and changed, with times. This is how practices and HIPAA auditors see who did what.
- Technical data: IP address, browser and error logs, used to run and secure the service. Our logs are built to leave out client health information and sign-in links. When we find something in them that shouldn’t be there, we fix the logging, and logs age out after 30 days (section 9).
- Practice details: the practice’s name and its time zone, which sets the times on its schedule and in its emails.
- Invitations: we invite each practice’s first supervisor. After that, on the Practice plan, a supervisor invites new staff from inside their own practice. chERP emails the setup link to the person invited. We keep the name, email address, role and any note the supervisor adds.
- Billing details: who to send the practice’s subscription payment link to, and a record of what it has paid. Card details are entered on Stripe’s payment page; we never see or store them.
- Practice name and logo: if a practice on the Practice plan turns on white-labeling, the name it wants its clients to see and the logo image it uploads. We use them only to show to that practice’s own clients (see “Practices that use their own name and logo” below).
The client portal is for adults aged 18 and over (section 11). For clients the practice invites to it, we store their name, email address, a hashed password (or, if they choose to sign in with Google, the name and email Google confirms), when they confirmed they’re 18 or older, and what they enter in homework, check-ins, forms and questionnaires. All of this is client health information and is covered by section 2.
Links that work without signing in
A practice can also give a client a link that works without signing in. Anyone who has the link can use it until it expires, so it should go only to the client. The code that makes each link work sits in a part of the web address that browsers don’t send to our servers, so it stays out of our server logs. There are four kinds:
- Check-in links last 7 days unless the practice chooses a shorter or longer time, and never more than 14 days.
- Group intake form links last 30 days.
- Practice log links let a client log their homework practice between sessions. A link shows the client’s first name and their current homework: each assignment’s title, its instructions for resisting rituals, and the words the client chose to describe their distress levels. What the client logs (how high their distress got, whether they did a ritual anyway, and any note) is added to their record. A link can be used as often as the client likes for 7 days unless the practice chooses a shorter or longer time, and never more than 14 days. The practice can withdraw it at any time.
- Questionnaire links let a client answer standard self-report questionnaires their clinician has chosen, either straight away or on a schedule the clinician sets. A link shows the client’s first name and the questions. It works once, and expires after 7 days. The answers are scored automatically and filed on the client’s record as answers the client gave themselves. Some answers, such as those about thoughts of self-harm, are flagged for the clinician to review in chERP; the client is shown crisis contacts, such as 988, at the same time. When that happens, chERP also emails the client’s clinician (or, if the chart has no active clinician, the practice’s supervisors) a short notice that a client’s answers need review, which says nothing about who the client is or what they answered (section 6). Nobody is watching the answers as they arrive, and the notice doesn’t mean anyone will respond at any particular time: the clinician sees the answers, and any flag, when they next open chERP. A client who uses the portal also sees open questionnaires there.
What a client sends through one of these links is noted in the practice’s audit log. Check-in and intake links sent before we moved the code out of the web address still work until they expire; opening one of those can leave that one request in our server logs, which are deleted after 30 days.
Email to clients
chERP can email clients appointment reminders, links to intake forms, invitations to set up a client portal account, practice log links and questionnaire links. A reminder names the client, their clinician, the practice and the appointment time. A practice log email (subject “Your practice log”) and a questionnaire email (subject “Questions from your clinician”) name the client, their clinician and the practice, but never what the homework is or which questionnaires are being asked. Questionnaire emails on a schedule are sent automatically, on the day the clinician chose, not before 8am in the practice’s time zone. These are ordinary emails. They aren’t encrypted end to end, and once one reaches a client’s inbox, anyone who can open that inbox can read it. The name of a therapy practice can itself say something about a person’s care.
So chERP emails a client only when their practice has recorded that the client agreed to be emailed by the practice (reminders, forms, portal invitations), and only at the one address that agreement covers. The same agreement covers every kind of email above, including practice log and questionnaire links. Practices should get the client’s informed consent first. Staff record it in chERP, which notes who recorded it, when, and a one-way fingerprint (a hash) of the address it covers. Staff can turn it off at any time.
- A new address needs a new agreement. If the client’s email address changes, the agreement switches off, and nothing is emailed until the practice records it again for the new address.
- The same address is the portal sign-in. Changing it on a portal account that’s already set up ends that account’s access: the old password and Google sign-in stop working, and the client needs a new invitation at the new address.
- One address, one client. chERP won’t give a client an email address that another client, in any practice, already uses, or that belongs to a staff account.
Practices that use their own name and logo
A practice on the Practice plan can show its own name and logo, in place of ours, on what its clients see: the client portal once they’ve signed in, its setup pages, check-in, form, practice log and questionnaire pages, and PDFs made for a client or for whoever pays for their care. Emails to clients show the practice’s name, but not its logo. The app the practice’s staff use, and the portal’s sign-in page, still show chERP.
- chERP still keeps the records. Nothing about how we hold or protect client information changes. A short line naming chERP stays on every one of those screens, emails and PDFs, so clients can tell that chERP keeps their records for the practice.
- Emails come from the same address. Emails to clients still come from our address (section 6), even when they show the practice’s name.
- Before sign-in. The practice’s name and logo can appear on pages that open from a link before anyone signs in, such as a check-in, intake, practice log, questionnaire or portal setup link. Anyone who has a working link can see them.
Asking about becoming a client
The chERP sign-in page used to have a form, “Ask about becoming a client”, for people who wanted to be seen by a practice that uses chERP. That form is switched off, and chERP doesn’t take new inquiries from the public.
- If you sent an inquiry before it was switched off, we still hold what you gave us: your name and email address, any phone number and note you added, and the IP address the form was sent from.
- If a practice took you on, your inquiry is part of your record there, covered by section 2.
- Otherwise it isn’t shown to any practice in chERP, and nobody is working on it. You can ask us to delete it (section 9).
Trying chERP in the sandbox
Therapists can try chERP at try.cherpocd.com/try, which gives them a practice of their own with an invented sample client, a few guided tasks and a short survey. The sandbox is a separate copy of chERP, at its own web address (try.cherpocd.com), with its own database. It never shares a database with practices’ real records.
Please don’t enter or describe real clients there. The sandbox is for invented clients only. It isn’t covered by a Business Associate Agreement, and it isn’t the place for anyone’s health information. If you think real client details were entered, write to [email protected] and we’ll delete that sandbox.
When you use the sandbox, we collect:
- Your answers: the rating you give each task and any comment you add, which tasks you reached and whether you used a shortcut, and your answers to the closing survey.
- Where you came from: the source tag on the link you followed (for example
?from=linkedin), and when your visit started and each step happened. - A scrambled network address: a salted hash of your IP address (for IPv6, of its first half, the /64), used only to limit how many sandboxes one network can start. We don’t keep it in readable form for this purpose.
- Session and security records: the ordinary sign-in session for your sample practice, and a security log of actions taken in it. Neither records your IP address or browser type. Our hosting provider’s server logs do, for 30 days (section 9).
- If you ask to join the beta (by answering “yes” or “maybe”): your name and email address, and if you choose to give them, your practice’s name and rough ranges for how many clients you see.
- Why: to improve chERP, and to contact you about the beta if you asked us to. We use your beta details only for that, not for other marketing.
- Who sees it: chERP’s own team can view the answers and download the beta sign-up list. No practice sees any of it.
- No email from the sandbox. The sandbox never sends email. If you asked to join the beta, a person on our team writes to you separately.
- No analytics. Like the rest of the app, the sandbox has no analytics or tracking tools.
- Bot check. Before a sandbox starts, your browser solves a small puzzle to show it isn’t an automated script. It runs in your browser, and no outside company is involved.
- The orientation video is hosted on YouTube and shown in YouTube’s privacy-enhanced mode (youtube-nocookie.com). It loads only when you press play; until then, your browser sends nothing to YouTube. Once you press play, YouTube receives your IP address and browser details and may store information in your browser, and YouTube’s own privacy policy applies to that. You don’t have to play it to use the sandbox.
How long we keep it. Everything above, including the sample practice and what you typed into it, your visit, answers and survey, the scrambled address, and your beta sign-up details, is deleted automatically 90 days after your visit started. If our team has downloaded the beta list to contact you, we keep that copy only while we’re in touch with you about the beta, and delete your details from it if you ask. The security log isn’t part of that deletion: it’s built so entries can’t be quietly changed or removed, and it’s kept for as long as the sandbox runs, then deleted with it. It holds no IP address or browser details for visitors. Server logs age out after 30 days, as elsewhere (section 9). You can ask us to delete your sandbox or beta details sooner (section 10).
5. How we use information
- To provide chERP: create accounts, send staff invitations, sign people in, send appointment reminders, form links, portal invitations, practice log links and questionnaire links (including questionnaires sent on a schedule the clinician sets), score a client’s questionnaire answers, flag some for their clinician and send the clinician a notice that answers need review, send staff the morning task email if they turn it on, let practices export their records, show a practice’s own name and logo to its clients if it turns on white-labeling, and take practices’ subscription payments
- To keep chERP and its users secure, and to detect and investigate misuse
- To answer questions and give support
- To learn from sandbox visits how to improve chERP, and to contact people who asked to join the beta about the beta only (section 4)
- To send practices service and billing notices. We don’t send marketing email to clients, ever.
- To meet our legal obligations, and to enforce our Terms of Service
We don’t sell personal information or share it for targeted advertising.
6. Who we share it with
We use a small number of service providers. Each one may use information only to provide its service to us. This is the complete list. The two that store or send client health information do so under a Business Associate Agreement with us.
- Google Cloud: runs the chERP app and client portal, their database (including any inquiries sent before the inquiry form was switched off), backups and server logs. It also runs the separate sandbox (section 4) and its database, which is meant for invented clients only. Handles client health information, under a BAA (accepted 17 September 2026).
- Google Workspace (Gmail): sends email from [email protected], and keeps a copy of each message in that mailbox. To clients who have agreed to be emailed by the practice, and only at the address they agreed to (section 4): appointment reminders, group intake form links, portal invitations, practice log links and questionnaire links (scheduled questionnaire emails are sent automatically). None of these says what the homework is or which questionnaires are being asked. If the practice uses its own name and logo (section 4), these emails show the practice’s name, with a short line naming chERP, but still come from this address. To new practice staff: the link to set up their account, which names the practice and the person who invited them. To a client’s clinician, when answers the client sent through a questionnaire link include a flagged item: a notice that a client’s answers need review, with a link to Today in chERP. It doesn’t name the client, the questionnaire or the answers. To a practice’s supervisors: a notice that we’ve marked the practice’s Business Associate Agreement signed, which names the practice and the date it was signed, and holds no client information. To clinicians and supervisors who turn it on for themselves (it’s off until they do, and isn’t available in the sandbox): a morning task email, at most once a day and not before 7am in the practice’s own time zone (Mountain Time if the practice hasn’t set one), sent only on a day when they have open tasks due that day or overdue. It carries their own name, how many tasks are due today and how many are overdue, and a link to Today in chERP. It never includes what a task says. It isn’t sent to a switched-off account or to staff of a suspended practice, and our record of each one sent holds only the two counts. Handles client health information, under a BAA.
- Google sign-in: optional, for staff and clients who choose “Sign in with Google”. Google confirms who you are and gives us your name and email address. Google learns that you signed in to chERP, but receives no records from it. No client records; we don’t rely on a BAA for it. You can sign in with a password instead.
- Google Analytics and Google Tag Manager: analytics for this website only (section 3). No health information; no BAA needed.
- Stripe: takes practices’ subscription payments through the payment links we send. It receives the practice’s billing contact and card details, and never any client or health information. No health information; no BAA needed.
- Cloudflare: hosts this website, www.cherpocd.com, on Cloudflare Pages. No health information; it doesn’t handle the app.
- YouTube (Google): hosts the sandbox’s orientation video, which loads only if you press play (section 4). It then receives your IP address and browser details under YouTube’s own privacy policy. No health information; no BAA needed.
Otherwise, we disclose information only:
- to the practice it belongs to
- when the law requires it, such as a valid subpoena or court order. Where we’re allowed to, we’ll tell the practice first.
- to protect someone’s safety, or the security of chERP
- to a successor if our business is merged or sold. The successor has to honor this policy and every BAA we’ve signed.
7. Cookies
This website sets cookies only if you choose “Accept” in the cookie banner: two Google Analytics cookies, _ga and _ga_TP1NBT1QJ3, which last up to two years. If you choose “Decline”, none are set. Your choice itself is saved in your browser’s storage, not in a cookie. You can change it any time with “Cookie settings” at the bottom of each page, or clear it in your browser.
The chERP app uses only the cookies it needs to keep you signed in. We don’t use them for tracking or advertising.
sid, for staff: lasts at most 12 hours. The session behind it ends sooner, after 30 minutes without activity or when you sign out.pid, for the client portal: lasts at most 8 hours. The session ends sooner, after 20 minutes without activity or when you sign out.oauth, during Google sign-in only: lasts at most 10 minutes, and is deleted as soon as sign-in finishes.
The sandbox (section 4) uses sid for your sample practice and pid for the sample client’s portal view, as above, plus one more:
sbx: lets the same browser return to its sandbox. It’s signed so it can’t be forged, lasts 24 hours, and is sent only to the sandbox’s own/api/sandboxaddress.
If you press play on the sandbox’s video, YouTube may set its own cookies or store information in your browser (section 6).
8. How we protect it
- Two-step sign-in is required for every staff account
- Data is encrypted in transit (TLS) and at rest (AES-256)
- Access is limited by role and caseload, and every chart view is logged in an audit log that shows any tampering
- Sessions time out after inactivity
- Backups are taken automatically every day. We’ve tested that they restore, and our policy is to repeat that test every quarter
No system is perfectly secure. If there’s a breach of unsecured client health information, we tell the practice without unreasonable delay, and no later than 30 calendar days after we discover it. The practice then notifies affected clients, and others, as the law requires of it. If a breach affects other personal information we hold, we notify people as the law requires.
9. How long we keep it
- Client records stay in chERP for as long as the practice is a customer, following the practice’s instructions, because they’re legal clinical records the practice must keep. chERP archives a client’s chart rather than deleting it. Staff can delete some working items, such as a rating saved partway to finish later, which is deleted once it’s finished or discarded; each deletion is noted in the audit log. When a practice leaves, it can export its data for 30 days. We then return or destroy it as the BAA sets out.
- Exports. A practice can download a client’s complete record, or its supervisors every record the practice holds, at any time. We don’t keep a copy of the download; each export is noted in the audit log. Once downloaded, the copy is the practice’s to protect.
- Backups age out automatically after 30 days, so deleted data can remain in encrypted backups for up to 30 days.
- Audit logs and compliance records are kept for at least six years, as HIPAA requires. We never delete audit log entries to save space.
- Server logs are kept for 30 days, then deleted automatically. Google keeps its own record of administrative changes to our cloud account for 400 days.
- A practice’s name and logo for white-labeling are kept while the practice is a customer. If it turns white-labeling off or moves to the Solo plan, we stop showing them but keep the logo so it can turn white-labeling back on, unless it asks us to delete it. When a practice leaves, we delete them with the rest of its data after its 30 days to export.
- Staff accounts are switched off, not deleted, when a practice removes someone, so the audit log can still show who did what.
- Inquiries sent through “Ask about becoming a client” before the form was switched off, including ones a practice declined, are kept until they’re deleted. We don’t yet delete them automatically. If yours didn’t lead to care, you can ask us to delete it.
- Emails chERP sends to clients are kept in the sending Google Workspace mailbox until they’re deleted. We don’t yet delete them automatically.
- The sandbox: the sample practice and everything in it, your visit, answers, survey, scrambled network address and beta sign-up details are deleted automatically 90 days after your visit started. The sandbox’s security log, which holds no visitor IP addresses, is kept for as long as the sandbox runs (section 4).
- Emails and demo requests you send us are kept as long as we have a reason to follow up, then deleted.
10. Your choices and rights
Practice staff and website visitors can ask us to show, correct or delete personal information we hold about them. Practice staff can write to [email protected], and anyone else to [email protected], and we’ll reply within 30 days. Depending on where you live, you may have more rights under state law. We’ll honor them, and we won’t treat you differently for using them.
Some things can’t be deleted. We can’t delete audit log entries, because they’re a legal record of who accessed what. And we can’t delete a practice’s clinical records on an individual’s request; the practice decides what happens to them.
To stop website analytics, choose “Cookie settings” at the bottom of any page and then “Decline”.
Clients: see section 2. Your practice is the right first contact.
11. Children and teens
This website isn’t aimed at children.
The client portal is for adults aged 18 and over. A client confirms they’re 18 or older when they set up their account, or the next time they sign in, and we record when they did. The portal also needs a date of birth on the client’s chart, written as a full date (YYYY-MM-DD) between 1900 and today. If that date is missing, can’t be read, or says they’re under 18, chERP won’t send them a portal invitation and they can’t use the portal, whatever they confirm. Practice staff can add or correct a date of birth on the chart; each change is recorded in the audit log, which notes whether the date made the client an adult or not, but not the date itself.
Practices that treat children and teens keep their records in chERP as usual; the portal rule doesn’t change a minor’s chart. There is no portal account for parents or guardians.
- Group intake, practice log and questionnaire emails. chERP won’t email any of these links to a client whose chart says they’re under 18, or whose date of birth can’t be read. If no date of birth is recorded, the email can still go, if the client has agreed to be emailed.
- Links handed over in person or sent another way (section 4). Before staff make a practice log link, send questionnaires or set up a questionnaire schedule for a client whose chart says they’re under 18, or has no date of birth or one that can’t be read, chERP warns them and asks them to confirm. It doesn’t stop them. Check-in links don’t check age at all. A practice can give any of these links to a younger client or a parent, so the practice decides whether to, and handles consent under the laws that apply to it.
- Appointment reminders go to the address the practice has recorded agreement for, whatever the client’s age. For a younger client that may be a parent’s address.
Information about minors is client health information, covered by section 2.
12. Changes to this policy
If we make a material change, we’ll update the date at the top and email practices at least 30 days before it takes effect. We won’t use information we already hold in a materially different way without the consent the law requires.
13. Contact
Questions about privacy, or a request about your information:
chERP OCD
607 S 360 E
Salem, UT 84653
Practices using chERP: [email protected]
Everyone else: [email protected]