Terms of Service
Draft — subject to change.
Version: draft 1 · Date: 2026-09-24 · Product: Cosign, at cosignagents.com · Provider: [Company legal name], a(n) [entity type] based in Oklahoma City, Oklahoma ("we", "us"). The customer organization that accepts these terms is "you" or the
"Customer".
Plain-language summary (not part of the agreement)
Cosign is business software. Software agents, which are computer programs that use AI models, read the documents and messages your organization receives and propose actions — for example, "post this bill to your accounting system". Nothing happens until a person you have authorized approves the proposal (we call that a "co-sign"). Then the platform carries the approved action out and keeps a permanent record of what was proposed, what the person saw, and who approved it.
These terms say: what you get; that your organization is responsible for its own people and its own data; that the AI only proposes and your people decide; that text your people type into the app is shared work data, kept for the work even if a person later leaves; how either side can end the relationship and how you get your data out; and what we are and are not liable for.
1. The agreement
1.1 These Terms of Service (the "Terms"), the Privacy Policy, the Data Processing Addendum (the "DPA") and any order form together form the agreement between you and us for the Cosign service (the "Service").
1.2 Who accepts. A person who creates an organization on the Service, or accepts an invitation into one, accepts these Terms on behalf of the organization they act for, and confirms they have authority to do so. The platform records which version of the Terms was accepted, by whom and when.
1.3 Business use only. The Service is for businesses and organizations. It is not offered to consumers or to anyone under 18.
1.4 Order of precedence if documents conflict: an order form, then the DPA (for data-protection matters), then these Terms, then the Privacy Policy.
2. Words with a fixed meaning
- Organization — a customer workspace on the Service. All of a Customer's data lives inside its Organizations, and no Organization can see another's data.
- Administrator — a member of an Organization who can invite and remove members, set retention choices and ask for erasures inside that Organization.
- User — any person the Customer invites into an Organization, including Administrators.
- Customer Data — everything a Customer or its Users put into an Organization or that arrives into it: emails and attachments sent to the Organization's addresses, uploaded files, records in connected systems, text Users type, and what the Service derives from them (extracted text, proposals, approvals).
- Shared Work Data — the part of Customer Data that a User created or typed while doing the Customer's work: notes, comments, approvals, replies, problem reports. Section 6 explains why this has its own name.
- Proposal — an action the Service's software agents suggest.
- Co-sign — an approval of a Proposal by a User who is authorized to give it. A co-sign is recorded permanently.
- Connected Service — an outside system the Customer links to an Organization, such as QuickBooks Online.
- Sub-processor — an outside company we use to run the Service and that may handle Customer Data.
3. Your Organization, your Users
3.1 You are responsible for your Users. You decide who is invited, what they may do, and when they are removed. Every User's actions in your Organization are your actions under these Terms.
3.2 Sign-in. Users sign in with a link emailed to their address; there is no password. That means the security of each User's mailbox is the security of their access to your Organization. You must keep Users' mailboxes protected (for example, with two-step sign-in at the mail provider) and remove a User promptly when they leave or their mailbox is compromised. Removal takes effect on the User's next request to the Service.
3.3 Administrators speak for you. We act on an Administrator's instructions — invitations, removals, retention choices, erasure requests, connecting and disconnecting a Connected Service — as your instructions.
3.4 Your Organization's contact. You will keep at least one Administrator reachable, and give us a security contact (a person and an email address) we may notify under section 11.
4. What the Service does, and what it does not
4.1 Proposals are suggestions. The Service's software agents, using AI models from outside providers, read Customer Data and produce Proposals. A Proposal is a suggestion, not a decision, and not advice. It may be wrong, incomplete or based on a misread document.
4.2 A person decides. No Proposal has any effect on your books, your Connected Services or anyone outside the Service until a User with the right authority co-signs it. The Service shows the approving User exactly what will happen before they approve.
4.3 A co-sign is your authorization. When a User co-signs, you authorize us to carry out that action exactly as shown, and you are responsible for the decision as if a member of your staff had carried it out by hand. We keep a record of the content the User saw, the time and the User's identity, and you may rely on that record as your own approval record.
4.4 Not professional advice. We do not provide accounting, bookkeeping, tax, legal or financial advice. Proposals about your books are prepared for your review; you and your professional advisers are responsible for their correctness, for your tax positions and for your records.
4.5 Your records are yours to keep. The Service is not your system of record for tax or accounting purposes. You must keep your own copies of records the law requires you to keep (see the Privacy Policy's retention table for how long the Service keeps things).
4.6 How AI is used. We will publish a plain description of what the AI does and does not do, and we will not make claims about its accuracy that our own measurements do not support.
5. Customer Data
5.1 You own it. As between you and us, you own Customer Data. You give us the right to store, process, transmit and display it only to provide, secure, support and improve the Service for you, and as the DPA allows.
5.2 You are responsible for having the right to give it to us. Customer Data includes emails from your suppliers, tenants, clients and staff. You confirm that you may lawfully collect it and hand it to us for processing, and that you have given any notices your own privacy obligations require.
5.3 Roles. For Customer Data, you decide the purposes and we act on your instructions (in privacy-law words: you are the controller or business, and we are the processor or service provider). For the small set of records we keep about each person in order to run the platform — their profile, their sign-in emails, problem reports they send us — we are the controller. The Privacy Policy sets this out; the DPA holds the processor terms.
5.4 No selling, no training. We do not sell Customer Data, do not share it with other customers, and do not use it to train AI models. Our Sub-processors are bound in writing not to train on it either; where a Sub-processor's plan would allow training, we do not send it Customer Data.
5.5 Where it lives. The Service is hosted in the United States. Sub-processors and their regions are listed on the Sub-processors page.
6. Shared Work Data
6.1 Why this section exists. When a User types text into the Service — a note on a bill, a comment, a reply, a report of a problem — they are doing your work, with your tools, on your behalf. That text is part of your Organization's record of the work, not only the User's personal information.
6.2 What you and the User agree. Text a User creates in an Organization is shared with the Organization and with us, to carry out and record the Organization's work. It belongs to that work as well as to the person.
6.3 What happens when a person leaves or asks to be erased. The Organization may keep the text a former User created, with the User's identity removed: their name and address are taken off, and the record shows an internal code and "former member" in their place. The record of who approved what is kept because it is the Organization's audit trail. We describe such kept text as "identity removed", never as "erased". A User's request to erase their platform profile is handled separately, by us, under the Privacy Policy.
6.4 Your promise to your Users. You will tell your Users, in a way that meets your own legal duties, that text they create in the Service is Shared Work Data on these terms.
7. Acceptable use
You will not, and will not let a User:
- use the Service to break the law, or to process data you have no right to process;
- upload malware, or try to get around the file checks, access controls or rate limits;
- try to reach another Organization's data, or probe, scan or test the Service's security without our written agreement;
- use the Service to make decisions about individuals that the law regulates specially (employment, credit, housing, insurance or health decisions about a person) — the Service is built for a business's own back-office work;
- resell the Service, or use it to build a competing product;
- send unsolicited bulk mail through the Service, or use it in a way that harms our mail reputation;
- feed the Service content that is unlawful, infringing or abusive.
We may act on a violation under section 10.
8. Connected Services (for example, QuickBooks Online)
8.1 You authorize the connection. When an Administrator connects an outside system, you authorize us to read from and write to it as your agent, only to carry out co-signed actions and to prepare Proposals.
8.2 Their terms are theirs. Your use of a Connected Service is governed by its own terms. For QuickBooks Online, we and Intuit each answer for our own handling of data; we do not process your data on Intuit's behalf, and Intuit is not our Sub-processor.
8.3 Disconnecting. An Administrator may disconnect at any time. When you disconnect, or your Organization closes, we stop reading and writing, revoke our access with the Connected Service, and keep only what section 10.5 and the DPA say we keep.
8.4 We store the minimum. We keep the connection credentials encrypted, keep no copy of a Connected Service's data beyond what the Service needs to show and record your work, and never log its data.
9. Our commitments; fees
9.1 Security. We keep the safeguards described in the DPA's security annex: encryption in transit and at rest for secrets, access rules enforced by the database, a permanent audit record, virus checks on files, retention and erasure by rule. We will tell you of a security incident affecting your Customer Data as the DPA says.
9.2 Availability. We aim to keep the Service available at all times and monitor it from outside.
9.3 Support. [support email].
9.4 Changes to the Service. We may improve and change the Service; we will not remove a material capability without reasonable notice.
9.5 Fees. [There are no fees during the alpha and beta periods. / Fees are stated in the order form.]
10. Suspension, termination and leaving
10.1 You may leave at any time by asking an Administrator to close the Organization, or by notice to us.
10.2 We may suspend an Organization or a User, with notice where practical, if we reasonably believe there is a security risk, a breach of section 7, unpaid fees, or a legal requirement. We lift a suspension when the cause is resolved. A suspended Organization's data is kept, not deleted.
10.3 We may terminate on [30] days' written notice for a material breach that is not cured, or on [90] days'
notice for convenience.
10.4 Getting your data out. Before an Organization is closed, and for [30] days after, you may export your
Customer Data in a common format.
10.5 What happens to your data after closing. A closed Organization enters a 90-day deletion delay, during which it can be exported but not used. After that we erase its content and derived data. We keep, for as long as our retention rules say: the audit record of who proposed, approved and carried out what (with personal details removed on request as section 6.3 describes), and records we must keep by law. Backups expire on their own schedule, and if a backup is ever restored we repeat the erasures made since it was taken.
10.6 Survival. Sections 4.3, 5, 6, 10.5, 12, 13, 14, 15, 16, 17 and 19 survive termination.
11. Security incidents
If we become aware of unauthorized access to Customer Data, we will tell your security contact within the time the DPA states, say what we know, and work with you on what to tell your own people.
12. Confidentiality
Each side will keep the other's confidential information secret, use it only for the agreement, and protect it as it
protects its own, for [3] years after the agreement ends (indefinitely for Customer Data and trade secrets). Usual
exceptions apply: information already public, independently developed, or that must be disclosed by law (with notice
where lawful).
13. Intellectual property; feedback
13.1 We own the Service, its software, its designs and its documentation. You get a right to use it under these Terms, nothing more.
13.2 You own Customer Data and the output the Service produces for you (Proposals, extracted text, records), subject to our right to keep the audit record.
13.3 If you give us suggestions, we may use them without obligation.
14. Warranties and disclaimers
14.1 We warrant that the Service will perform materially as its documentation describes and that we will provide it with reasonable skill and care.
14.2 Except as stated above, the Service is provided "as is". We do not warrant that Proposals are accurate, that the Service is error-free or uninterrupted, or that it meets any accounting, tax or regulatory standard. AI-generated Proposals can be wrong; your Users' review is the safeguard.
15. Limitation of liability
15.1 Neither side is liable for indirect, consequential, special or punitive damages, or for lost profits, revenue or data, even if told they were possible.
15.2 Our total liability under the agreement is limited to [the fees you paid in the 12 months before the claim / US$ [amount] if no fees were paid].
15.3 Exceptions. The limits do not apply to [a side's breach of confidentiality, its indemnity obligations, or its gross negligence or wilful misconduct; to a Customer's payment obligations; to our breach of the DPA up to a separate cap of US$ [amount]].
16. Indemnities
16.1 You will defend and indemnify us against third-party claims that Customer Data, or your use of the Service in breach of section 7, infringes someone's rights or breaks the law.
16.2 We will defend and indemnify you against third-party claims that the Service itself infringes a US patent, copyright or trademark, with the usual exclusions (your modifications, combinations, or Customer Data).
17. Sanctions and export controls
17.1 You confirm that neither you nor any of your owners, Administrators or Users is on a US sanctions list (including the Office of Foreign Assets Control's Specially Designated Nationals list) or located in, or ordinarily resident in, a country or region subject to comprehensive US sanctions (today: Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk and Luhansk regions of Ukraine; Intuit's list adds Belarus and Russia for apps that connect to QuickBooks).
17.2 You will not use, export or allow access to the Service in breach of US export-control or sanctions law, and you will tell us at once if 17.1 stops being true. We may suspend or terminate at once if it does.
17.3 We may check the country of a new Organization at creation and screen it against the sanctions list.
18. Changes to these Terms
We may change these Terms. Each version is numbered and dated. A material change takes effect only after an
Administrator accepts the new version in the Service (we will ask at the next sign-in, with [30] days' notice by email
first); a non-material change takes effect when posted. If you do not accept, you may leave under section 10.1.
19. Governing law and disputes
19.1 These Terms are governed by the laws of the State of Oklahoma, without regard to its conflict-of-laws rules.
19.2 Disputes go to the state or federal courts in Oklahoma County, Oklahoma, and each side consents to their jurisdiction.
20. General
Entire agreement; no assignment without consent except to a successor of the whole business; independent contractors;
notices in writing to the addresses on the order form or [legal email]; severability; no waiver by delay; force
majeure for events beyond a side's reasonable control (not including a Sub-processor's failure we could have avoided);
US federal government users get only the rights in these Terms as commercial software.