The context stays with you
Keep contact details and internal follow-up together in the client record.
Your work, shared
with care.
Briefs and proposals can contain sensitive project information. Here is how access is designed, what you control and what still needs verification before launch.
Clear about where we are.
These are implemented product controls with local tests. Production storage, provider agreements, backups and operational checks are still being finalised. This page is not a certification or an external audit.
Your work has two sides.
You decide what to share.
Prepare the project in your workspace and share a version made for your client.
A draft you can work on
Edit the content and review the proposal before publishing a version.
A view for your client
The published document contains the proposal, without the studio's internal notes.
Screenshots and details from the actual app, using fictional data.
What you can control.
- A separate workspace
- Clients, briefs and proposals belong to a studio. The implemented server and database controls enforce account boundaries; browser filters are not the access boundary.
- Share deliberately
- A published link exposes the client-facing document. Draft changes remain private until you publish a new version.
- Links you can revoke
- Public links use hard-to-guess tokens, expiry and revocation. Anyone with a valid link may access it; they are not password-protected invitations.
- Control over client data
- The product includes export and deletion workflows. Studio-only notes and follow-up are separate from the public proposal.
- Clear activity records
- A visit is not proof of reading or identity. Link responses, email-code acceptance and local test activity have distinct states.
The details, in writing.
Read the available legal documents for the current environment. Final production providers and terms must be confirmed before public launch.
A little more
clarity.
Where will project information be stored?
The final production environment and provider details are pending confirmation. We are not yet making a public promise about a specific data region. A studio’s custom domain does not move its data to its own hosting.
Are public proposals indexed?
Client proposal and brief routes are configured not to be indexed. That instruction is not access protection: use expiry and revocation to control valid links.
Can I request help with privacy?
Use the contact details in the privacy document or the contact link in the footer. Ask only for the client information needed for the project.