How we protect your documents

• The database and the receiving area for files are hosted in São Paulo, Brazil (region sa-east-1).
• The application itself also runs in the São Paulo region (gru1).
• Once received, documents are filed in the firm's Microsoft 365 environment, which becomes the official record.

• All traffic uses HTTPS with TLS. The domain sends an HSTS header, which instructs the browser never to accept an unencrypted connection.
• Files and the database are encrypted at rest with AES-256 by the storage infrastructure.
• No file has a public address. All reading happens through a signed, short-lived link issued only to an authenticated user.

• There is no open sign-up. Access is created by a named invitation, valid for 7 days and usable once.
• The invitation is bound to an email address. If the link is forwarded to someone else, it does not work for them.
• We store only the cryptographic hash of the invitation, never the code itself.
• You set your own password when you activate the invitation. It must be at least 12 characters, and passwords that have appeared in known public breaches are refused.
• Passwords are stored only as a salted hash by the authentication provider. No one at the firm can read your password.
• Sessions are held in a cookie that JavaScript cannot read, and are refreshed on the server.

Isolation between clients is enforced by the database itself, through row-level security policies, and not by a check in the interface.

The practical difference: even if there were a flaw in the interface, a query made with one client's credentials returns no record and no file belonging to another. The rule lives in the innermost layer, where a programming mistake in the outer layer cannot reach it.

• Every sign-in, file upload, questionnaire save and read-link issued creates a record with date, time, author and originating address.
• That record cannot be altered or deleted, not even by a system administrator: the database refuses the operation.
• The trail for your account is visible to you inside the portal, on the audit trail page.

• Only document, image and audio formats are accepted. Executables and archives are refused.
• The check reads the content of the file, not the extension in its name — a program renamed to .pdf is refused.
• Malware scanning is performed by Microsoft Defender at the point of filing in the firm's environment.

• The receiving area is temporary. Once filing in the firm's environment is complete, it is no longer the reference copy.
• The database has a daily backup.
• After the engagement ends, documents follow the firm's document retention policy, and you may request a copy or deletion through the channels set out in the privacy policy.

None of the services below is permitted to use the content of your documents to train artificial intelligence models or for any purpose of their own.

• Vercel — running the application.
• Supabase — database and file receiving area, in São Paulo.
• Microsoft 365 — final filing and email, within the firm's corporate environment.
• Anthropic — reading documents to produce the internal summary that briefs the team. The content is not used for training.
• OpenAI — converting a voice briefing into text, if you choose to record one. The audio is not used for training.

Recording is optional — the written form covers the same ground. If you do record, one thing is worth stating plainly: the audio is sent to a speech-to-text service (OpenAI) to be converted into text. It is not used to train models, but it does leave our environment for that single step.

The resulting text is a working aid for the team, not a record of what you said. Automatic transcription makes predictable mistakes with technical terms, and we treat the recording itself as the source. Nothing produced by transcription is sent back to you as if it were your words.

• It does not request and does not hold access to your Google Drive, OneDrive or any system of yours. You choose and send each file.
• It does not publish any document at a freely accessible address.
• It does not share your documents with another of the firm's clients, under any circumstances.

This environment went live recently and has not yet been penetration-tested by an independent firm. The controls described above are implemented and can be demonstrated; external audit is planned before wider use.

If your legal team or your investor requires a formal security assessment before you send anything, tell the lawyer responsible for your account: we run that process before any document is uploaded.