Privacy
What we hold, and why
Private Attaché keeps a professional firm's work in one place. That means it holds real information about real people, so this page says plainly what is kept, who it is shared with, and how to have it removed.
Last updated 20 October 2026
Who this covers
This policy is for Private Attaché, run by Right Tail Corporation. It covers the Work Center, the Client Portal, the Learning Center and the Partner Center, which share one sign-in.
Two kinds of people appear in it. A professional, who signs up and runs a firm's workspace. And that firm's clients and contacts, whose details the professional enters or invites. The professional decides what goes in; we hold it for them and do as they ask with it.
What we collect
Only what the product needs to do its job.
- Your account: name, email address, and either a password you chose or the Google account you signed in with. We never see a Google password.
- Your firm: its name, logo, plan, and the people you invite to it.
- Your work: clients, contacts, requests, work plans, forms, documents, messages and invoices, exactly as you enter them.
- Your devices: the browser and operating system you sign in from, when you last used each, and the network address of the most recent visit. This is what the Active sessions list on the Sign-in screen shows you, and nothing else reads it.
- Payments: handled by Stripe. Card numbers never reach our servers; we keep the subscription, the invoices and the last four digits Stripe tells us.
- What you connect: see below.
The services you connect, and what they let us read
Nothing below happens unless somebody in your firm connects it, and any of them can be disconnected on the Apps screen. Disconnecting deletes the stored token at once.
- Google Calendar and Outlook Calendar: we read the events in a window around today so they appear beside the work, and we write the events you create in the product.
- Gmail and Outlook Mail: we read messages exchanged with people already in your Work Center, which is to say your clients, their contacts and your own colleagues. We do not read the rest of the mailbox, and the mailbox owner's own address is never treated as one of those people, precisely so that everything in the inbox does not match. A short summary of a matching message is stored against the client it concerns.
- Google Drive: we copy documents from the product into a folder we create for your workspace. We ask for the narrowest scope Google offers, which lets us touch only files we created and never the rest of your Drive.
- Slack: we list the channels you choose, read their recent messages, and post what you send from the product.
- QuickBooks Online: we create invoices there from the product's own, and read payments back.
Artificial intelligence
The product drafts work plans, summarises email and answers questions. Two providers do this work: DeepSeek writes, and Google Gemini searches and reads a document you point it at.
What is sent is the text needed for the task at hand and nothing more. It is not used to train anybody's model. Every request is metered against your credits, which is why the figure on your bill moves with real use.
Who else sees it
We do not sell anything, and we do not share anything for advertising. Your information reaches a third party in three cases only.
- The services above, when you have connected them, for the purposes described.
- The companies that run the product: Supabase for the database, storage, sign-in and the emails that carry invitations, password resets and sign-in codes; Vercel for hosting; Stripe for payment.
- When the law requires it, or to protect somebody from harm.
How long we keep it
Your work stays while your account is open, because that is what it is for. Archive a record and it is hidden from the lists while remaining recoverable.
Ask us to close your account and we delete it, and the firm's data with it, within thirty days. Backups fall out of rotation within another thirty. Where the law makes us keep an invoice, we keep the invoice and nothing else.
Keeping it safe
Access is enforced by the database itself, not only by the screens: a row belongs to a workspace, and a reader who is not a member of that workspace cannot read it even if they reach the address.
Traffic is encrypted. Passwords are held by the authentication service, hashed, and never in a form we can read. Sign-in can be protected by a second step, either a code emailed to you or an authenticator app, and you can see and end your other sessions.
No system is perfect. If something goes wrong that affects you, we will tell you.
Your choices
You can see and correct most of what we hold from inside the product, under Settings. For the rest, write to us.
- Ask for a copy of what we hold about you.
- Ask us to correct it.
- Ask us to delete it, and your account with it.
- Withdraw a connection, by disconnecting that service on the Apps screen.
Children
The product is for professional work and is not intended for anybody under 16. We do not knowingly collect their information, and will delete it if we learn we have.
Changes, and how to reach us
If this policy changes in a way that matters, we will say so in the product rather than quietly editing the page.
Write to collaxionsupport@gmail.com. We answer within two working days.
Questions about any of this, or a request about your own data, go to the same place.