Last updated: October 26, 2026
1. Who we are
Robin is a product of Zamora Design LLC, El Cerrito, California. Questions: privacy@zamora.design.
2. Who this covers
Studio users hold accounts; call participants join without one. Where a studio uses Robin on its own clients’ information, the studio decides what is collected and we act on its instructions. Data processing agreements: privacy@zamora.design.
3. What we collect
- Calls: a transcript (speakers, text, timestamps), up to twelve marked-up screen frames attached to their tickets, participant name, business and email as supplied, call metadata and rating, and tickets and comments. We do not store call audio; it is processed live and never written to disk.
- Voice notes: transcribed, never saved; only the transcript is kept.
- Accounts: sign-in identity is handled by Clerk; we store preferences and usage counts. Paid plans bill through Stripe; card details never reach Robin.
- Quotes, contracts and invoices: the document’s contents and recipients (contract text freezes when sent); signature records (name, email, typed signature, time, a salted hash of the IP address, browser, document fingerprint and consent version); decline reasons; signed PDFs in private storage; payment amounts, dates, methods and statuses; and Stripe’s reference to any saved payment method. Card and bank details stay with Stripe.
- Ask Robin: reads only the studio records the asker can already see, and changes nothing. Conversations are not stored on our side; we keep usage counts and content-free logs.
- Our site: Vercel Web Analytics, cookieless and aggregate only. The contact form gives us your email and message.
4. How we use it
To run calls and produce transcripts, tickets and summaries; to operate and support the product; to send documents and take payments on them; to answer Ask Robin questions; to reply to inquiries; and to check Robin’s filing accuracy using ticket content. We do not sell personal information or use call content for advertising.
5. Who else handles it
US-hosted providers for call and voice carriage, speech-to-text, AI models, hosting and storage, sign-in, email and notifications, and payments. Each receives only what its function requires; we will say which provider handles what on request.
Robin’s main AI model is Google’s Gemini API. Content sent to it may be used to develop Google’s products and services, and human reviewers may read it. It receives transcribed call text, a picture of your screen on turns where you ask Robin to look, and the review, email-drafting and Ask Robin content described above — never call audio. Ask Robin never sends it contact details, payment details or contract text, but anything said aloud is in the transcript. When the main model fails, a backup model from another provider answers that turn; we have not confirmed its retention or training terms. The speech provider is told on every request not to train on the audio. Marked-up screens go to no AI model.
6. How long we keep it
Call records: until the studio deletes them; deleted items disappear immediately and are purged after fourteen days. Ask Robin: nothing kept. Documents, payment and signature records are kept as the record of what was agreed; signature records cannot be edited or deleted within Robin. Accounts: the life of the account. To request deletion, write to privacy@zamora.design; legally required records stay, and we will tell you which and why.
7. Where data lives
US infrastructure, database in Northern Virginia. Non-US information is transferred to and processed in the US. EU/UK studios needing a transfer mechanism or DPA should write before running a call.
8. Access
Studios are separated server-side; one cannot see another’s records. Screen images live in private storage behind expiring links. Zamora Design administrators can access records for support.
9. Your rights
Anyone whose information appears in Robin may request a copy, correction or deletion at privacy@zamora.design. Where a studio controls the record, we act on your request and inform the studio, or refer you to them and say so. Depending on where you live, you may have further rights under the CCPA or GDPR; write to us and we will honor them.
10. Security
Authentication is required and two-factor authentication is required on Robin accounts. We hold no security certification: no SOC 2, ISO audit or independent penetration test yet. We would rather say so than imply otherwise.
11. Consent on calls
Participants see a notice before joining that the session is transcribed by Robin, an AI project manager. Joining indicates agreement to it and to this policy.
12. Children
Robin is a business product, not directed at anyone under 18.
13. Changes
Posted here with an updated date; material changes emailed to account holders.