Legal
Privacy Policy
What we collect, what we do with it, and who else touches it. The plain-language summary is the honest short version, so read that first.
Last updated 11 August 2026
In plain language
01 Who we are and how to reach us
The service at zeypm.com is operated by [FULL_NAME], a sole trader (autónomo) registered in Spain, tax ID [NIF], address [ADDRESS]. For everything this policy covers you can write to [PRIVACY_EMAIL]. We play two roles under data protection law. For your account, billing relationship, and visits to this website, we are the data controller. For the content your organization puts into the service — including personal data about your team, collaborators and clients — your organization is the controller and we are its processor, acting under the Data Processing Agreement at /dpa.
02 The data we collect
Account data: name, email address, password (stored only as a secure hash), avatar if you add one, two-factor authentication settings, and sign-in metadata. Content data: whatever your organization creates or uploads — tasks, docs, files, messages, comments, meeting notes, recordings and transcripts, time entries, and email sent to a project’s inbound address. Billing data: your plan, subscription state and invoice history; card details are collected and held by Paddle, not by us. Technical data: IP address, browser and device information, and the server logs needed to run and secure the service. Support data: what you send us through the contact form (protected by Cloudflare Turnstile) or by email. Integration data: if your organization connects Google or GitHub, the tokens and metadata those integrations need — and nothing before you connect them.
03 Why we process it, and on what legal basis
We process account, content and billing data to perform our contract with you: operating the product, syncing it in real time, sending the transactional email the service requires, and billing your plan. We process technical data and logs under our legitimate interest in keeping the service secure, preventing abuse, and understanding aggregate usage — without any third-party analytics. AI features run only when someone in your organization invokes them, sending the relevant content to Anthropic through Cloudflare AI Gateway to produce the requested result; this is part of performing the contract, and the content is not used to train models. Optional integrations run on your consent, expressed by connecting them. Where law requires us to keep records — for example tax records connected to billing — the basis is legal obligation.
04 How long we keep it
Account data is kept while your account exists. Organization content is kept while the organization’s subscription is active; after a subscription ends, content remains exportable for [30] days and is then deleted from production systems within [60] days. Encrypted backups roll off automatically within [BACKUP_RETENTION_DAYS] days of the data’s deletion. Server and security logs are kept up to [90] days. The AI request registry — which records model, token counts and cost per AI call, not the content of the call — is kept for [12] months for billing and quota transparency. When you delete specific content in the app, it leaves production immediately (subject to the same backup roll-off), except where the trash or version-history features your organization uses deliberately retain it.
05 Subprocessors and international transfers
The full, current list of sub-processors — who they are, what they do for the service, and where they process — is published at /subprocessors and forms part of this policy. In summary: Cloudflare hosts and serves the application (its edge network operates globally), stores uploaded files, and sends our transactional email; PlanetScale hosts the database in AWS eu-west-2 (London); Anthropic provides AI features; Google and GitHub are involved only if your organization enables those integrations. Paddle processes payments as merchant of record and is an independent controller for that data. Transfers from the EEA to the United Kingdom are covered by the European Commission’s adequacy decision for the UK (valid to 27 December 2031). Where processing involves the United States, it is covered by the provider’s EU–US Data Privacy Framework certification and/or Standard Contractual Clauses in our agreement with them, as listed per provider at /subprocessors.
06 Your rights and how to exercise them
You have the rights the GDPR gives you: to access the personal data we hold about you, to correct it, to have it erased, to receive it in a portable format, to restrict or object to certain processing, and to withdraw consent where processing runs on consent. You can exercise them from your account settings where the product provides it, or by writing to [PRIVACY_EMAIL]; we respond within one month. If your data lives in an organization we process for — for example, you are a client or collaborator of one of our customers — the request is ultimately that organization’s to answer, and we will assist it or point you to it as the GDPR provides. You can complain to a supervisory authority at any time; in Spain that is the Agencia Española de Protección de Datos (aepd.es), and if you are elsewhere in the EU/EEA your local authority also works.
07 Cookies and local storage
The service uses only what it strictly needs to work, which is why there is no cookie banner: session cookies that keep you signed in (set by our authentication system), a CSRF protection token, and the security cookies Cloudflare sets to protect the service from bots and abuse. Your interface preferences — theme, density and similar — are stored in your browser’s local storage and never leave your device. There are no analytics cookies, no tracking pixels and no advertising identifiers, on this site or in the app. The contact form loads Cloudflare Turnstile, which performs its anti-spam check without tracking you across sites.
08 Security
All traffic is encrypted in transit (TLS), and data is encrypted at rest by our storage providers. Each organization’s data is isolated by access controls enforced on every request, including module-level and client-visibility rules within a project. Two-factor authentication is available on every account. Operational access to production systems is limited to the operator and protected by the same standards. If a personal data breach occurs, we will notify the competent supervisory authority within 72 hours where the GDPR requires it, and affected customers without undue delay, with what we know and what we are doing about it.
09 Changes to this policy
When this policy changes, the “Last updated” date changes with it. For material changes — new processing purposes, new categories of data, or a new sub-processor with a different footprint — we will tell you in the app or by email before the change takes effect, so you can object or export your data first. Continuing to use the service after the effective date means the updated policy applies.
Questions about any of this? Get in touch.