> For the complete documentation index, see [llms.txt](https://docs.rubica.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubica.au/households/secure-presentations/security-and-data.md).

# Security and Data Handling

What is stored, how clients are kept apart, and what is logged.

* **Each person has their own link.** An invite link is for one person, works once and lasts 7 days. A forwarded invite that has already been used doesn't let anyone else in.
* **Dates of birth and passcodes are never stored as typed.** They're scrambled the same way passwords are, as soon as you share. Nobody at your firm or at Rubica can read them back, only check a guess.
* **Passcodes are never emailed.** You give them to the client yourself.
* **Wrong guesses are limited.** 5 wrong tries locks that person out for an hour.
* **Firms are kept apart.** Each firm's presentations live on its own web address, and a sign-in for one firm never works for another's.
* **Your email is checked before it's saved.** Scripts, forms and on-click code are removed from a firm template, and the email preview in Salesforce can't run code.
* **Firm-sent emails are logged** on the household. The client's one-time link is replaced with the presentation's plain address in the log, so the log can't be used to sign in.
* **Everything is recorded.** Invites, sign-ins, wrong tries, opens, previews and changes appear in the share's **Activity**.
* **Your CRM keeps a record of each presentation** on the household: its title, who it's shared with, the sign-in check, expiry and activity. It never holds the one-time links, dates of birth as typed, or passcodes.
* **Pages aren't cached.** Private presentations are marked so browsers and networks don't keep a copy.