Legal

Privacy Policy

How Rivet handles the information you and your organization share with us.

Version 1.1 · Effective

1. Who we are and what this policy covers

Rivet is operated by Rivet, Inc. ("Rivet", "we", "us"). This policy explains what personal information we collect through the Rivet app, our website at rivet.network and the Rivet API. It also explains how we use that information, who receives it, how long we keep it, and the choices you have.

Rivet is a service for businesses. Organizations use it to exchange documents, messages and workflow steps with the businesses they work with. Information in Rivet therefore falls into two groups, and different people decide how each is used.

Information your organization puts into Rivet. This means documents, messages, workflows, catalogs, records about the businesses your organization works with and the people at them, and email sent to your organization's Rivet address. Your organization decides what goes in and why. We handle it on your organization's behalf, following its instructions and our agreement with it. If you have a question or a request about this information, start with your organization, and we will help it respond.

Information Rivet decides how to use. This means your account and sign-in details, the security records we keep to protect the service, your organization's billing records, and information about visits to our website. We are responsible for how this information is used.

This policy does not cover services you choose to connect to Rivet, such as your accounting system or the account you sign in with. Their own policies govern what they do with information. Some optional features have their own terms and a supplemental privacy notice, which we show you before you turn them on.

2. Information we collect

Your account. We collect your name, work email address and the password you set. If you sign in with Google or Microsoft, we collect instead the name, email address and account identifier that provider shares with us. We also collect the second factors you set up: an authenticator app, a passkey, email codes, or a phone number for text-message codes. We record your role and permissions in each organization you belong to, and display preferences such as theme and text size.

Your organization. Its name, handle, address, phone number, website, industry, entity type, company size, tax identification number and logo, and who administers it.

What you and the businesses you work with put into Rivet. This includes:

  • documents such as invoices, purchase orders, quotes, bills of sale, delivery confirmations and settlement statements, and their attachments;
  • messages and channels, and workflow steps and approvals;
  • signatures, with the IP address from which each was made;
  • comments and notes, and the addresses and contacts on documents;
  • vehicle identification numbers and product catalogs.

This content often names people who do not use Rivet, such as the contact on an invoice, or the buyer, seller and witnesses on a bill of sale.

Email sent to your organization's Rivet address. Each organization on Rivet has its own email address. When anyone sends email to it, including people who do not use Rivet, we receive the sender's name and email address, the subject line, the message and its attachments. We keep the sender's details, the subject, reference numbers found in the message, the first 5,000 characters of the message body, and every attachment.

Invitations. When you invite someone, we keep their name and email address, any business details you enter for them, and your welcome message.

Files and decks your organization shares. When your organization shares a file or a deck with someone, we keep that person's name and email address and the one-time codes they sign in with, stored only as a one-way hash. We also record which pages or slides each person opens and for how long, so your organization can see who has viewed what it shared.

Gate passes. When your organization issues a gate pass for goods to be collected, we keep the name, company, phone number and email address of the person named to collect them. When the goods are released, we record who presented the pass, who released the goods and when. If the releasing device shares its location, we also record where.

Accounting systems you connect. You can connect an accounting system such as QuickBooks or Xero. When you do, we receive, under your authorization, your company's details, chart of accounts, customers, vendors, invoices, bills and payments. Connecting Xero also shares the connecting person's name and email address with us. We keep a record of each document we send to your accounting system and of its reply, and we may import past invoices and bills as reference documents. Your authorization is stored encrypted.

Bank accounts you connect. When you connect a bank account, we use Plaid Inc. to make the connection. You sign in to your bank through Plaid, not through Rivet, and Rivet never sees your bank username or password.

  • What Plaid gives us: your bank's name, and the account's name, type, last four digits, balances and transactions. When you set an account up for payments, Plaid also gives us its account and routing numbers.
  • What we keep: the bank and account details, the balances and the transactions, and the token that identifies the connection, which is stored encrypted. We do not store the account or routing number.
  • Plaid's own policy: Plaid handles your information under its own privacy policy, which we show you before you begin.

Gio. Your conversations with Gio, a running summary of each conversation, the preferences and shortcuts Gio keeps, the ratings and comments you give Gio's answers, and daily usage counts for your organization. Section 4 explains this in full.

