Privacy Policy
Effective date: 16 November 2026
This policy explains what personal data BackupLatte collects about its customers and website visitors, why, and what rights you have.
1. Who we are
The controller of the personal data described here is Stanislav Sysoiev, sole trader (CEIDG), ul. Lwowska 6G/25, 61-131 Poznań, Poland, NIP 7822934324, REGON 527330815, operating BackupLatte ("BackupLatte", "we"). Contact for any privacy matter: [email protected].
For connected workspace content, the customer normally acts as controller and we act as processor. Where the customer acts for another controller, it is the processor and we act as its subprocessor on authorized instructions. That processing is governed by our Data Processing Addendum; see section 9 if your data is in someone else's workspace.
2. What we collect, where it comes from and why
| Data | Source | Why | Legal basis (GDPR) |
|---|---|---|---|
| Account: email, password if set (stored only as a bcrypt hash), Google account ID if linked, sign-in refresh token (our database keeps only its hash), last login time | You; Google when you choose Google sign-in | Create and secure your account, sign you in | Contract (Art. 6(1)(b)) |
| Linear connection: your Linear user ID, organisation ID, name and key, OAuth access and refresh tokens (encrypted with AES-256-GCM), backup schedule and retention settings | Linear, when you connect | Connect to Linear and run the backups and restores you ask for | Contract |
| ClickUp connection: authorizing user and selected workspace IDs and names, encrypted OAuth access token, schedule and retention settings | ClickUp, when you connect | Establish and administer the requested integration | Contract for an individual customer; legitimate interest in administering an organization's account |
| Backup and restore records: time, status, size, item counts, error messages | Generated by the Service | Show your backup history, troubleshoot failures | Contract; legitimate interest in a reliable service (Art. 6(1)(f)) |
| Recorded choices: optional payment-recovery choice, notice version and grant/withdrawal times | Your separate instruction | Respect your choices and demonstrate the applicable permission | Consent where applicable; legitimate interest in recording instructions and compliance |
| Subscription: Paddle customer and subscription IDs, plan, status, billing dates, number of active users in your connected workspaces (counted via the connected platform) | Paddle; Linear or ClickUp | Enforce your plan and limits | Contract |
| Payment event records: Paddle event, transaction, subscription and customer IDs, event type and status | Paddle | Process and audit billing events | Contract; legitimate interest |
| Job diagnostics: for failed backup/restore jobs, the workspace, backup and restore IDs and the error message | Generated by the Service | Investigate and retry failures | Legitimate interest |
| Technical logs: IP address, request path, timestamps, error details | Your browser / our servers | Security, abuse prevention (rate limiting), debugging | Legitimate interest |
| Website analytics (landing page and blog, only if you agree): pages viewed, referrer, device and browser type, country and region, Google Analytics cookie identifiers | Your browser, through Google Analytics | Learn which pages help visitors, improve the site | Consent (Art. 6(1)(a)); you can withdraw it any time |
| Emails we send you: backup alerts (a backup failed or has gaps, or works again), with the workspace name and the reason; account emails with a one-time link (confirm your address, reset your password, link Google sign-in); a welcome email once you confirm your address; a confirmation of your plan, price and billing dates when a subscription starts | Generated by the Service | Tell you when your backups need attention (you can turn alerts off per workspace; they go only to a confirmed address); let you confirm your address and recover access; help you get started and confirm what you bought | Contract |
| Emails you send us | You | Answer support and legal requests | Contract / legitimate interest |
An email address and either a password or Google sign-in are required to have an account. A connection to the service you want to back up is required to make backups. Google sign-in requests only your email and Google account ID; we do not store Google access or refresh tokens or request access to Gmail, Drive or Calendar. Linking Google to an existing email account keeps the same account and data.
Payments. Paddle is our Merchant of Record and collects your name, address, payment details and tax ID at checkout as an independent controller (see Paddle's privacy notice). We never receive your full card number or security code. We deliberately do not store the payment method details (such as card brand, last four digits or expiry) or billing address that Paddle's notifications contain — we keep only the identifiers and status listed above.
Apart from Google Analytics on the landing page and the blog, used only if you agree (section 3), and Paddle Retain engagement tracking for payment recovery described below, we do not use analytics, advertising trackers or profiling, and we do not sell personal data.
ClickUp workspace content
As processor we read permitted tasks, descriptions, fields, assignees, comments/replies, checklists, workspace/member metadata, readable Doc pages as Markdown and supported ClickUp-hosted files. Doc metadata can be stored even when ClickUp refuses page content; it is not treated as a backup of that content. Page availability and known gaps are recorded separately. Snapshots, exports, original/current/prior provider-ID mappings, scoped aliases, pending creation records, skipped items and owner recovery decisions support the requested service. Raw records can contain third-party links; external file contents are not copied. ClickUp OAuth tokens are encrypted with AES-256-GCM. We do not request a ClickUp password.
Workspace-member profiles and raw workspace content described above are processed on the customer's instructions under the DPA. The account contract is not a substitute for that customer's lawful basis concerning other people. Billing uses aggregate member counts.
MCP access and activity
When you connect a Model Context Protocol (MCP) client, we store its label, identifier and redirect URLs, your granted permissions, and connection dates. We store authorization codes and tokens as hashes. We use these records to provide the access you request under the contract.
The activity log records the time, tool, outcome and relevant platform, workspace or backup identifiers. It excludes tool arguments and returned data. We keep this log for security and accountability based on our legitimate interests.
3. Cookies and browser storage
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
refresh_token | Cookie (HTTP-only) | Keeps you signed in | 7 days |
google_oauth | Cookie (HTTP-only) | Protects Google sign-in against forgery | 10 minutes |
linear_oauth | Cookie (HTTP-only) | Protects the Linear connection flow against forgery | 15 minutes |
clickup_oauth | Cookie (HTTP-only) | Protects the ClickUp authorization flow against forgery | 15 minutes |
| App theme | Local storage | Remembers System, Light or Dark chosen in the app | Until you change it or clear site data |
| ClickUp recovery decision | Session storage | Keeps the decision ID, plan/intent version and chosen action stable after a lost response | Until settled or the tab is closed |
| Payment-recovery choice | Account preference and browser state as needed | Records and applies your optional Paddle Retain choice | Decision history and notice evidence while the account exists; removed with the account, subject to the database-backup period |
| Access token | Session storage | Authenticates requests while the tab is open; usable until it expires | Until the tab is closed (the token itself expires after 15 minutes) |
| Workspace view | Local storage | Remembers whether you chose tiles or table view | Until you clear site data |
| Pending restore | Session storage | Remembers the restore you started while you connect the workspace to restore into | Until the restore starts or the tab is closed |
| Analytics choice | Local storage (landing page and blog) | Remembers whether you accepted or declined analytics | Until you change it or clear site data |
_ga, _ga_<ID> | Cookies (landing page and blog), only if you accept | Google Analytics: tell visits apart and count them | 2 years |
Necessary session and authorization items are set only for their flows, and selected preferences store a setting you chose. Optional Paddle Retain processing requires a separate opt-in; it is not included in necessary authentication or payment consent. The documentation uses no analytics.
Analytics. If Google Analytics is offered on the landing page or the blog, we ask before using it. Until you accept, Google's script is not loaded and no analytics cookie is set. While analytics is offered, you can change your choice under Cookie settings at the bottom of those pages; declining removes the analytics cookies. We do not use Google Analytics for advertising: ads personalisation and Google signals are turned off, ad-related storage stays off, and Google does not collect city-level location or detailed device data for us.
If you separately opt in to Paddle Retain, we may initialize its optional in-app recovery notifications and engagement measurement using your Paddle customer ID. We do not initialize that optional background feature before the opt-in. You can decline or withdraw it under Subscriptions → Optional payment recovery without losing checkout, subscription access or ordinary billing management.
Checkout and payment links can load Paddle.js when you request those payment flows. Paddle's processing for those flows is described in its privacy notice. Withdrawing Retain permission must stop its optional background processing, rather than only hide a reminder.
Paddle's checkout opens only when you choose a plan or follow a payment link from Paddle. Paddle may set cookies in its checkout context, such as Cloudflare's bot protection cookie __cf_bm on paddle.com (30 minutes); Paddle's privacy notice applies to them.
4. How long we keep data
- Account, connection and subscription data: while your account exists.
- Disconnected Linear workspace: we delete its tokens at once; the workspace record and its backups remain until you delete the workspace or your account, and backups expire as below.
- Backups: for the retention period you set (1–365 days, 7 by default), then deleted by a daily cleanup. Copied files are kept while at least one remaining backup contains them. A ZIP export of a backup is kept for up to 7 days, never longer than the backup. Deleting a workspace deletes its backups, files and exports from storage within 2 days.
- Payment event records: removed by the daily cleanup 90 days after they were processed, or 90 days after receipt if processing never succeeded.
- Job diagnostics: failed-job records are removed by the daily cleanup after 90 days. Our job queues also keep the last 100 finished and 100 failed jobs per queue (IDs and error messages); those of a deleted workspace are removed by an hourly cleanup, and a job still running at deletion is removed within an hour after it ends.
- Backup alert, account, welcome and subscription emails: our copy is kept 30 days after sending; one that could not be sent is dropped after 7 days. The links in account emails work for 48 hours (address confirmation) or 1 hour (password reset) and once; we keep only a hash of each link, removed 7 days after it expires.
- Support and legal correspondence: support messages are kept for 2 years after the last message in the conversation, so we can follow up on the same matter; complaints, legal notices and data-protection requests for 6 years after they are closed, the general limitation period for claims under Polish law. Support is handled through the mail provider; any additional mailbox destination or forwarding must be included in the recipient inventory before use.
- Website analytics: kept in Google Analytics for 2 months; the cookies last up to 2 years unless you decline or clear them.
- Technical logs: our servers rotate logs by size (at most 30 MB per service); older entries are overwritten and not archived. Their age therefore depends on traffic.
- Disaster-recovery copies of our database: normally about 15 days. Local copies are removed by the next daily backup run after 14 days; copies in storage expire after 14 days and Cloudflare usually removes expired objects within a day.
- Accounting records: invoices to buyers are issued and kept by Paddle as seller. Our own accounting and tax records (Paddle statements, reverse invoices, payout and transaction reports, refund and chargeback records, bank confirmations) are kept for 7 years, or longer where a specific law requires it (legal basis: Art. 6(1)(c) GDPR). They identify buyers only by Paddle identifiers and transaction details where they do so at all.
- Account deletion: email [email protected] from your account address. We first make sure no subscription or payment can continue — including a payment Paddle is still processing — then delete your account, connected workspaces, subscription records, backups, job diagnostics and queue records within 30 days. Database recovery copies containing them normally expire about 15 days later, and payment event records (IDs and status only) within 90 days. Paddle keeps its own records under its policy.
ClickUp deauthorization
Disconnecting stops access and work for that connection. Workspaces can share one authorization; its token is erased when no active workspace needs it. If ClickUp or a user deauthorizes, deactivates, uninstalls or otherwise terminates the application, affected ClickUp data and associated metadata are permanently deleted within 10 days. This includes snapshots, copied files, exports, restore records and disaster-recovery copies. The ordinary retention and database-backup periods above do not extend this deadline. We notify ClickUp of compliance as required by its Developer Terms.
Account creation, payment and ordinary retention settings do not authorize longer storage. Records that must be kept by law are limited to that separate purpose and do not justify retaining ClickUp workspace content indefinitely.
MCP activity is removed by routine cleanup after 90 days. Revoking a connection stops further access through that connection. Existing activity remains available until its retention period ends or the account is deleted, subject to the database-backup period above.
5. Who we share data with
- Service providers (processors) that run our infrastructure — see Subprocessors. They may use the data only on our instructions.
- Paddle, as the independent controller of the checkout and payment.
- Google (Google Ireland Limited, with Google LLC), which provides Google Analytics on the landing page and the blog when you accept it, and optional Google sign-in when you choose it. For Google sign-in, your browser visits Google and we exchange the authorization code with Google to verify your identity.
- Linear, which you connect: we read from and, for restores you start, write to your own Linear workspace.
- ClickUp, the service you connect, receives authorization requests and restore writes to your chosen workspace. Its own terms govern its processing. It is not a new BackupLatte subprocessor.
- Authorities or others where required by law.
MCP clients you authorize receive responses to their tool calls. Depending on the tool, responses can include workspace names and IDs, backup and restore status and coverage, and MCP activity. The client can retain information it received before you revoked access. Check the client's privacy terms and settings before connecting.
6. International transfers
Our servers are in Falkenstein, Germany, and backups are stored in a Cloudflare R2 bucket under the EU jurisdiction setting, which keeps stored objects in the EU. Other processing may happen outside the EEA: Cloudflare's network handles requests globally, and Paddle, Linear and ClickUp may process data in the UK or the US. Our email provider is Zoho Mail on Zoho's EU data centre (zoho.eu) for primary storage. EU storage does not mean all access is confined to the EU: Zoho describes support access from group companies in India under Standard Contractual Clauses in its published privacy information. You can ask us for details about the applicable processing arrangements at [email protected].
Google Analytics data may be processed in the US by Google LLC under Google's data processing terms, with the EU Standard Contractual Clauses; Google LLC is certified under the EU–US Data Privacy Framework. Backup alert emails are sent through Resend (Plus Five Five, Inc.), which processes data primarily in the USA under its data processing addendum, with the EU Standard Contractual Clauses and the EU–US Data Privacy Framework. Cloudflare's data processing addendum provides safeguards including the EU Standard Contractual Clauses and the EU–US Data Privacy Framework. See Subprocessors for provider locations and transfer safeguards. You can ask us for details at [email protected].
7. Security
Linear and ClickUp tokens are encrypted at rest; passwords and sign-in refresh tokens are stored in our database only as hashes. Connections between your browser, Cloudflare, the connected services and our storage are encrypted. Our backend does not expose ports to the internet: it is reached only through an authenticated Cloudflare tunnel, and its internal services talk over isolated private networks on the same server.
If you enable encryption with your own key, we store the public keys and their fingerprints. Your private key stays in your browser. We read workspace data while taking a backup and when you unlock stored data for restore, export or conversion back to ordinary storage. Account and workspace details, snapshot dates, sizes and record counts, file checksums, platform error messages and restore records remain outside this optional encryption. ClickUp restore records can include names of restored items and email addresses used to match users.
Temporary data keys and export passwords are encrypted under a server key held separately from the database. Restore and conversion unlocks can be used for up to 72 hours from creation. Export unlocks can be used for up to 24 hours. Encrypted copies of temporary key material can remain in database backups until those backups expire under section 4.
If a breach affects your data we will notify you and the authorities as the law requires.
8. Your rights
Under the GDPR you can request access to, correction of, deletion of, or a copy (portability) of your personal data, restrict or object to processing based on legitimate interests, and withdraw any consent. Write to [email protected]; we answer within one month. You can also complain to a supervisory authority — in Poland the President of the Personal Data Protection Office (UODO), ul. Stanisława Moniuszki 1A, 00-014 Warsaw, uodo.gov.pl — or to the authority where you live or work.
9. If your data is in someone else's backup
If you are a member of a Linear or ClickUp workspace that another person or organisation backs up with BackupLatte, the customer or the organization it acts for determines how that content is used. We process it on documented instructions. Contact that controller first where possible; we pass on requests received and assist the customer under the DPA.
10. Children
The Service is not intended for anyone under 18.
11. Changes
We will post changes here and update the effective date. For material changes we will also notify account holders by email.
Implementation of your choices
The existing infrastructure providers remain the same; ClickUp-hosted files are fetched directly from allowed hosts without an added file-conversion provider. A restore decision payload is kept in browser session storage until its outcome is known, to repeat the same decision safely after a lost response or reload. ClickUp OAuth uses a 15-minute authorization-state cookie. Optional Paddle Retain payment recovery uses a separate account permission under Subscriptions; you can withdraw it there at any time.