Privacy policy
Last updated: November 17, 2026
This policy explains what NCT HOLDING collects when you use Canopus, why, on what basis, for how long, and what you can do about it. It is written to be read, not endured.
Canopus is a growth manager for SaaS products that are already up and running. A team of agents reads a founder's product, works out who it is for and drafts campaigns that the founder approves before anything is sent; Canopus then sends those emails itself, from the founder's domain. This document therefore describes two different relationships: what we do with your data, and what we do on your instruction with your customers' data.
Data controller
NCT HOLDING, a SASU with a share capital of €1,000, 57 avenue du Maréchal Juin, 64200 Biarritz, France, registered under number 131 634 651 (RCS Bayonne), is the data controller for the data described here, except for the section Data you bring with you. For any question, or to exercise the rights below, write to contact@canopushq.io.
For the data a founder brings into the service about their own customers, we act as a processor and the founder is the controller. That is the subject of the section Data you bring with you and of the data processing agreement.
What we collect about you
| Data | Why | Legal basis | Kept for | | --- | --- | --- | --- | | Email address, name | To create and identify your account | Performance of the contract | While the account exists | | Password (hashed, never stored in clear) | To sign you in | Performance of the contract | While the account exists | | Profile received from Google or GitHub, if you sign in that way: email address, name, picture, account identifier | To sign you in without a password | Performance of the contract | While the account exists | | Sessions: IP address, browser, last activity | To show you your active sessions and let you revoke them | Performance of the contract | 30 days after the session ends | | Security events: sign-ins, password and two-factor changes, role changes | To let you audit your account, to investigate abuse | Legitimate interest: the security of the service | 12 months | | Acceptance of the terms: version accepted, date, IP address, browser | To prove the contract | Legitimate interest: proof of the contract | While the account exists | | Billing data: plan, subscription status, invoices | To charge you, to meet our accounting obligations | Legal obligation | 10 years | | Identity of the subscribing business: legal name, country, SIREN or registration number, VAT number, declaration of acting for a business | To check that the buyer is a business, apply the right VAT, issue invoices | Performance of the contract and legal obligation | While the account exists, then 10 years on invoices | | Content you create: organizations, profile, files, strategies, campaigns | To provide the service | Performance of the contract | While the account exists | | Error reports | To fix failures | Legitimate interest: the proper running of the service | 90 days |
Creating an account requires an email address and a name; without them the service cannot work. Everything else is optional or produced by your use.
We do not buy data about you, and we do not sell or rent yours.
Signing in with Google or GitHub
If you choose to sign in with Google or GitHub, that provider sends us the items listed above, and nothing else: we ask for no access to your files, your repositories or your contacts. Google and GitHub process your sign-in as separate controllers, under their own privacy policies.
Error reports and session replay
When an error occurs in your browser, Sentry records a report and a replay of the last seconds of the session that led to it. Nothing is recorded when there is no error. The replay masks all text and all inputs and blocks images and videos: it shows the shape of the page and the clicks, not what you read or type. Email and IP addresses are scrubbed from reports before they are sent, and your identity in them is reduced to an identifier.
The beta list
Before its public opening, the service was in private beta and kept a list of the people who asked to be told when it opened. That list was closed at the opening, as this policy said it would be: its entries are erased, the hashed IP addresses with them. Someone who has since created an account is covered by the rest of this policy, like any account holder.
Data you bring with you
Once in the service, Canopus processes data about your customers and prospects. For all of this data we act on your instruction and under the data processing agreement: you decide what is connected, imported, captured and sent.
Connected tools
| Tool | What is read | What is never read |
| --- | --- | --- |
| Stripe | Your customers and their subscriptions: the customer id, the email address and name on the customer record, the plan, the amount, the status and the start date | No card number, no bank details, nothing else in your payment data. The connected key is a restricted key that needs only two read permissions, customers and subscriptions |
| PostHog | Aggregate product numbers: how many people appeared per day, retention and event volumes, as query results | No individual person. The queries return counts and dates, never a row per person |
The Stripe figures are also written onto the contacts in the CRM: five fields whose source is Stripe, matched on the Stripe customer id. Every other field on a contact is yours and is never overwritten.
Every key is encrypted at rest with AES-256-GCM, bound cryptographically to the organization it belongs to, and readable only by the two server modules that need it. Removing a connector deletes the key immediately, in the same request: no grace period and no archived copy.
Your CRM, your imports and your capture forms
The contacts in your CRM come from what you enter, what you import, Stripe, and the capture forms you place on your own site. A capture form sends Canopus the email address and the fields you have set up in it; it is protected by a key specific to your organization, a honeypot field against bots and rate limiting. Informing the people who fill it in, and collecting their consent where the law requires it, is up to you.
When your product tells us that a person has deleted their account with you
(the user.deleted event), their records are erased. We keep a fingerprint of
their address, not the address itself, to prove that the erasure took place.
What we read on your site
When you ask for an analysis, the server reads your landing page and up to twelve pages that depend on it, as well as the competitor sites you name. What is kept is facts about each page: the title, the tags, the outline, an excerpt, the calls to action, the link graph. The HTML is discarded and never stored, and no screenshot is taken.
What is sent to the agents
The agents run on Anthropic's models. What reaches a prompt is the product brief written from your site, your answers to the strategy interview, aggregated figures about your customer base, and the ICP you validated. Aggregated means a count, a median, a percentile or a distribution: "38 customers, median $84 a month". No individual contact, no email address and no name from your CRM is put into a prompt, and neither is any card data or credential. That boundary sits in the query layer rather than in a prompt template, so it applies by construction to every agent, existing or to come.
Anthropic is a sub-processor, listed with the others at /legal/subprocessors. Data sent through the API is not used to train its models. Prompts and answers are not written to our logs either: about a model call we record the agent, the prompt version, the model, the token count, the cost and the duration.
The emails Canopus sends for you
Canopus sends your emails itself, from the domain you verified by publishing the DNS records we show you. Sending goes through Amazon SES, in the Paris region. There are three kinds of sending:
- campaigns, which you approve one by one;
- sequences, a series of messages you approve once, which then go out on the schedule and conditions you set, and stop as soon as a person unsubscribes, bounces a message or reaches the sequence's goal;
- transactional emails, which your own product sends through the Canopus API (sign-up confirmation, password reset, receipts).
You are the controller for these recipients and we process them on your instruction. Nothing is sent as a campaign or a sequence until you have approved it, and approval is refused without a sender address and a postal identity.
Every commercial message carries a one-click unsubscribe that complies with RFC 8058, so the mail client's unsubscribe button stops the sequence. Unsubscribing removes the person from every future campaign and stops the one they have started.
What we record per recipient:
| Event | Why | | --- | --- | | A message being sent | To count it against your quota and show you what went out | | Delivery to the recipient's server | To show you what arrived | | A bounce, with its type and the reason given by the server | To stop writing to an address that does not exist, to protect your domain's reputation | | A complaint, when the recipient marks the message as spam | To stop writing to them, to protect your domain's reputation | | A click on a link in the message | To show you what works and to attribute sign-ups | | The unsubscribe and its date | To make it effective and to be able to prove it |
We place no tracking pixel and do not record opens. A click is tied to a destination stored on the campaign, never to a destination carried in the URL. Of a transactional email, we keep the recipient, the sender, the subject and the status, never the body.
The suppression list. An address that has hard bounced, complained or unsubscribed is added to a suppression list specific to your organization, and Canopus then refuses to write to it. An unsubscribe blocks only commercial messages; a hard bounce or a complaint blocks everything. When a contact is erased, their unsubscribe goes with them, but a hard bounce or a complaint stays on the list: that is what protects your domain's reputation if the address is imported again. We also monitor each domain's bounce and complaint rates over seven days, and a domain that exceeds the threshold is suspended until it has been reviewed.
Payment details
No card number reaches our servers. Payments are processed by Stripe, which is the controller for that data. We keep only the identifiers Stripe sends us and the state of your subscription.
When you subscribe, the SIREN of a French business is checked against the French State's public Recherche d'entreprises API (data.gouv.fr), and a European VAT number against the European Commission's VIES system. Only the number looked up is sent to them. The legal name, the SIREN and the VAT number are also held on your customer record at Stripe, which issues the invoices.
Analytics
Traffic measurement is aggregated and cookie-less: no identifier is stored on your device and no profile is built. If that were to change, this page would change first, and your consent would be collected before anything non-essential is stored.
Who else sees your data
We use a small number of sub-processors, each bound by a data processing agreement: hosting, database, email sending, payments, rate limiting, error reporting, AI models and anti-bot checks. The full list, with what each one receives and where it processes, is at /legal/subprocessors.
We give 30 days' notice before adding a sub-processor.
Where your data lives
Databases, file storage, email sending and application functions are in the European Union. Several of our providers are companies incorporated in the United States, even when they host in Europe, and some process in the United States. Where a transfer outside the European Economic Area takes place, it relies on the EU-US Data Privacy Framework where the company is certified under it, and otherwise on the European Commission's standard contractual clauses.
Your rights
The GDPR gives you the right to access your data, to correct it, to erase it, to restrict its processing, to object to processing based on our legitimate interest, to receive it in a portable format, and to withdraw a consent you have given at any time, without affecting what was done before. You may also set instructions on what happens to your data after your death (Article 85 of the French Data Protection Act).
No decision producing legal effects concerning you is taken solely on the basis of automated processing: the agents propose, and a human approves.
Two of these rights are self-service, from Settings → Data & privacy: Export my data produces a usable copy, and Delete my account schedules erasure. Deletion is not instant: the account is deactivated immediately and purged 30 days later, a window during which a compromised account can still be recovered. Records the law requires us to keep, such as invoices, survive that purge.
If your data is in the service because a founder using it put it there, they are the controller and the request goes to them. Write to us anyway if you cannot reach them: we will point you to the right person and help them answer you.
For anything else, write to contact@canopushq.io. We answer within one month. If our answer does not satisfy you, you may complain to your supervisory authority, in France the CNIL.
Cookies
See the cookie policy.
Changes
Any material change is announced by email to every account holder at least 30 days before it takes effect. The date at the top of this page always reflects the version in force.