Privacy Policy
Draft — subject to change.
Version: draft 1 · Date: 2026-09-24 · Service: Cosign, at cosignagents.com · Provider: [Company legal name], [address], [privacy email].
The short version
- Cosign is business software used by organizations. Most of the information in it belongs to those organizations (their emails, files and records). For that information, the organization decides and we act on its instructions.
- We keep a small set of records about each person ourselves: their profile (name, email address and the link to their login), the sign-in emails we send them, problem reports they send us, and security records. For those, we decide, and this policy tells you how to ask us to change or erase them.
- We use outside companies to host and run the service. They are listed, with what each one sees, in our sub-processor list.
- We do not sell personal information, do not use it for advertising, and do not use it to train AI models.
- Our servers are in the United States.
1. Two roles, so you know whom to ask
In privacy law, the party that decides why and how personal information is used is the controller (California says "business"); the party that handles it on the controller's instructions is the processor ("service provider").
| Information | Who decides | What that means for you |
|---|---|---|
| Your platform profile — name, email address, the link to your login at our sign-in service; the sign-in emails we send you; invitation records; the "do not email" list of our shared inboxes; problem reports you send us; our security records of your requests | We are the controller | Ask us (section 7) to see, correct or erase these. |
| Everything inside a customer organization — emails and attachments sent to it, files uploaded, text you typed there, records from connected systems, proposals and approvals | The organization is the controller; we are its processor | Ask the organization. If you ask us, we pass your request to every organization you belong to, belonged to or were invited to, with a due date, and tell you what we did (section 7.3). |
QuickBooks. If an organization connects QuickBooks Online, we act for that organization. We do not process QuickBooks data on Intuit's behalf; Intuit and we each answer for our own handling.
2. What we collect, and why
2.1 As controller (our own records)
| What | Where it comes from | Why we keep it |
|---|---|---|
| Name and email address; the identifier of your login at our sign-in service | The invitation an organization sent you; the sign-in service when you first sign in | To know who is asking on every request; to email you sign-in links |
| Sign-in emails and their delivery records | Created when you ask to sign in | To sign you in; to prove a link was sent when a sign-in fails |
| Invitation records | An administrator invited you | To let you in only when someone invited you |
| The "do not email" list of our shared inboxes | You, or an organization, asked us not to write to an address | So we do not email someone who asked us not to (kept as a scrambled copy of the address) |
| Problem reports | You wrote one in the app ("Report a problem") | To fix the problem; kept in our own records, not the organization's |
| Security and request records | Every request you make | To refuse requests that are not allowed, to detect abuse, and to keep the audit record. These records name you by an internal code, never by address |
| Your organization memberships, roles and what you approved | Your actions in the app | The permanent audit record of who did what |
Caller addresses. The service counts requests per caller address to slow floods. The count is kept in memory only and is not stored.
Cookies. The web app sets the cookies its sign-in library needs to keep you signed in, and one cookie that remembers the last place you were in the app. There are no advertising or analytics cookies.
2.2 As processor (an organization's records)
Emails and attachments sent to the organization's addresses; files its members upload; records in systems it connects (for example, QuickBooks Online); text its members type; the text we extract from documents; the actions our software agents propose and the approvals its members give. We use these only to provide the service to that organization. The organization's own privacy notice tells its people, suppliers and clients what it does with them.
Outside people. Someone who emails an organization that uses Cosign — a supplier, a tenant, a client — will have their message stored and read by the service for that organization. The organization is responsible for telling them. Nothing in one organization is visible to another.
3. How AI is used
Software agents, using AI models from outside providers, read an organization's documents and messages and propose actions. A person approves before anything happens. Documents are sent to a text-reading service to turn scanned pages into text, and to a virus-scanning service to check files. These providers are in the sub-processor list with what each one receives. We do not use your data, or an organization's data, to train AI models, and we choose providers and plans that do not train on what we send them.
4. Who we share it with
Sub-processors — companies that run parts of the service for us (hosting, database, email, file scanning, text
reading, monitoring). The current list, with what each one receives and where it is, is published
at [URL]. We tell customer organizations before we add one.
Connected services — only at an organization's instruction, only the data needed for the approved action.
Law — when we must, and to protect the service or people's safety. We tell the organization first when the law allows.
Business transfer — if the business is sold, the buyer takes over this policy.
We never sell personal information or share it for advertising, and we have not in the past 12 months.
5. How long we keep things
A legal hold — an order to preserve records — pauses every deletion below.
| What | How long | Counted from |
|---|---|---|
| Your platform profile (name, email, login link) | Until you or an administrator removes you, then erased on request within one month | your request |
| Invitation records and sign-in delivery records | Kept; erased on request (replaced by a keyed marker so the erasure can be proved) | your request |
| Problem reports | 180 days | filing |
| Stored replies to repeated requests (some carry an email address) | 30 days | storing |
| The original copy of an incoming email (headers and undecoded body, kept only to re-check delivery) | 30 days | receipt |
| Emails and attachments not attached to any case | 3 years | receipt |
| Case documents, the case record and its memories | 7 years after the case closes by default (on the organization's request, from 3 years to no limit), then deleted. A summary of each case's approvals and writes, with no personal details in it, is kept while the organization's account exists. The organization can request a copy of its records at any time | case closed |
| Finished background work records | 14 days; failures: 90 days after they are acknowledged | completion; acknowledgement |
| Derived data (caches, projections) | 30 days unused | last use |
| The audit record — who proposed, approved, carried out and paid for what | Never deleted; personal details replaced by an internal code on erasure | — |
| A closed organization's content | Erased after a 90-day delay, after an export receipt; the audit record stays | closing |
| Backups | [to fill in] |
— |
| Our sub-processors' own logs | Their stated periods | — |
| Your signed-in session | One-hour token, refreshed silently; signed out after 14 days without use | last use |
An organization may keep its content longer than these windows; it may not shorten a financial-record window.
6. How we protect it
Encryption in transit everywhere; secrets (such as connection credentials) encrypted at rest with keys held outside the database; access rules enforced by the database itself, so no organization can read another's rows; a permanent audit record; virus checks and safe re-building of files before anyone opens them; retention and erasure by rule, with receipts; an outside monitor that alerts us when the service is down. No method is perfect; if we learn of a breach affecting you we will tell the affected organization within the time our customer terms state, and you directly where we are the controller and the law requires it.
7. Your rights, and how to use them
7.1 What you can ask
Depending on where you live, you may have the right to know what we hold about you, to correct it, to get a copy, to have it erased, to limit how it is used, to object, and not to be discriminated against for asking. We give everyone these rights for the records we control, whatever the law requires.
7.2 How to ask us (our own records)
Email [privacy email] from the address on your profile, or ask through the app. We confirm your identity by sending a
link to that address. We answer within one month. Erasure of your platform profile:
- We switch your account off everywhere at once (reversible for a week).
- After the wait, an operator confirms; your memberships end and pending invitations are cancelled.
- Your login is removed at the sign-in service; we erase your profile, sign-in emails, invitation records and mail you sent to our own addresses.
- You get a receipt listing what was erased, what was kept, and where each organization's request stands.
What we keep after an erasure, and why: a scrambled copy of your address so we never email you again; records of who did what, under an internal code shown as "former member"; backups until they expire (with the erasure repeated if one is restored); our providers' logs for their stated periods.
7.3 Asking about an organization's records
We pass your request to every organization you belong to, belonged to or were invited to, with a one-month due date. The organization decides — it may remove your identity from what you typed and keep the record as its business record ("identity removed"), delete the content, or state a reason for keeping it — and one of our operators carries out what it asks. If an organization does not answer, we follow up, and we record that it went unanswered; we do not act on an organization's data without its instruction. Text you typed while doing an organization's work is shared work data under our customer terms: the organization may keep it with your identity removed.
7.4 Complaints
You may complain to us at [privacy email] and to your local privacy regulator.
8. Where the data is
We are based in Oklahoma City, Oklahoma. The database, the sign-in service, file storage and the application servers
run in the United States, in northern Virginia (the us-east-1 region); our sub-processors are in the United States
unless the sub-processor list says otherwise (the text-reading service processes in the European Union). If you are
outside the US, your information is transferred to the US.
9. Children
The service is for business use by adults. We do not knowingly collect information from anyone under 18.
10. Changes
Each version of this policy is numbered and dated. We tell organizations of material changes by email and in the app before they take effect, and keep old versions available.
11. Contact
[Company legal name], [address], [privacy email].