Security and technical records.

  • When you sign in and use Rivet, we record your IP address, browser and device type, how you signed in, and when your session started and was last active.
  • Our security log records sign-ins, changes to security settings, administrative actions and access to sensitive records, for example when someone views or downloads a document. Each entry includes the IP address and browser of the person who acted.
  • When you accept our Terms of Service and this policy, we record which version you accepted, when and how, and the IP address and browser you used.
  • To limit sign-in abuse, we keep short-lived counters keyed to your IP address or to a one-way hash of your email address, never the address itself.

Billing. Your organization's plan, its number of members, and its usage, such as documents imported with AI. While Rivet is free during its invitation period, we collect no payment details.

Developers. API keys, which we show you once and then store only as a one-way hash; webhook endpoints; and API usage counts.

Visits to our website. Our website and app use no third-party analytics, advertising or tracking tools. Like any web host, the services that deliver our pages see the IP address and details of each request.

3. How we use information

We use personal information to:

  • provide Rivet: store information, show it to the people entitled to see it, run workflows, deliver messages and notifications, route email to the right place, and keep your accounting system in step with Rivet;
  • run the AI features described in section 4;
  • keep Rivet secure: confirm who you are, apply your organization's security settings, detect and prevent abuse, and keep a security log;
  • bill your organization for its plan and usage;
  • send service messages, such as invitations, notifications, billing notices, security alerts, and notice of changes to our terms or this policy;
  • answer you when you contact us;
  • understand and improve Rivet, using aggregate counts, the ratings and comments you give Gio, and counts of topics Gio could not answer, which record the topic and never the question or who asked it; and
  • meet our legal obligations and enforce our terms.

We do not sell personal information, share it for advertising, or use it to build advertising profiles. Rivet does not train AI models on your information. We do not send marketing email to people who use the app.

4. How our AI features handle information

Two features send information to our AI model provider: document extraction and Gio.

Document extraction. When you upload a document for Rivet to read, or one arrives by email at your organization's Rivet address, we send the whole file to our AI model provider with its file name. A file is an image, or a PDF up to its first 20 pages.

  • For a document you upload in a connection, we also send the name of the organization you are working with.
  • For email, we also send the sender's email address and the subject line.

The provider returns the details it finds, such as parties, dates, amounts, addresses and line items. For a document you upload in a connection, you review the results, and nothing is created until you confirm. For email, the results are stored with the message so it can be routed, and they become part of your organization's records.

Gio. Each time you ask Gio something, we send our AI model provider:

  • your question;
  • the recent messages in your conversation with Gio, and its running summary;
  • the preferences and shortcuts Gio keeps for you;
  • basic facts about your organization's setup; and
  • the results of the lookups Gio makes to answer you.

Those results can include the names of your connections and of the businesses you work with, document details, the names of people in your organization's activity, and short excerpts of messages you can read. Gio reads only what you are allowed to read, only inside your organization, and never another organization's private information. Gio can suggest a change, and nothing changes until you confirm it.

What Gio keeps. Your conversation is kept as messages in your own Gio channel, with a running summary of it. Gio keeps the preferences you ask it to remember and the shortcuts you save. A shortcut saved for your whole organization is visible to its members. Gio may also suggest a preference based on your conversation, and a suggestion does nothing until you confirm it. You can review, confirm and delete the preferences, shortcuts and suggestions Gio keeps in "What Gio knows".

What our AI provider does with it. Our AI model provider may use this information only to provide its service to us, and is not permitted to use it to train its models.

AI output can be wrong or incomplete. Check extracted details and Gio's answers before you rely on them.

5. Who receives information

The people you work with on Rivet. Rivet exists to share information between businesses, so sharing is built into how it works.

  • Members of your organization see its information according to the roles and permissions its administrators set. Administrators can see membership and security activity, export a member's information, and delete a member's account.
  • When your organization works with another organization on Rivet, the documents, messages and workflow steps in that shared connection are visible to the members of both. Your organization's private workspace is not.
  • If you join another organization's workspace as a guest or connection member, that organization sees what you do there.
  • When your organization shares a file, a deck or a gate pass with someone, that person sees what is shared with them, and your organization sees when they viewed it.

