Security and privacy
Last updated: November 16, 2026
In short
- Families' contact details, notes, messages and call transcripts are encrypted in our database.
- We sign a business associate agreement (BAA) with each community that needs one under HIPAA, and we need one from every company below that handles family information.
- Families can see, download or delete what a community holds about them, from the link at the bottom of every email.
- We don't sell personal information, and we don't put advertising or analytics tags inside the app or on pages where families type their details.
Who is responsible for what
Each senior living community decides what information to collect from families and what to do with it. Under HIPAA the community is the covered entity and we are its business associate. Under the GDPR and similar laws the community is the controller and we are its processor. We only use family information to run the service for that community.
How we protect information
- Encrypted when stored: names, email addresses, phone numbers, form answers, notes, texts, chats, call transcripts and summaries, and tour notes are encrypted in the database with AES-256-GCM. The key is kept outside the database and the code.
- Encrypted in transit: every page and connection uses HTTPS.
- Who can see it: staff only see the communities they belong to, with roles that limit what each person can do. Two-step sign-in is available, and idle sessions sign out automatically.
- Records of access: we log sign-ins, changes to settings, and every data export and deletion, so a community can see who did what.
- Less data to AI: when we use AI to draft emails or suggest next steps, we leave out names, email addresses and phone numbers and fill them in afterwards. The chat assistant and AI phone agent do see what a family says to them, and recorded calls are transcribed, so our AI provider is covered by the agreements below.
- No ad tracking inside the service: Google Analytics and the cookie banner run only on our public marketing pages, never in the app, on community pages, forms, quizzes, tour booking or the email preferences page.
Business associate agreements
Communities that are covered by HIPAA sign a BAA with us before they put family information into Occupancy Pilot. To ask for ours, email [email protected].
Every company in the table below that handles family information must sign a BAA with us, or a data processing agreement for the GDPR, before it receives that information. The table shows where each one stands.
Requests from families
Every email a community sends through Occupancy Pilot has a link to a preferences page. From there a family member can:
- stop marketing emails or texts,
- see what each community holds about them and download a copy,
- delete it themselves.
Before showing or deleting anything we email a one-time code to the address, so a forwarded email can't be used by someone else. Every request is recorded, and the community can see it. After a deletion we keep only a scrambled copy of the email address, so we can make sure no more emails are sent to it.
Families can also ask the community directly, or email [email protected]. We answer within 30 days.
How long we keep information
- Family records (contact details, notes, activity) are deleted automatically 7 years after they were created, unless the community deletes them sooner.
- Anonymous website visits used to show which marketing works are deleted after 18 months.
- Call recordings are deleted from our phone provider when the family's record is deleted.
- When a community leaves, it can export its data, and we then delete its account and everything in it.
- Deletion requests are honored right away. We keep a record that the request happened and a scrambled email address on the do-not-email list, never the deleted details.
Companies that help us run the service
These companies process information for us. "Family information" means anything about a family or prospective resident, such as contact details, messages or call audio.
| Company | What it does | What information | BAA |
|---|---|---|---|
| Our hosting provider | Runs our servers and database in the United States | All information in the service, encrypted as described above | BAA required before go-live |
| Cloudflare | Protects the site from attacks and speeds it up | All web traffic passes through it, including what families type into forms | BAA required before go-live |
| Twilio | Phone calls, call tracking numbers, call recordings, texts and the AI phone agent's phone line | Phone numbers, text messages, call audio and recordings | BAA required before go-live |
| SendGrid (Twilio) | Sends email | Email addresses, names and email content | BAA required before go-live |
| OpenAI | AI chat and phone answers, drafts and suggestions, call transcripts and summaries, and tour notes | What families say to the chat assistant or AI phone agent, recorded call audio, and tour recordings. Drafts and suggestions leave out names, emails and phone numbers | BAA required before go-live |
| Stripe | Takes card payments for Occupancy Pilot plans | The account's name, billing email and card. No family information | Not needed: no family information |
| Google Fonts | Typefaces on some family-facing pages | The visitor's IP address and browser details. No family information | Not needed: no family information |
| Pexels | Stock photos staff can add to pages and emails | Search words staff type. No family information | Not needed: no family information |
| Google (Tag Manager, Analytics, Search Console) | Measures visits to our own marketing website only | Visits to occupancypilot.com marketing pages, only with cookie consent. Never used in the app or on family pages | Not needed: no family information |
| ConsentCaptain | Cookie consent banner on our marketing website only | Your cookie choices on our marketing pages | Not needed: no family information |
Connections a community turns on
A community can connect its own accounts. Information then goes to that company under the community's own agreement with it, not ours:
- Calendars (Google Calendar, Microsoft 365): booked tours with the family's first name and a link back to the record.
- Senior living CRMs (such as Yardi, WelcomeHome, Aline, Sherpa, Enquire, Salesforce): family records the community chooses to send.
- Google Ads and Meta ads: only the ad click ID and the type of milestone (inquiry, tour, move-in). No names, emails, phone numbers or health details, not even scrambled.
- Webhooks and Zapier: whatever the community sets up to send.
We'll update this list before we add a new company that handles family information.
Report a security problem
If you think you've found a security problem, email [email protected]. Please don't access or change other people's information while testing. If there is a breach of family information, we tell the affected community promptly, and no later than HIPAA requires, so it can notify families.
See also our Privacy Policy, HIPAA page and accessibility statement.