Seyuna Privacy Policy
Payments in the United States and Canada are processed by Moneris. Standard Stripe Billing handles payments in other supported countries. Stripe Tax calculates tax for both, and Seyuna remains the seller.
Last updated: 2026-10-24
Seyuna is operated by Seyuna Inc., a federal corporation incorporated under the Canada Business Corporations Act, corporation no. 1412077-9.
1. About this Policy and the defined terms we use
This Privacy Policy explains how Seyuna Inc. (“Seyuna”, “we”, “us”, “our”) collects, uses, discloses, retains, transfers, and protects personal information when you use our Services. It applies worldwide to everyone who interacts with us, and is written to meet our obligations under:
- the Personal Information Protection and Electronic Documents Act (PIPEDA) (Canada);
- the EU General Data Protection Regulation (GDPR);
- the UK GDPR and the Data Protection Act 2018;
- the ePrivacy Directive (EU cookie and electronic-communications rules); and
- US state privacy laws, including the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA) (applied on a forward-looking basis).
Throughout this Policy:
- “Customer” means the account holder, the person or organization that signs up for Seyuna to build and host one or more sites (also referred to as a “builder”).
- “End User” means a visitor to, or user of, a Customer’s Tenant App.
- “Tenant App” means a site hosted by Seyuna on behalf of a Customer.
- “Services” means the Seyuna AI website builder, the public hosting platform, domain registration and related reseller services, billing, and all associated websites, dashboards, and APIs.
- “AI Output” means generated source code, site structure, copy, design specifications, domain-specific language (“DSL”), or other output produced by the AI builder from Customer prompts, instructions, and inputs.
- “Personal information” / “personal data” carries the meaning given under the applicable law listed above.
This Policy works alongside our Terms of Service, Acceptable Use Policy, Data Processing Agreement, Sub-Processor List, and DMCA / Copyright Policy. Where we process personal data on a Customer’s behalf as a processor, the Data Processing Agreement governs and prevails over this Policy in the event of a conflict for that processing.
2. Who we are: the organization accountable for your personal information
Seyuna is operated by Seyuna Inc., a federal corporation incorporated under the Canada Business Corporations Act, corporation no. 1412077-9.
Mailing and registered address:
Seyuna Inc. 7030 Woodbine Ave, Suite 500 Markham, Ontario, L3R 6G2, Canada
Accountable individual (PIPEDA Principle 4.1). Seyuna has designated a Privacy Officer who is accountable for our compliance with this Policy and applicable privacy law. You can reach the Privacy Officer at:
Privacy Officer Email: privacy@seyuna.com Seyuna Inc., 7030 Woodbine Ave, Suite 500, Markham, Ontario, L3R 6G2, Canada
The Privacy Officer is the accountable individual under PIPEDA Principle 4.1 and is your primary point of contact for any question, request, or complaint about how Seyuna handles personal information.
Our EU and UK Article 27 representative contact details appear in Section 17.
3. Our two roles: when we are a controller and when we are a processor (the double layer)
Seyuna processes personal information in two distinct platform roles, and your rights and our obligations differ depending on which applies. This distinction is central to how the Services work, because Seyuna is the host of record for public Tenant Apps that may contain user-generated content.
Domain registration has a separate registrar-reseller allocation: Name.com, Inc. is the controller of domain registration data, and Seyuna acts as a processor for that data. That domain-specific role is described in Section 4.3 and Section 6.
3.1 Seyuna as controller (GDPR Art. 4(7) / PIPEDA “organization”)
When we decide why and how personal information is processed, we act as a controller. This includes:
- the personal information of Customers, the people who create Seyuna accounts, build Tenant Apps, and pay us (account, billing, support, and security data);
- our own marketing, analytics, security, and corporate operations; and
- statutory and safety obligations we carry as host of record (for example, abuse handling and DMCA processing).
For this controller-layer processing, this Privacy Policy is the governing notice.
3.2 Seyuna as processor (GDPR Art. 4(8) / PIPEDA agent) for Customer/End-User data
When a Customer builds and operates a Tenant App, the Customer is the controller of the personal information that Tenant App collects from its End Users (for example, the contents of a contact form on the Customer’s site, or accounts the Customer’s site creates for its own End Users). Seyuna hosts and processes that data on the Customer’s instructions, as a processor / service provider.
For this processor-layer processing:
- the Customer (not Seyuna) is responsible for providing its own privacy notice to its End Users, for establishing a lawful basis, and for responding to End-User rights requests;
- Seyuna’s handling is governed by the Data Processing Agreement, which forms part of our Terms of Service; and
- if you are an End User of a Tenant App and you want to exercise your rights over data the Tenant App holds about you, please contact the Customer who operates that site in the first instance. We will assist that Customer in responding, and we will route requests we receive to the relevant Customer where we can identify them.
End-User notice. Seyuna does not control, and is generally not aware of, what personal information an individual Customer chooses to collect through its Tenant App. The Customer is the controller of that information.
A narrow but important exception applies to safety and unlawful-content processing (abuse and DMCA handling): for those purposes Seyuna acts as an independent controller because we are legally required to, regardless of any Customer instruction.
4. The personal information we collect
4.1 Information you provide when you create and use an account (Customer data)
| Category | Examples |
|---|---|
| Account / identity data | Full name and email address. We collect your self-declared age and the time you complete your signup profile to check that you meet our minimum age of 18; we do not collect your date of birth or ask for your country of residence during signup. Billing country and address details are collected separately when you set up billing, as described below. Sign-in is passwordless: we use one-time email verification codes, optional social sign-in, and passkeys, so we do not store an account password. Existing email sign-in links may remain valid until they expire. If you enable two-factor authentication, we store your TOTP secret and encrypted backup codes. |
| OAuth / federated sign-in tokens | Where you connect a third-party account (for example, a Git provider or a single-sign-on identity provider), we store the OAuth access/refresh tokens and basic profile identifiers needed to operate the connection. |
| Prompts, instructions, and design DSL | The prompts you submit to the AI builder, the generated design specification / domain-specific language (“DSL”), AI Output, site content you create or upload, and the configuration of your Tenant Apps. |
| Uploaded media | Images, documents, and other files you upload to build or populate a Tenant App. |
| Billing metadata | Plan, subscription status, billing country, tax status, GST/HST applicability, invoice and receipt records, partial card data (such as the last four digits and card brand) and payment-method tokens returned by our payment processors, and transaction history. Card details are entered on the payment processor’s hosted surfaces; Seyuna does not store full payment-card numbers or card security codes (CVV). Payment data is handled by our payment processors (Moneris for the US/Canada; Stripe for other supported countries) and by Stripe Tax for tax calculations (see Section 6). |
| Support and communications | The contents of your messages to us, including abuse, security, legal, and DMCA correspondence. |
4.2 Information we collect automatically (technical and session data)
| Category | Examples |
|---|---|
| Session and security data | IP address, user-agent string, device and browser characteristics, timestamps, and authentication/session identifiers, collected to keep you signed in, secure the account, and protect the platform. |
| Bot-defence and integrity signals | Signals generated by Cloudflare Turnstile and our edge security to distinguish humans from automated abuse. |
| Operational logs | Request, error, security, and audit logs generated as you use the Services, including logs needed for abuse handling, security monitoring, and incident response. |
| Essential cookies | A small number of strictly necessary cookies (session, authentication, and Turnstile). See Section 10. |
| API / connected-client (MCP) data | Where you connect a third-party client (for example, an AI assistant) through our OAuth-based API or MCP interface: client registration details, authorization codes and access tokens, granted scopes, and a one-way hashed form of the connecting IP address used for rate limiting (the raw IP address is not stored or logged for this purpose). |
4.3 Domain registration data (special handling)
When you register, transfer, or renew a domain through Seyuna, we collect the registration data required to provision the domain: the registrant’s first and last name, optional organization name, postal address, city, state/province/region, postal code, country, email, and phone number. Under the ICANN Registration Data Policy (effective 21 August 2025), this registrant contact data is also used for the administrative, technical, and billing contacts for the domain. We collect this data so that you (the registrant), and not Seyuna’s own account, are recorded as the registrant of any domain you register through us.
Data minimization. We collect only the fields the registrar (Name.com) requires to register the domain, validate the registration data, and meet ICANN policy. We do not collect additional registrant data beyond this set, and we transmit it only to Name.com over an authenticated connection to give effect to your registration. We do not log the field values of your registrant contact data.
Registrant email verification. ICANN policy and the Registrar Accreditation Agreement (RAA) WHOIS Accuracy Program require the registrant email to be verified. After registration, a verification message is sent to the registrant email on file. If the registrant data is inaccurate or the email is not verified, the domain may be suspended; you must correct or verify registration data within fifteen (15) days of a request. Your Seyuna account provides a way to see an unverified-registrant state and to resend the verification email so your domain is not suspended.
Seyuna resells domains through Name.com, Inc. under Name.com’s API Reseller Program. Name.com is the ICANN-accredited registrar. Seyuna is a reseller and is not ICANN-accredited. As stated in the mandatory clause in Section 6, Name.com, Inc. is the controller of domain registration data, and Seyuna acts as a processor for that data. Seyuna’s Privacy Officer (privacy@seyuna.com) is Seyuna’s designated data-protection contact for matters concerning domain registration data, including for communications with Name.com.
4.4 Information from End Users (processor layer)
As described in Section 3.2, Tenant Apps may collect personal information from End Users (for example, form submissions, accounts, uploads, or analytics the Customer configures). Seyuna processes that data on the Customer’s behalf and does not determine its purposes, except for the safety and unlawful-content processing for which we are legally responsible as host of record.
5. Why we use your information, and our lawful basis
The table below states, for each purpose, what we do and the lawful basis we rely on under the GDPR/UK GDPR (Art. 6), together with the PIPEDA basis (which is consent, express or implied, with limited exceptions permitted by law).
| Purpose | What this covers | GDPR/UK GDPR Art. 6 basis | PIPEDA basis |
|---|---|---|---|
| Provide the Services | Create and run your account, operate the AI builder, host your Tenant Apps, process your prompts/DSL, generate AI Output, and serve your sites to End Users. | Art. 6(1)(b): performance of a contract. | Consent (given by signing up and using the Services). |
| Billing, tax, and accounting | Process payments, issue invoices/receipts, apply and remit GST/HST and other taxes, and keep statutory financial records. | Art. 6(1)(b) (contract) and Art. 6(1)(c) (legal obligation, e.g. tax law). | Consent; statutory financial-record obligations. |
| Security, fraud and abuse prevention | Authentication, session protection, bot defence (Turnstile), abuse detection, sanctions and eligibility screening, and platform integrity. | Art. 6(1)(f): legitimate interests in securing the Services; Art. 6(1)(c) where law requires. | Consent / legitimate-business purposes permitted under PIPEDA. |
| Safety and unlawful-content handling | Removing illegal content, abuse handling, DMCA processing, and preserving related data under legal hold where required by law. | Art. 6(1)(c) (legal obligation) and Art. 6(1)(f) / Art. 6(1)(e) (public-interest grounds). | Permitted disclosures under PIPEDA (including disclosures required by law and to protect against unlawful activity). |
| Service communications | Account, security, billing, legal, and transactional notices. | Art. 6(1)(b) (contract) and Art. 6(1)(f). | Implied consent for transactional messages. |
| Marketing communications | Optional product news and offers, only where permitted (see CASL/marketing statement in Section 13). | Art. 6(1)(a): consent (and Art. 6(1)(f) for limited existing-customer messaging where lawful). | Express consent under CASL for commercial electronic messages, subject to permitted exceptions. |
| Product improvement and analytics | Aggregated, de-identified service metrics and reliability monitoring. | Art. 6(1)(f): legitimate interests. | Consent / legitimate-business purposes. |
| AI model training (code and structure only) | Train, develop, and improve Seyuna’s own AI models and Services using the frontend and backend code and structure of hosted Tenant Apps, including Seyuna-generated code and first-party Customer-modified or Customer-authored code. This excludes third-party libraries, packages, dependencies, and other code identifiable as third-party components, as well as text content, media files, Customer data, End-User data, and personal data; Seyuna scrubs personal data from code before training. There is no opt-out for that non-personal code and structure (subject to the right to object, Section 9). | Art. 6(1)(f): legitimate interests under the GDPR/UK GDPR, not consent; legitimate interests under the Swiss FADP where applicable. | Consent, as an identified purpose accepted through the Terms of Service and this Policy. |
| Substantiating our own claims | Keeping records that adequately and properly substantiate any performance or marketing claim we make. | Art. 6(1)(c) and Art. 6(1)(f). | Consent / legal obligation. |
| Legal, corporate, and dispute purposes | Comply with law, enforce our terms, establish/exercise/defend legal claims, and handle corporate transactions. | Art. 6(1)(c) and Art. 6(1)(f). | Permitted disclosures under PIPEDA. |
Substantiation note (Canada). Under the Competition Act’s private right of action for deceptive marketing (in force 20 June 2025), any performance or marketing claim we make must be supported by adequate and proper substantiation before the claim is made. We retain the records needed to meet this standard.
Where we rely on legitimate interests, you may object as described in Section 9. Where we rely on consent, you may withdraw it at any time (subject to legal or contractual limits), and we will tell you the consequences of doing so.
6. Recipients and sub-processors
We share personal information only as needed to run the Services and as described here. We do not sell personal information, and we do not “share” it for cross-context behavioural advertising as those terms are defined under the CCPA/CPRA.
We use the following categories of service providers and sub-processors. The current, itemized list (including each provider’s role, location, and the safeguards that apply) is maintained at the Sub-Processor List.
- Cloud hosting and edge platform: Cloudflare, Inc. (Workers, Workers-for-Platforms, R2 object storage, D1, CDN, DNS, WAF/DDoS, and bot mitigation (Turnstile)) to run and serve the Services and Tenant Apps.
- Database: Neon, Inc. (Neon Postgres) for managed PostgreSQL database services.
- AI model provider: Anthropic, PBC for AI model inference on Customer prompts, builder inputs, generated output, and associated request metadata. Anthropic does not train its models on Seyuna’s commercial-tier data under the applicable commercial terms.
- Transactional email: Postmark (operated by ActiveCampaign, LLC / Wildbit) for account, security, billing, and service notifications.
- Source-code mirroring: GitHub, Inc. (a Microsoft company), where you enable the optional GitHub sync feature, for hosting a mirror of your project’s source code.
- Optional sign-in providers: GitHub, Google, and Microsoft, where you choose to sign in with them; each acts as an independent controller of its own identity service, and we store the resulting connection tokens (see the Sub-Processor List).
- Payments and tax: Moneris for Customers in Canada and the United States, Stripe Billing for other supported countries, and Stripe Tax for tax calculations. Seyuna remains the seller.
- Domain registration: Name.com, Inc. (ICANN-accredited registrar) under its API Reseller Program.
Some recipients are not Article 28 sub-processors for every purpose. They may act as independent controllers or statutory recipients for limited purposes, including payment processing and domain registration. These include Moneris, Stripe, Name.com, Inc., and law enforcement, government, and other authorities, as required by applicable law.
Mandatory clause: domain registration data. Name.com, Inc. is the controller of domain registration data, and Seyuna acts as a processor for that data. As the ICANN-accredited registrar, Name.com determines the purposes and means of processing the registration data it is required to collect, validate, escrow, and (where applicable) publish or disclose under ICANN policy. Seyuna, as a reseller and processor, captures the registrant contact data you provide on your instruction and transmits it to Name.com (and, as required, to registry operators and to the global domain-name system) over an authenticated connection so the domain can be created and maintained. This processing is governed by ICANN policy, including the ICANN Registration Data Policy (effective 21 August 2025), the Registration Data Reminder Policy (RDRP), the RAA WHOIS Accuracy Program (under which inaccurate or unverified registrant data must be corrected or verified within 15 days or the domain may be suspended), and, for transfers, use of a Transfer Authorization Code (TAC). Seyuna’s Privacy Officer (privacy@seyuna.com) is Seyuna’s designated data-protection contact to Name.com for matters concerning domain registration data. Where Seyuna offers domain privacy / ID Protection, see Section 8.4. Domain privacy / ID Protection is not offered at launch; the conditional terms above apply only if and when Seyuna introduces it.
Sub-processor changes. We will give Customers at least 30 days’ advance notice before a new sub-processor that processes Customer/End-User personal data begins, and Customers will have a 14-day window to object on reasonable data-protection grounds, as set out in the Data Processing Agreement.
We may also disclose personal information to professional advisers, to authorities where required by law (see Section 8.5), and to a successor entity in a merger, acquisition, financing, or sale of assets, subject to appropriate confidentiality protections.
7. International data transfers
Seyuna operates globally and uses cloud infrastructure that may store and process personal information in Canada, the United States, the European Union, the United Kingdom, and elsewhere.
7.1 Inbound transfers into Canada (EU/UK -> Canada)
Canada benefits from a renewed EU adequacy decision (adopted 15 January 2024). Transfers of personal data from the EU/EEA into Canada to Seyuna therefore do not require Standard Contractual Clauses (SCCs): the European Commission has recognized that the part of Canadian law applicable to the commercial private sector provides an adequate level of protection. The United Kingdom maintains its own separate adequacy basis recognizing Canada for transfers of UK personal data, so transfers from the UK into Canada likewise do not require the UK International Data Transfer Addendum (UK IDTA).
7.2 Onward transfers from the EU/UK to the United States and other countries
Our principal cross-border exposure is onward transfers, for example, where personal data moves from our Canadian or EU operations to providers operating in the United States, and Seyuna is the data exporter. For those onward transfers we rely on:
- the EU-US Data Privacy Framework (DPF) and its UK extension, where the receiving provider is DPF-certified, as recorded in our Sub-Processor List; and
- Standard Contractual Clauses (SCCs) and, for UK data, the UK International Data Transfer Addendum (UK IDTA), together with a transfer impact assessment, only where a provider is not DPF-certified or where a specific processing activity is not covered by that provider’s certification.
Stripe processes billing data for supported countries outside the United States and Canada and tax-calculation data for both payment providers. The safeguards described above apply according to the provider’s role in the relevant processing activity.
7.3 Safeguards on request
You may request a copy of the relevant transfer safeguards (for example, the SCCs or details of a provider’s DPF certification) by contacting the Privacy Officer at privacy@seyuna.com. See also the Data Processing Agreement and Sub-Processor List.
7.4 EU data residency for Tenant App data
For Customers whose organization has a validated billing or residency country in the EU/EEA, the dedicated database and object storage for their Tenant Apps are provisioned in the European Union (currently an EU database region, with object storage subject to an EU jurisdiction restriction). This placement is enforced at provisioning time and fails closed: if EU placement cannot be confirmed, the Tenant App is not provisioned in the United States instead. This commitment applies to Tenant App data at rest. Platform account, billing, consent, and control-plane records (Section 4.1) and transient processing of request traffic at the network edge nearest a visitor are handled as described in Sections 7.1 and 7.2 and may occur outside the EU.
8. Specific disclosures
8.1 Where the Services are available, and the Quebec exclusion
Account sign-up and billing for the Services are available from the United States and Canada and from all countries supported by our payment processors, except for sanctioned or embargoed jurisdictions, China, certain high-data-localization markets, and the Province of Quebec, which are excluded. This availability restriction concerns account creation and billing: Tenant Apps that Seyuna hosts remain reachable on the public internet globally, except where a jurisdiction is hard-blocked at the network edge (currently comprehensively sanctioned or embargoed jurisdictions). You are responsible for complying with the laws that apply to you where you are located.
Wherever you are, we apply a single global privacy baseline (the GDPR/UK GDPR and PIPEDA high-water mark) as the floor for every market we serve, and we honour the rights that apply to you under your local law and cannot be waived. Quebec residents are blocked at signup by a geographic/residency check, and our Terms of Service reflect this exclusion. If you are a Quebec resident, the Services are not currently available to you.
8.2 Account-holder age (18+)
The Services are intended only for individuals who are at least 18 years old, and accounts may only be opened by such individuals. We do not knowingly collect personal information from anyone under 18 as a Customer. If you believe a person under 18 has provided us personal information as a Customer, contact privacy@seyuna.com and we will take appropriate steps to delete it. Obligations for End Users of a Tenant App are the responsibility of the Customer that operates the site.
8.3 No statement of internal thresholds
This Policy describes how we protect personal information for everyone, regardless of our size. We do not condition the rights and protections in this Policy on any internal assessment of our scale or revenue.
8.4 Domain privacy / ID Protection
Where Seyuna offers domain privacy / ID Protection (for example, Name.com ID Protection), enabling it can replace certain public-facing registration contact details with proxy details, subject to registrar and registry rules. This feature is described conditionally because it is not assumed to be enabled at launch. Domain privacy / ID Protection is not offered at launch; the conditional terms above apply only if and when Seyuna introduces it.
8.5 Foreign-government and lawful access
Your personal information may be processed in the United States and in other countries, and may be subject to access by foreign courts, law-enforcement, regulatory, or national-security authorities under the laws of those countries, including, in the United States, the CLOUD Act and similar legal mechanisms. This can occur even where the data originated in Canada or the EU/UK, because some of our service providers are subject to those laws. Where we are legally required to disclose personal information, we will do so to the extent required, and (where we are lawfully permitted) we will seek to limit the disclosure and to notify affected individuals or Customers. This disclosure is provided in line with guidance from the Office of the Privacy Commissioner of Canada on personal information processed across borders.
9. Your privacy rights and how to exercise them
Depending on where you live and which law applies, you have some or all of the following rights over personal information for which Seyuna is the controller:
- Access: obtain confirmation of, and a copy of, the personal information we hold about you.
- Rectification / correction: have inaccurate or incomplete information corrected.
- Erasure / deletion: have personal information deleted, subject to legal limits (see Section 9.3).
- Restriction and objection: restrict, or object to, certain processing, including processing based on legitimate interests and direct marketing.
- Portability: receive certain information in a portable, machine-readable format.
- Withdraw consent: withdraw consent at any time where we rely on consent, without affecting prior lawful processing.
- CCPA/CPRA rights (US): to know, access, correct, delete, and to opt out of “sale” or “sharing” of personal information. As stated in Section 6, Seyuna does not sell or share personal information as those terms are defined by the CCPA/CPRA, so there is nothing to opt out of; we will honour a valid request regardless. You also have the right not to be discriminated against for exercising your rights. See Section 9.4 for how we honour the Global Privacy Control (GPC) opt-out preference signal automatically.
We do not make decisions producing legal or similarly significant effects about you based solely on automated processing within the meaning of Article 22 GDPR / UK GDPR. Automated security, fraud, abuse, and content-safety systems may assist review, flag content, or trigger protective controls, but consequential action is handled through the operational processes described in our legal policies and the applicable law.
9.1 How to make a request (DSAR route)
Submit a data-subject access or rights request (“DSAR”) by emailing the Privacy Officer at privacy@seyuna.com, or by writing to Seyuna Inc., 7030 Woodbine Ave, Suite 500, Markham, Ontario, L3R 6G2, Canada. We will verify your identity before acting, and we will respond within the timeframe required by the applicable law, for example one calendar month under the GDPR/UK GDPR, 30 days under PIPEDA (extendable under PIPEDA where permitted), and 45 days under the CCPA/CPRA. You may use an authorized agent where the law allows. There is normally no fee, though the law permits a reasonable fee or refusal for manifestly unfounded or excessive requests.
9.2 End-User requests (processor layer)
If you are an End User of a Tenant App, exercise your rights with the Customer that operates that site (see Section 3.2). If you contact us, we will, where we can, forward your request to the relevant Customer and assist them in responding.
9.3 Limits
Rights are subject to legal exceptions, for example, where we must keep information to comply with law, to establish or defend legal claims, to protect others, or because another controller such as Name.com or Stripe must handle the request for data it controls. Where required by law, we remove illegal content, preserve related data under legal hold (which can override a deletion request), and report to the relevant authorities, and we may be unable to notify you where the law prohibits it.
9.4 “Do Not Sell or Share” and the Global Privacy Control (GPC)
We do not sell or share your personal information as those terms are defined by the CCPA/CPRA and other US state privacy laws, and we do not use it for cross-context behavioural (“targeted”) advertising. We use only strictly necessary technologies (see Section 10): there is no ad tech, advertising pixel, or third-party analytics tag, so there is no “sale” or “share” to opt out of today.
Even so, we honour the Global Privacy Control (GPC) automatically. When your browser or a privacy extension sends the Sec-GPC opt-out preference signal, we treat it as a valid request to opt out of any “sale” or “sharing” of personal information under the CCPA/CPRA and the Colorado and Connecticut privacy laws, and we record that opt-out durably for your account (or, if you are not signed in, via a strictly first-party preference marker that contains no personal information). This means that if we ever introduce any practice that would qualify as a “sale” or “share,” your recorded GPC opt-out is already in force and will be respected without any further action by you. You do not need to do anything: enabling GPC in your browser or extension is sufficient. If you are signed in, your “Do Not Sell or Share” status is shown in your account privacy settings.
You may also exercise this right (and any other right above) at any time via the DSAR route in Section 9.1.
10. Cookies and similar technologies
At launch, Seyuna uses essential (strictly necessary) cookies only: specifically session, authentication, and Cloudflare Turnstile cookies needed to sign you in, keep the Services secure, and defend against automated abuse. Because these are strictly necessary, they do not require consent under the ePrivacy Directive, and we do not currently display a cookie consent banner.
We do not currently use analytics, advertising, or other non-essential cookies or tags. If we later add any non-essential or analytics technology, we will first deploy a compliant cookie consent banner and obtain consent where required, and we will publish a separate, detailed Cookie Policy at that time. (Adding any non-essential or analytics tag is the trigger that requires the consent banner.)
11. AI-processing disclosures
The AI website builder processes the prompts, instructions, and design DSL you submit, together with content you provide, in order to generate and modify your Tenant Apps. This processing relies on performance of our contract with you (Art. 6(1)(b)) and your consent under PIPEDA. AI generation may involve our AI sub-processors listed in the Sub-Processor List. Variable AI token consumption and related billing changes are addressed in our Terms of Service.
AI training. Anthropic does not train its models on Seyuna’s commercial-tier data under the applicable commercial terms. Seyuna uses the frontend and backend code and structure of hosted Tenant Apps, including both Seyuna-generated code and first-party Customer-modified or Customer-authored code, to train, develop, and improve Seyuna’s own AI models and the Services, including the website-builder. This training is on code and structure only. It excludes third-party libraries, packages, dependencies, and other code identifiable as third-party components, as well as text content, media files, Customer data, End-User data, and personal information. Seyuna scrubs personal information from the code before training, and the training pipeline is designed so that personal information does not enter the training set; any personal information that incidentally remains is processed on the basis of Seyuna’s legitimate interests, as described in the DPA and GDPR Addendum. This use of non-personal code and structure is part of the Service, and there is no opt-out for that non-personal code and structure. Where the GDPR, UK GDPR, or Swiss FADP applies, the lawful basis is Seyuna’s legitimate interests in developing and improving its AI models and Services, not consent; under PIPEDA, this use is among the identified purposes you consent to by accepting the Terms of Service and this Policy. This does not limit your right to object described in Section 9.
12. Data retention
We keep personal information only as long as needed for the purposes described in this Policy, to provide the Services, and to meet legal, tax, accounting, security, domain-registration, and dispute-resolution requirements; after that, we delete or de-identify it. Specific periods are set out in our retention schedule, available on request from the Privacy Officer and summarized in the Data Processing Agreement. Key periods include:
- Account and Tenant App data: retained for the life of the account and for a limited wind-down period after closure, then deleted or de-identified.
- AI builder prompts, inputs, and AI Output: retained while needed to provide the Services and, where tied to a saved project, retained with that project unless deleted earlier by you or required to be retained for legal, safety, or dispute purposes.
- Billing, tax, and accounting records: retained for 7 years where Seyuna keeps those records. Payment providers may retain records separately under their own applicable obligations.
- Domain registration and registrant-consent records: retained for 7 years where required for domain-registration, registrar, dispute, or contractual purposes.
- Security and operational logs: retained for a limited period for security monitoring and incident response, subject to longer legal, abuse, or breach-record needs.
- Data-breach records: under PIPEDA, we keep records of every breach of security safeguards for 24 months, whether or not the breach met the real-risk-of-significant-harm threshold.
- Data under legal hold: retained for the period that applicable law requires, unless a longer judicial order or legal process applies.
When we delete live data, backup or disaster-recovery copies may persist for a limited period until they expire through the ordinary backup lifecycle. We restrict use of those copies and do not restore deleted data to active systems except where legally required or necessary for security, continuity, or dispute purposes.
13. Marketing emails (CASL) and your choices
We send transactional and service messages (account, security, billing, legal, and similar notices) as part of providing the Services; these are not marketing, and you cannot opt out of them while you have an account.
For commercial electronic messages (marketing), we comply with Canada’s Anti-Spam Legislation (CASL): we send marketing email only where we have the required express or implied consent, we clearly identify ourselves (Seyuna Inc., with our mailing address), and we include a working unsubscribe mechanism in every message that takes effect promptly. You can opt out of marketing at any time using the unsubscribe link or by emailing privacy@seyuna.com. Where the GDPR/UK GDPR applies, our marketing relies on your consent (Art. 6(1)(a)).
14. How we protect your information
We use technical and organizational safeguards appropriate to the sensitivity of the information, including encryption in transit, access controls, authentication and session protections, edge security and bot defence (Turnstile), logging and monitoring, legal-hold controls for restricted evidence, and least-privilege access for staff and sub-processors. No method of transmission or storage is perfectly secure, but we work to protect personal information against loss, theft, and unauthorized access, use, or disclosure.
Seyuna is a pre-certification startup. This Policy does not claim that Seyuna has obtained SOC 2, ISO 27001, PCI DSS certification, or any similar third-party certification unless a separate published document expressly says so after it has been obtained.
15. Data-breach commitment
We maintain an incident-response process to detect, contain, and assess security incidents. If a breach of security safeguards creates a real risk of significant harm to affected individuals, we will report it to the Office of the Privacy Commissioner of Canada and notify affected individuals as soon as feasible, consistent with PIPEDA’s breach-notification requirements, and we will notify relevant authorities and individuals as required under the GDPR/UK GDPR (including notifying a competent supervisory authority within 72 hours where required). Where we act as a processor for a Customer, we will notify the affected Customer without undue delay so they can meet their own obligations, as set out in the Data Processing Agreement. As noted in Section 12, we keep records of all breaches for 24 months.
16. How to raise a concern or complaint
If you have a question, concern, or complaint about how Seyuna handles personal information, please contact the Privacy Officer first at privacy@seyuna.com (or by mail at Seyuna Inc., 7030 Woodbine Ave, Suite 500, Markham, Ontario, L3R 6G2, Canada). We will investigate and respond.
If you are not satisfied with our response, you may also contact the relevant regulator:
- Canada: the Office of the Privacy Commissioner of Canada (OPC).
- United Kingdom: the Information Commissioner’s Office (ICO).
- European Union / EEA: your local Data Protection Authority (DPA), or the lead supervisory authority for our EU operations.
17. EU and UK representatives (GDPR Article 27)
Where required, Seyuna will appoint representatives in the EU and the UK under Article 27 of the GDPR and UK GDPR. EU and UK individuals may contact our representative on any matter relating to the processing of their personal data, in addition to contacting our Privacy Officer, once those details are published.
- EU representative (GDPR Art. 27): [TO BE COMPLETED BEFORE PUBLICATION: appoint EU GDPR Article 27 representative and insert name, address, and contact details]
- UK representative (UK GDPR Art. 27): [TO BE COMPLETED BEFORE PUBLICATION: appoint UK GDPR Article 27 representative and insert name, address, and contact details]
In the meantime, all individuals may contact our Privacy Officer at privacy@seyuna.com.
18. Governing law and your statutory rights
This Policy is governed by the laws of the Province of Ontario and the federal laws of Canada applicable there, including PIPEDA and the Consumer Protection Act, 2002 (Ontario), without prejudice to mandatory consumer and data-protection rights you may have where you live. Nothing in this Policy removes or limits the mandatory statutory rights of EU/UK residents under the GDPR, UK GDPR, and Data Protection Act 2018, or the rights of US state-law residents under laws such as the CCPA/CPRA.
19. Changes to this Policy
We may update this Policy from time to time. When we make material changes, we will update the “Last updated” date above and, where appropriate, provide additional notice (for example, by email or an in-product notice). Your continued use of the Services after an update takes effect means you have read the revised Policy.
Seyuna is operated by Seyuna Inc., a federal corporation incorporated under the Canada Business Corporations Act, corporation no. 1412077-9. GST/HST registration / Business Number 719107609RT0001.