Providers that run Rivet. We use service providers for cloud hosting, databases and file storage; passing messages between our own systems; delivering our website and app; sending and receiving email; sending text-message verification codes; connecting your bank account; and AI processing. They may use personal information only to provide their services to us. Our current list of these providers, what each does and where it processes information is available on request at contact@rivet.technology. We notify organization administrators by email at least 30 days before a new provider begins processing customer information.

Services you choose to connect. When you sign in with Google or Microsoft, connect your accounting system, or connect your bank account, information moves between Rivet and that service at your direction.

Signed records you share. If Rivet gives you a signed record of a document's history, you can share it with anyone you choose. Anyone can check it against our public verifier, which answers only whether the record is genuine and reveals nothing else.

Legal reasons and business changes. We may disclose information when the law requires it, in response to valid legal process, to protect the rights, property or safety of Rivet, our customers or others, or to enforce our terms. If Rivet is part of a merger, acquisition, financing or sale of assets, information may be transferred as part of it, and this policy will continue to apply to it.

6. How long we keep information

We keep information for as long as we need it to provide Rivet to your organization, and as follows.

InformationHow long we keep it
Your accountFor as long as it exists. When it is deleted, we erase your name, email address, phone number, sign-in methods and security factors, and end your sessions. Documents, messages, comments and signatures you made stay in your organization's records as they were written.
Sessions30 days after they end, so security events can be investigated.
Security logAt least 400 days.
Your acceptance of our terms and this policyKept as the record of the agreement, including after your account is deleted.
Your organization's documents, attachments, messages, workflows and catalogsFor as long as your organization uses Rivet. We do not delete them on a schedule.
Email received at your organization's Rivet addressFor as long as your organization uses Rivet.
Email that reaches no organizationKept until we delete it at your request (section 12).
Files and decks your organization shares, and the records of who viewed themUntil your organization removes the file, the deck or the person it was shared with, or leaves Rivet.
Gate passes and their release recordsFor as long as your organization uses Rivet.
Document historyPermanently, by design. See below.
Gio preferences and shortcutsUntil you delete them or your account is deleted.
Your Gio conversations and their summariesUntil your account is deleted or your organization leaves Rivet.
Export files7 days after they are created.
Records of what was sent to your accounting systemFor as long as your organization uses Rivet, including after you disconnect it.
A bank account you connectedUntil you remove it, which ends the connection at Plaid. The record of the connection and the transactions recorded against it stay with your organization's financial records.
Operational logsUp to 400 days.
BackupsInformation we delete can remain in our database provider's backups until they expire.
Invoices and billing recordsKept as financial records, including after your organization leaves Rivet.
Revoked API keysTheir one-way hash is kept in the security record.

Document history. When Rivet records a change in a document's status, it records it in an append-only history, so that anyone holding a signed record of the document can confirm it has not been altered. Each entry identifies the account that made the change by an internal identifier, never by name or email address. The history is never deleted, including after an account or organization is.

When your organization leaves Rivet. An administrator can close your organization's account in Settings → Security → Data & retention, choosing a closing date 7 to 30 days away, and can cancel until the closing steps begin. Two days before the closing date, access is limited to administrators, and we prepare an export of your organization's records for them to download. The export lists your organization's files but does not contain them, so download any files you want to keep before the closing date. Within 30 days after the closing date, we:

  1. archive your organization's security log;
  2. move shared conversations to each counterparty's own keys, so it can still read them;
  3. destroy every encryption key that belongs to your organization, so anything encrypted with those keys can never be read again;
  4. delete your organization's private records and files: its workspace, private channels and messages, members' access, catalogs, addresses, the files and decks it shared and the records of who viewed them, the email received at its Rivet address and its attachments, Gio memory, API keys and webhooks; and
  5. leave each business you worked with its copy of what you shared with it (the connection, its messages and its documents), with your organization shown as "Former Rivet organization" and its identifying details removed.

We keep the security log, document history, billing records and the record of each person's acceptance of our terms, as described above.

