Privacy

This notice covers three groups of people:

• Business users — people who create a Relayd account and work in a workspace, including invited team members.
• Clients and recipients — people a business exchanges documents with through a Drop, Request or Delivery link. They don't need an account.
• Website visitors, including anyone who uses the contact form.

When a business uses Relayd to collect or send its clients' documents, that business decides what to ask for and why. Relayd handles those documents on the business's behalf. If you're a client with a question about your documents, contact the business that sent you the link first.

Accounts. Your name and email address; a hashed password (we never store it in a readable form) or, if you sign in with Google or Apple, the identifier that provider gives us; and session records, which include the IP address and browser description of each signed-in session. Email verification and password reset codes are stored only as hashes and expire after 10 minutes.

Workspace content. Everything a business adds or receives: client records (name, email, company, phone, notes), documents and every version of them, original file names, any name or email an uploader types on a Drop page, review decisions and notes, Request templates, team invitations (the invited email address) and the workspace's activity history.

Link activity. When someone opens a Delivery or downloads a file from it, we record that it happened and when. If a Delivery requires email verification, we send a one-time code to the recipient's address and store only a hash of it.

Contact form. The details and message you send are delivered to our inbox by email. They are not saved in Relayd's database.

Billing. If a workspace subscribes, Stripe processes the payment. We keep the Stripe customer and subscription identifiers and the plan; card details never reach Relayd.

Security signals. To stop automated abuse we use Cloudflare Turnstile on forms and count requests per IP address for rate limiting.

• To run the service: accounts, workspaces, links, uploads, reviews, deliveries and history.
• To send service emails: sign-in codes, password resets, team invitations, and — when a business chooses to — Request and Delivery links and reminders to its clients.
• To keep the service secure: verifying people aren't bots, rate limiting and investigating abuse.
• To bill subscriptions and answer the messages you send us.

• We don't sell personal data or use it for advertising.
• We don't use analytics or advertising trackers on the website or in the app.
• We don't read, analyse or classify the documents you exchange; they are stored and delivered as-is.

We use a small number of service providers, each only for its part of the job:

• Cloudflare — hosting (Workers), the database (D1), private document storage (R2), Turnstile bot checks and rate limiting.
• Microsoft — sending email through Microsoft 365 (Microsoft Graph).
• Stripe — subscription payments and the billing portal.
• Google and Apple — only if you choose to sign in with them.

The database and document storage are held in Cloudflare's EU jurisdiction. Requests are handled by Cloudflare's network, which serves visitors from locations near them. Emails pass through Microsoft's systems on the way to the recipient.

We only use cookies the service needs to work. There are no advertising or analytics cookies.

• A session cookie that keeps you signed in (up to 14 days).
• A security clearance cookie showing you recently passed a Turnstile check (up to 12 hours).
• A short-lived cookie that remembers the email address you're signing up or resetting with (30 minutes).
• A preference cookie remembering which workspace you last used, if you belong to more than one.
• On Deliveries that require a code, a cookie that keeps the files unlocked on that device (12 hours).

Turnstile runs Cloudflare's own checks in your browser to tell people from bots. Delivery pages also use your browser's session storage so one visit isn't counted as several opens.

• Documents, their earlier versions and activity history are kept for as long as the workspace exists. Replacing or rejecting a document keeps the earlier version on record by design.
• Closing or expiring a link stops it working; it doesn't delete the documents already exchanged.
• Sign-in, reset and Delivery access codes expire after 10 minutes; invitations after 7 days.
• Contact form messages live in our email inbox, not in the app.

There isn't yet a self-serve way to delete a workspace. To close your account or have a workspace's data deleted, contact us from the account's email address.

You can ask us for a copy of the personal data we hold about you, or ask us to correct or delete it. Business users can update their name and password in Settings at any time. If your data is in a business's workspace because you're one of its clients, that business is usually best placed to help, and we'll support it. You can also complain to the Information Commissioner's Office (ICO) in the UK.

Questions about privacy? Send us a message and choose “Security or privacy”. We'll update this page when the way Relayd handles data changes.