Privacy Policy

Privacy Policy

Briggzy is a family care-coordination service operated by Keystone Software LLC, an Alabama limited liability company. This policy covers the Briggzy app and briggzy.com. Questions, or a request about your information, go to privacy@briggzy.com.

1. What we collect

Account details. Your name, email address, phone number, and the sign-in and session data needed to keep your account secure.

Care information about the person you care for. This is the heart of the product, and it is health information: diagnoses and conditions, medications and doses given, allergies, appointments, incidents, notes, measurements, routines, supplies, expenses, insurance details, emergency contacts, and any free-form text you write. The person being cared for is often a child or another dependent who has no account of their own; the caregivers in their circle enter and see this information on their behalf.

Files you upload. Photos attached to an entry, documents, and expense receipts.

Household details you choose to add, such as care instructions or home access notes that a substitute caregiver would need.

Device and notification data. If you turn on notifications, a push token for that device. If you connect a calendar, the access token that connection needs.

Basic usage and security data. Which product actions happen and when, so we can tell whether the beta is working, plus rate-limit counters. Activity is tied to a one-way fingerprint built from a shortened IP prefix and browser family; we do not store your full IP address with it.

If you ask to be invited. Briggzy's beta is invitation only, and you can apply from briggzy.com without creating an account. When you do, we keep your email address, the browser you sent it from, and where the request came from, so we can invite you. That is the whole of it: we do not add you to any other list, and applying does not create an account or share anything with anyone.

We do not collect location, contacts, advertising identifiers, or biometric data.

2. How information is used

To operate the service: to let the people you invite coordinate care, to send the reminders you ask for, to keep your account secure, and to understand whether the product works during the beta. Nothing else.

We do not sell your information, we do not share it for advertising, and we do not use it to train models.

Support and troubleshooting. We hold the key that encrypts your care information, so it is technically possible for us to read it. As a practice we do not. Our error reports and logs are built to carry no care details — no names, conditions, medications, or note text — so day-to-day debugging happens without them. If a problem can only be solved by looking at your actual entries, we ask you first and look at no more than the problem needs.

3. Who can see your information

Ongoing access is limited to the people added inside each circle. Temporary guest links show only the level of detail you chose when you shared them, and they expire on their own.

A guest link is a secret in a URL. Anyone who has the link can open it until it expires or you revoke it, so treat it like a key: send it to one person, and revoke it from the circle's sharing page when they no longer need it.

4. Who else processes it, and why

These companies handle data on our behalf, as service providers acting on our instructions. None of them receives it for their own purposes.

• Supabase — the database, sign-in system, and file storage. Data is held in the United States (US West).
• Vercel — hosting and scheduled jobs. Requests pass through it to reach the app.
• Resend — delivery of account emails only (sign-in links, invitations, confirmations). It handles the email address and the link, not your care information.
• Cloudflare — the challenge that stops automated sign-up and sign-in abuse. It sees the request, not your care information.
• Apple and Google — app distribution, and delivery of push notifications to your device if you turn them on. Notification text is deliberately generic (for example, "a dose is due"); it never contains health details or names.

One integration sends information out at your request rather than ours: if you connect Google Calendar, the appointments you sync — their title, time, location, and any notes on them — are written to your own Google calendar, and Google's privacy policy governs them there. Disconnect it from the circle's calendar settings to stop that.

5. Security

Traffic is encrypted in transit. Access is enforced per row in the database, so a person can only read the circles they belong to, and guest links resolve to exactly the slice of data they were created for. On top of that, sensitive free-text and health fields — names, conditions, medications, notes, documents, titles, and the like — are encrypted with our own key before they are stored, so they are not readable in the database as plain text. Uploaded files live in private storage that is not publicly reachable.

No service is immune. Briggzy is in private beta and should not be your only copy of anything critical, such as a medication schedule.

6. Your choices

You can export everything your account can see, and delete your account, from inside the product under Me. If you cannot sign in, you can still ask us to delete it from our account deletion page. You can revoke guest links at any time. To see, correct, or get a copy of your information, write to privacy@briggzy.com and we will answer within 30 days.

7. Deleting your account

Deleting closes your sign-in, ends your sessions on every device, and removes you from every family you were part of. We delete your phone number, the notification tokens for your devices, any calendar you connected, and your personal shortcuts, and we revoke the guest links and calendar feeds (ICS export links) you created. Your email address and phone number are released, so you or whoever holds them next can use them again.

The care history stays. Doses, notes, appointments, incidents, and documents you logged remain in the family circle they belong to. They are records about the person being cared for, made together by that family, and removing them would erase another caregiver's record of their own child's care. Your display name stays on those entries too, so the history still reads "logged by Dad" rather than "Member" — deleting your account is not the same as being forgotten everywhere. If you would rather your name did not remain, change your display name before you delete, or write to privacy@briggzy.com.

If you organize a family, you choose what happens to it before you can delete your account. You can hand it to another member, who has to accept it, or delete the family outright. Deleting a family permanently removes its records, notes and files for everyone in it; we tell you how many people that is before you confirm.

8. How long we keep information

We keep your account details and your circles' care information for as long as the account is open. After you delete your account we keep three things on purpose: the care entries described above, the record that you accepted these policies and which version of them (that record is the proof of consent itself), and a small internal note of your display name so your entries keep their author. We also keep the circle-side history of who read a briefing, which is care coordination rather than a profile.

Deletion takes effect in the live service immediately. Where a copy exists in an encrypted operational backup, it is never restored into the service and ages out with that backup within 30 days.

One narrow exception: where the law requires us to keep something, or where we need it for a legal claim, a security or fraud investigation, or to enforce our terms, we keep that specific record for as long as that reason lasts, and then delete it. We do not use anything kept this way for any other purpose, and it does not put your account back in the product.

A request to be invited is kept until you have an account or until the beta closes, whichever comes first, and is then deleted. Ask us at privacy@briggzy.com to remove it sooner and we will, whether or not we have invited you yet.

9. Where information is processed, and your rights

Briggzy is operated from the United States and your information is processed there. If you use it from elsewhere, you are sending it to the United States.

Depending on where you live you may have the right to see, correct, export, or delete your information, to withdraw consent, and to complain to a regulator. The product gives you export and deletion directly; for anything else, write to privacy@briggzy.com. We do not charge for these requests and we do not treat you differently for making one.

Briggzy is not intended for use by children on their own accounts. An adult caregiver holds the account and enters information about the person in their care.

10. Data handling posture, and why HIPAA does not apply

Briggzy's consumer beta operates as a privacy- and consent-based service you use directly as a family. It is not a medical device, it does not diagnose or treat, and it does not replace a clinician's records.

**HIPAA does not apply to Briggzy, and this matters.** HIPAA covers healthcare providers, health plans, and clearinghouses, and the vendors they hire. Briggzy is none of those: it is a tool a family uses directly, like a notebook or a shared calendar. Information does not become HIPAA-protected just because it is about health. So the medication list, notes, and appointments you keep here are protected by this policy, by the access controls in the product, and by consumer-privacy law — not by HIPAA. Your doctor's copy of the same information is still covered by HIPAA in their hands; your copy here is not.

11. Changes to this policy

We may update this policy. When we do, we record the version in effect at the time you accepted it, and we ask you to accept a new version when the substance changes.

12. Contact

Keystone Software LLC · privacy@briggzy.com. Requests to access, correct, export, or delete your information go to that address, and there is a public account deletion page you can use without signing in.