Legal hold. An administrator can place a legal hold on your organization. While it is in place, we do not delete your organization's records through account deletion or closing, and its export files and the earlier versions of the files it shares do not expire, until the hold is lifted. Short-lived records that exist only to run the service, such as sessions and verification codes, and our operational logs still expire on their usual schedule.

7. Your choices and rights

Get a copy of your information. Download your information from Settings → Account → Export my data, once a day. The download is a single file, signed so its contents can be verified, and it is available for 7 days. It includes your profile, sign-in and security settings, sessions, memberships, the security events about you, and records of the messages and documents you created. Your organization's administrators can also export a member's information or everything the organization holds.

Correct it. Update your profile in Settings. Your organization's administrators can update its details.

Delete it. Your organization's administrators can delete your account in Settings → Security, after exporting your information or recording a reason. If you belong to more than one organization, each deletes only its own records about you, and your sign-in remains for the others. You can also ask us, and we will work with your organization.

If you do not use Rivet. Your information may be in Rivet because a customer holds it: you emailed an organization's Rivet address, you are named in a document, or you were invited or sent a file. In that case, that organization decides how it is used. Contact the organization, or contact us and we will pass your request on and help it respond.

Your rights under privacy laws. Depending on where you live, you may have the right to know what personal information we hold about you and how we use it, to receive a copy, to correct it, and to have it deleted. You may also have the right to opt out of its sale or its use for targeted advertising, though we do neither. We will not treat you differently for exercising these rights. To make a request, contact us as described in section 12. We will confirm your identity, usually by confirming you control the email address on your account, and respond within 45 days. You may use an authorized agent.

8. How we protect information

We protect information with safeguards that include:

  • encryption of all traffic to Rivet with TLS 1.2 or later;
  • encryption of stored information, with named personal and credential fields also encrypted individually under keys that belong to your organization, held in a cloud key-management service. These fields include phone numbers, tax identifiers, access tokens and authenticator secrets;
  • access limited, on every request, to the organization and connections that hold the information;
  • multi-factor authentication, which administrators can require across their organization, with recovery codes stored only as keyed hashes;
  • sessions with time limits that administrators can end at any time, and a fresh check of your identity before sensitive actions;
  • sign-in with Google or Microsoft linked to an existing account only when the provider has verified the email address;
  • single sign-on and automatic user provisioning for organizations that use them; and
  • a security log that administrators can review and export.

Rivet's servers can read the content stored in Rivet, because document extraction, search and Gio need to work with it.

No system is perfectly secure. If a security incident affects information we handle for your organization, we will notify your organization without undue delay. Our security practices, and how to report a vulnerability, are described at rivet.network/security.

9. Cookies and browser storage

Rivet sets only its own cookies, and only these:

CookieWhat it doesHow long it lasts
accessTokenKeeps you signed in15 minutes, renewed while you use Rivet
refreshTokenRenews your sign-in securelyUntil your session's time limit
resetToken, resetPendingComplete a password reset10 minutes
rivet_signed_outTells the sign-in page why you were signed out5 minutes
deck_sessionKeeps you signed in to files and decks shared with you7 days
rivet_theme, rivet_textRemember the theme and text size you chose1 year
viewportChooses the mobile or desktop layoutUntil you close your browser

We do not use analytics, advertising or other third-party cookies, so there is nothing to opt out of.

The Rivet app also keeps some working information in your browser, for example a form you have not finished. It also keeps copies of a few recent screens for up to 24 hours, so they open when you are offline. Clearing your browser's data for Rivet removes them.

10. Children

Rivet is for businesses and is not directed to anyone under 18. We do not knowingly collect information from children.

11. Where information is processed

We store and process information in the United States. Information in transit may pass through our network provider's servers in other countries. If you use Rivet from outside the United States, your information is transferred to the United States.

12. Contact us

Write to contact@rivet.technology with privacy questions, requests, or security reports. Rivet works remotely and handles every request by email.

13. Changes to this policy

When we change this policy, we post the new version here with its effective date and version number, and we keep every earlier version. If a change materially affects how we use information we already hold, we notify organization administrators by email at least 30 days before it takes effect, and we ask members to review it the next time they sign in.