Privacy policy
Privacy Policy
Last updated November 15, 2026.
This Privacy Policy describes how Caring Voice (“we,” “us,” or “our”) collects, uses, shares, and protects personal information when you use caringvoice.app and related services (the “Service”). By using the Service, you agree to this Policy. Terms of use are separate and appear on our Terms page.
1. Information we collect
Account holders (listeners and private accounts): name, email address, and a hashed password.
Institution accounts: the same account fields. Institution SSO is available for Institution staff; when staff use Institution SSO, we receive the email address and identity attributes needed to sign them in.
Voices you add: a first name or nickname, a time zone, and the log configuration you choose.
People who enter the day: the name and role they type, the phrases they save, and basic device details kept with each care-log row. The client IP address is recorded on care-log rows and is not shown in review. No phrase is flagged as entered from outside.
Technical and security data: session cookies, PIN device grants when “Remember me” is used, and operational logs needed to run and secure the Service.
2. How we use information
We use personal information to operate and secure the Service: showing caregivers the right voice, producing conversations, emailing listeners, managing accounts and Institution access, and responding to support requests. We do not sell personal information, show advertising, or use log content for anything other than the conversations you asked for.
3. How we share information
We share information only as needed to provide the Service:
- With listeners and Approvers according to the access rules for each voice (see “Who can see what”).
- With subprocessors who host infrastructure, deliver email, or provide Institution SSO, under contracts that limit their use of the data to providing those services.
- When required by law or to protect the rights, safety, or security of users, the Service, or others.
We do not sell personal information or share it for cross-context behavioral advertising.
4. Cookies and similar technologies
Caring Voice uses cookies and similar browser storage that are necessary to run the Service. That includes remembering a signed-in session and, when someone uses a caregiver PIN with “Remember me,” remembering that this device may open that voice again without re-entering the PIN until the grant expires or is cleared. We do not use advertising cookies, and we do not sell personal information.
5. Do Not Track
Some browsers send a Do Not Track (DNT) signal. Caring Voice does not change its behavior in response to DNT signals. We limit tracking to what is needed to operate and secure the Service, as described on this page, whether or not a DNT signal is present.
6. Information about minors
Caring Voice is set up by adults about the people they care for, who are often minors. We ask for as little as possible: a first name is enough. Each voice has one owner, who decides which other listeners can see it and is the person who can erase the record. While a voice an institution set up still has no owner, the Cluster Admin (first Approver) can erase it too.
7. FERPA and state education law
Caring Voice adheres to the Family Educational Rights and Privacy Act and to the student-privacy requirements of applicable state education law. Where an institution or district is the custodian of a student's record, we handle that record under the district's direction and for no purpose beyond providing the service.
8. Who can see what
Contributors enter data throughout the day via PIN login. An Approver reviews, prepares, and sends the conversation to the Voice's listeners, ensuring consistency and correctness of the conversation.
- A PIN login shows only the phrases that device entered that day. An approver sees every phrase and is who gives the PIN to people who enter without an account. The PIN stays hidden until an approver opens it. Listeners and owners never see or set the PIN.
- Listeners and owners see approved content only, except for alerts they opted into. They do not see the day's conversation before an approver sends it. A signed-in listener or owner can open Try it only from the Phrases page. Try it lets them practice the caregiver day and see a packaged email on screen, marked as Try it / not a care log. Nothing from Try it is saved or emailed. Listeners never get a PIN to their own voice. A listener cannot be an approver on that same voice. A person who is both keeps two separate, unlinked accounts.
- Caring Voice staff work with accounts and access: we can help you get signed in, correct an email address, sort out who holds a voice and in what role, and check whether a conversation was sent. We do not read the phrases or conversations themselves.
9. The PIN
On the PIN login there is a Remember me checkbox, unchecked unless the person checks it, and a duration menu: 5 days, 1 month, 6 months, or 9 months. The menu shows 6 months unless they choose another. Checking the box alone remembers for 6 months. Changing the menu only matters when the box is checked. A month is a calendar month from the moment they sign in, in the voice's time zone.
When Remember me is checked, the device PIN grant and cookie last for the chosen duration. Closing the browser does not end it. Session ends does not shorten a remembered grant.
When Remember me is not checked, the device cookie lasts only until the browser closes. It has no expiry date and no maximum age, and it is gone when the browser closes. Leaving the page, switching tabs, and the screen sleeping do not end it. The server also ends the grant at a deadline, so a browser left open still loses the PIN when the deadline passes, and an intact cookie is refused after that deadline. If today's weekday has an end time still in the future, the deadline is that time today. If that time has already passed, the deadline is 15 minutes from sign-in. If today has no end time, the deadline is 6 hours from sign-in. Whichever comes first ends the grant: the browser closing, or that deadline.
Approvers set a time for each weekday, Sunday through Saturday, labeled Session ends. Each time is a time of day or empty. Empty means that weekday has no session end. Listeners and owners do not see or set them. Owners who are not approvers do not set them. Each time is a wall-clock time in the voice's time zone, or the installation's default time zone when the voice has none.
The product does not lock the day when the page is left or the screen sleeps. A district can say not to log on a student's device, and not to log other voices on that device.
10. Approvers
- The day's conversation reaches listeners only when an approver sends it. An alert, such as an injury, is the exception: it may reach listeners who opted into alerts before that send. A PIN session can mail an alert; the day's conversation still waits for an approver. Sending the day's conversation needs an account rather than a PIN, so the record can say who sent it. Nothing can be sent until an approver is seated. On a voice a household starts, the owner names the first approver and only the first. On a voice set up for a household to claim, the Cluster Admin is the first Approver, and the owner, once somebody claims it, does not seat Approvers.
- Adding an approver needs every current approver and the owner. Accepting an invitation does not seat the person: every current approver and the owner have to agree first. Removing an approver needs the owner plus one other approver. The person being removed does not vote. If there is no other approver, the owner alone can remove. If the voice has no owner, one other approver can remove.
- Approvers can see each other's names and email addresses. When the voice already has approver roles, the person accepting picks from that list and cannot type a different one. When it has none, the first person's typed role becomes the first approver role. An invitation lasts fourteen days. The invitation address counts as confirmed, and no confirmation email follows an account created from that invitation. Turning an invitation down adds nothing to the account, and the person can still write the day with the PIN.
- An approver cannot own the voice. It belongs to the household. Giving up ownership leaves the voice unowned and deletes nothing. Until an unclaimed voice is claimed, only the Cluster Admin (first Approver) can erase it, and only when an institution set it up. While a voice has no owner, any listener can invite one. Handing a voice on keeps the previous owner as a listener receiving conversations, and the new owner can hand it back. Closing an account leaves voices the person only guards where they are, with their owner. After leaving a voice, the owner — or, while it is unowned, any listener — can invite them again. The ownership and approver history is kept apart from the voice's content, survives erasure, and cannot be edited or removed.
11. Downloading a copy of a record
If you own a person's voice, you can download the whole record from that voice, as often as you like. It is the complete record rather than a tidied version of it: every phrase and utterance, the earlier wording of anything that was later corrected, every conversation as it was sent, who had access, and the name behind each item — who wrote it, who changed it, who sent it or took it out. That includes phrases you were never shown: ones that were never released to you, and ones someone in a current role cleared before a conversation went out. Each one says which it is. The caregiver PIN and the private caregiver address are left out. Pausing a voice does not take this away — you can still download the record afterwards.
What you receive is an ordinary zip file of web pages and data files. It is not encrypted and it does not expire, so anybody who can open the device it is sitting on can read it. Once it has downloaded it has left the service, and looking after it from then on is yours to do. We keep a record of each download: when it happened, and who asked for it.
12. Email
We send account email (confirmations, password resets, invitations) and the conversations and alerts your listeners opt into. Each listener can turn conversations or alerts off for each person.
13. Where your data is held, and how
Your data is held on servers run for us by third-party hosting and email providers, not on hardware we own or operate. If you want to know which providers we use and where they operate, email us and we will tell you. Passwords are hashed; PINs are encrypted; connections use HTTPS. No system is perfect, and we will tell you promptly if we learn of a breach affecting your data.
For Institution accounts that use Institution SSO, WorkOS is a subprocessor for that sign-in. WorkOS is not a certification of our care-data practices, and it does not replace the district’s own obligations under FERPA or state education law.
14. Your choices
Each voice has one owner. Only the owner can add or remove listeners, hand the voice to another listener, download the whole record, pause the voice, or erase the record. While a voice an institution set up has no owner, the Cluster Admin (first Approver) can erase it. While a voice has no owner, any listener can invite one, because that invitation is how the voice gets an owner. Listeners can change the voice itself — its items and its current roles. They do not see or set the PIN, and they do not see or set Session ends for any weekday. Each listener chooses for themselves whether to get conversations and alerts.
A listener who does not own a voice can stop following it whenever they like. The owner cannot simply walk away: hand the voice to another listener, or erase it. The same goes for closing your account — if you still own a voice, hand it on or erase it first, because we will not pass a voice to somebody else on your behalf.
Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of personal information, or to object to certain processing. Contact us using the address below to make a request. We may need to verify your identity before responding.
15. How long we keep things
We keep a care record for 10 years, unless the owner erases it sooner, and at the end of that period we erase it on the same terms. The period is long on purpose: a care record is the kind of thing a household or an institution may need to produce years after the voice that held it has gone.
When the owner asks to erase a record, we accept the request at once and wait 60 days before the care content becomes unreadable in the service. A hold can extend that date; we still accept the request — you do not have to ask again — and we tell you the date.
When that wait ends, the phrases, utterances and conversations stop being readable by you and by us in the service. Any copy that remains in backups after that erasure event is not accessible. What stays is the shape of the record rather than any of its words: that the voice existed, who logged and approved on which dates, and who asked for the erasure and when. That is a record of our conduct and the institution's rather than of your household, and we keep it.
Three things can hold an erasure up, and each of them is a legal obligation we are not allowed to erase around: a legal hold; an outstanding request to inspect the record; or an education agency being the custodian of it. If one applies we still accept the request — you do not have to ask again — and we tell you the date it will be carried out on.
16. Pausing a voice is not the same as erasing it
Pause stops the voice opening for every listener and caregiver. Nothing is destroyed: phrases and conversations already written stay as they are, encrypted, and no longer reachable through the app. Erasing is the stronger thing. Both are the owner's to do. If you want a copy of the record before you do either, the owner can download one at any time, including after the voice has been paused.
17. Protecting others in care content
When writing phrases or utterances, describe other people by their relationship or role rather than using their names. For example: a friend, a peer, a visitor, another individual, a sibling, or a teacher.
For staff, use their role when practical, such as OT, teacher, or Contributor.
The Occasional and Frequent note screens keep only a short reminder: include what happened and who did what, but avoid entering other people's names whenever possible. Longer examples live here and in the signed-in Guide.
18. Changes to this Policy
We may update this Privacy Policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the Service after an update means you accept the revised Policy. Material changes may also be described in product notices where appropriate.
19. Contact
Questions about privacy? Email hello@caringvoice.app.