Data processing terms

Who does what

Your organization is the controller of the personal data it keeps in CSresults: it decides what goes in and why. We are its processor, and process that data only to provide CSresults and as your organization instructs, through how it sets up and uses the service (its settings, the integrations it connects and the emails its team sends) or in writing.

The personal data involved

• Your customers' people: names, job titles, email addresses, phone numbers and their role on the account.
• What your team records about working with them: check-ins and who attended, notes, tasks, progress updates and who they were sent to, and uploaded files.
• What people tell you through a shared plan: a score, a comment and, if they give one, their name.
• The record of your team's work: who owns each customer, and who wrote a note, held a check-in or made a change.
• Anything your organization brings in from a CRM it connects.

Each person's sign-in account (their name, email address, password, two-step sign-in and sign-in records) is not part of this. We look after it as its controller, as the Privacy Policy explains.

CSresults is not built for sensitive data such as health details, payment card numbers or government ID numbers, and the terms ask you not to store them.

What we commit to

• Purpose. We use the data only to provide CSresults to you. We do not sell it, use it for advertising or use it to train AI models. Our staff use an AI coding assistant to run the service, which can read the data while they fix a problem or help you; it is listed with the subprocessors below.
• Confidentiality. Everyone who can reach it for us is bound to keep it confidential.
• Security. We keep the measures on the security page: tenant isolation in the database, encryption in transit, two-step sign-in, an audit log, and limited staff access.
• Subprocessors. We use the subprocessors listed below. Before we add or replace one, we update this list and email your admins, so you can object.
• Requests from people. We help you answer people who ask to see, correct, export or delete their data. Much of it you can do yourself: edit or delete a contact, export everything, and every progress update carries an unsubscribe link we honor across your organization. A request that reaches us about your data is passed to you.
• Breaches. If we learn of a breach affecting your data, we tell your admins without undue delay, with what we know and what we are doing about it, and keep you updated.
• Information. We answer reasonable questions and security questionnaires about how we process your data.

Where the data is

The database, with everything stored in CSresults apart from uploaded files, is in the United States, with Supabase on Amazon Web Services in Oregon, and email is sent from the United States. Uploaded files are in Cloudflare R2, whose storage region we have not yet confirmed; ask us if you need it. The subprocessor list below gives each provider's location as far as we know it. We will sign a data processing agreement that includes the EU Standard Contractual Clauses where you need them.

Return and deletion

You can export everything at any time from Settings, Data, and delete the organization there when you are done. Its records are removed from the database within minutes and its uploaded files within about ten minutes after that. We do not keep backups we could restore your data from, so a deletion cannot be undone. Copies can remain for a time in our providers' own systems (for example the email provider's sending logs), and in the CRMs, inboxes and webhook endpoints your organization sent data to.

We keep a short record of the deletion, our internal record of the requests the organization made and the changes we made for it, counts of the emails it sent, and the addresses progress updates went to with whether each unsubscribed, so that sending limits and opt-outs keep working, as the Privacy Policy describes.

Subprocessors

• Supabase

  Purpose

  The database, sign-in, and the background functions that sync CRMs, deliver webhooks and send email.

  Data

  Everything stored in CSresults apart from uploaded files, and the records of sign-ins.

  Location

  United States: Amazon Web Services, us-west-2 (Oregon)

• Cloudflare

  Purpose

  Storage for uploaded files (R2), and the network the site is served through.

  Data

  Files your team uploads to customers; every page request passes through its network.

  Location

  Uploaded files: Cloudflare R2, storage region not yet confirmed, so ask us if you need it. Network: worldwide.

• Lovable

  Purpose

  Builds and hosts the web app, counts page visits, and captures errors in the page.

  Data

  Page addresses, the referring page, browser type and language, and error details.

  Location

  Where Lovable stores this data is not yet confirmed; ask us if you need it.

• Resend

  Purpose

  Sends email: sign-in and confirmation emails, invitations, daily and weekly summaries, and the progress updates your team sends to customers. Open and click tracking are off.

  Data

  Each recipient's email address and the content of the email, which Resend keeps in its sending logs.

  Location

  United States: us-east-1 (Virginia)

• Anthropic

  Purpose

  Claude, the AI coding assistant our staff use to build, maintain and support CSresults. The product itself sends no data to it.

  Data

  What our staff look at with it while fixing a problem or answering a support request, which can include records from the database.

  Location

  United States

• NixiHost

  Purpose

  Hosts the mailbox our support, sales, privacy and security email arrives in.

  Data

  The messages you send us and our replies.

  Location

  United States

• Google (Gmail)

  Purpose

  The mailbox our operations alerts go to: new sign-ups, requests for seats, storage or a plan, and paused email sending.

  Data

  The name and email address of whoever signed up or asked, the organization's name, and any note they added.

  Location

  Google's data centers, in the United States and elsewhere

Data goes to these services only when your organization connects them, under your own agreement with each:

• HubSpot. When an admin connects it: companies, deals, products, contacts and meetings come in; results, check-ins, progress updates, forecasts and expansion opportunities go back.
• Salesforce. When an admin installs the CSresults package: accounts, opportunities, products, contacts and events come in; results, check-ins, forecasts and expansion opportunities go back.
• Webhooks and the API. Events go to the addresses an admin adds (for example Zapier, Workato or Make), and systems holding an API key read and write through the API.
• Calendar apps. When someone subscribes to their CSresults calendar link, their calendar app (Outlook, Google Calendar, Apple Calendar) fetches it.