This page explains how to have your Klirry account and everything Klirry holds about it deleted, including any data that came from your store or from Meta (Facebook) ads. It is the "Data Deletion Instructions" page referred to in our Meta app settings. Privacy contact: privacy@klirry.com.
Delete your account yourself
You do not need to contact us. If you are the account owner:
1. Sign in at klirry.com. 2. Open Settings → Billing. 3. In the Close account section, choose Close account, then type the account name and your password in the dialog and confirm.
There is no retention offer or extra step. Your account is closed immediately and a deletion request is created. This also works during the free trial, and it is also your request to switch to another provider (EU Data Act, Art. 25).
What happens next
- Day 0 — account closed. You are signed out everywhere, every stored credential for your store and ad accounts (including any Meta access token) is erased, and all syncing stops. The retrieval period starts.
- Retrieval period — at least 30 days. The account owner can still sign in. A closed account shows one page, with the date the data is deleted, buttons to download everything as JSON or CSV, a button to reopen the account and a sign-out button; nothing else works while the account is closed. The file list is on the data export format page. For an account that is still open the same download is under Settings → Export your data. We email the owner when the account is closed and once more in the last 7 days before the deletion. The same period applies to a free trial that is never paid: it is deleted on day 51 after the account was opened (30 days after the trial ends), and we email you first. An account paused for non-payment has 60 days from the pause, with the export open, before its data is deleted automatically (we email you before that too). If you change your mind, use Reopen the account on that page (or write to privacy@klirry.com) and the deletion is cancelled; you then reconnect your store and ad accounts, because the erased credentials are not restored.
- After the retrieval period — permanent deletion. Every table holding your data is erased: orders, ad spend, cost settings, connections and their stored credentials, users, and everything derived from them, including anything that came from Meta. A verification step then confirms nothing remains. For a Shopify store, deletion is completed within 30 days of the redact request Shopify sends after uninstall.
- Confirmation. We email the owner's address a deletion confirmation with a certificate reference. The certificate is anonymised: it holds a one-way hash, not your identity.
What is kept after deletion
Nothing else survives except the rows below, each with its own retention time and legal basis. This is the same table as in the Privacy Policy (section 6) and the DPA (section 7.2).
| Data | Retention | Legal basis |
|---|---|---|
| Customer data while the account exists (orders, order lines, ad spend, costs, connections, users, settings, reports) | For as long as the account exists | Contract; for Order Data the Customer's instruction as controller (GDPR Art. 28) |
| Customer data after cancellation, after a trial that is never paid, or after a pause for non-payment | Retrieval period with full JSON/CSV export, then hard deletion confirmed by email: after cancellation at least 30 days; after a trial that is never paid 30 days from the trial end (day 51 after the account was opened); after a pause for non-payment 60 days from the pause (day 7 after the first failed payment) | EU Data Act Art. 25(2); GDPR Art. 28(3)(g) |
| Shopify store data after the app is uninstalled (shop/redact) | Deleted within 30 days of the redact request | Shopify API Terms 6.2.3 |
| Own invoices, credit notes and accounting records, including the VIES result and the location evidence behind each invoice | 7 years after the end of the financial year | Bokföringslagen (1999:1078) 7 kap. 2 §; GDPR Art. 6(1)(c) and 17(3)(b) |
| VAT records for the One-Stop Shop (OSS) scheme | 10 years after the end of the transaction year | Mervärdesskattelagen (2023:200); GDPR Art. 6(1)(c) |
| Acceptance evidence: terms version, time, account, accepting user, acceptance method | 10 years from the acceptance (the general limitation period), pseudonymised once the account is deleted | GDPR Art. 6(1)(f) and 5(2): proof of the agreement in a legal claim |
| Audit log of security-relevant actions | While the account exists; after deletion 6 months, pseudonymised, then deleted | GDPR Art. 6(1)(f): security, fraud prevention, legal claims |
| Keyed HMAC identifier used to detect trial abuse (not reversible without the key; pseudonymised, not anonymous). It blocks a second trial only when the earlier trial was never paid | 12 months from the first trial start | GDPR Art. 6(1)(f): preventing repeated free trials |
| Support correspondence (emails between a customer and Klirry support) | 12 months after the last message in the conversation | GDPR Art. 6(1)(f): answering follow-up questions and defending a claim; deleted after that |
| Email suppression list (an address that bounced, complained or unsubscribed; the address only, with no link to an account) | No fixed end: kept so the address is never mailed again, until the owner asks for removal | GDPR Art. 6(1)(f); ePrivacy and Marknadsföringslagen (2008:486) 19 § |
| Deletion certificates (date and row counts, with a hash in place of the account) | 3 years | GDPR Art. 5(2) and 17: proof that deletion took place |
| Meta data deletion requests (random confirmation code, a keyed hash of Meta's user id, status and dates; no name or email) | 3 years | GDPR Art. 5(2) and 17: proof that the deletion Meta forwarded took place |
| Queued transactional mail jobs in the job queue (recipient address and the values filled into the message) | A sent mail: 1 hour, and the values are cleared the moment it is sent. A mail that failed for good: the values are cleared at the last attempt and the job is kept at most 7 days | GDPR Art. 6(1)(b) and (f): delivering the message and diagnosing a failed delivery |
| Keyed HMAC of a carrier tracking number on an order | 180 days after the order date | Processor: Customer's instruction (carrier invoice matching) |
| Newsletter subscriptions | Until unsubscribe; an unsubscribed address stays on the suppression list; an unconfirmed subscription is deleted after 30 days | GDPR Art. 6(1)(a) consent; Marknadsföringslagen 19 § |
| Website analytics (only after the visitor's consent) | 13 months | GDPR Art. 6(1)(a) consent; ePrivacy |
| Error reports (Sentry) | At most 30 days | GDPR Art. 6(1)(f): keeping the service working |
| Encrypted database backups | Pre-release dumps: 14 days. A nightly off-site copy is not yet in operation and will keep at most 30 days. Deleted data drops out of backups within that time | GDPR Art. 32: availability and recovery |
| The record of a deletion request (status and the address the confirmation was sent to) | 7 days after the deletion is confirmed by email; the proof that lasts is the deletion certificate (3 years, no personal data) | GDPR Art. 6(1)(f): showing the customer that the deletion ran |
| Password-reset, email-verification and invitation tokens (hashed; an invitation also holds the invitee email address), and the sign-in links and sessions of affiliate partners (hashed) | 7 days after the token expired or was used | GDPR Art. 6(1)(f): security of sign-in and answering "my link expired" questions |
| Log of the events Stripe sent (event id, type, a payload stripped of personal data), used to ignore duplicates | 90 days after receipt | GDPR Art. 6(1)(f): processing each billing event once and diagnosing failures |
| A referral click on a partner link that no signup followed (partner and time only; no visitor identifier) | 120 days after the click. A click that led to a signup becomes an anonymous count for the partner once the account is deleted | GDPR Art. 6(1)(f) and Art. 5(1)(e): crediting a partner inside the 90-day attribution window |
| Contact details of an affiliate partner (name or label, contact address, payout method) | While the partner agreement runs; erased 12 months after the partner was suspended or, if never activated, after the last change. Payout records follow the invoices row | GDPR Art. 6(1)(b) the partner agreement; Art. 6(1)(f) the fraud-review period afterwards |
| Background jobs that failed for good (tenant and connection ids and the error text), kept for inspection | 30 days after the failure (mail jobs: at most 7 days, see the mail queue row) | GDPR Art. 6(1)(f): diagnosing and replaying a failed job |
| IP address inside a rate-limit counter key (Redis), to slow down abuse of sign-in and the API | 2 minutes after the last request; counters for second-factor attempts 30 minutes | GDPR Art. 6(1)(f): protecting accounts against guessing |
| Application and proxy logs on the server (request path, status, timing; secrets and personal data are scrubbed before logging) | Rotated by size, not by time: at most 250 MB per container and 1 GB of host journal; older lines are overwritten. Error detail beyond that lives in error monitoring (30 days) | GDPR Art. 6(1)(f) and Art. 32: operating and securing the service |
Removed Klirry from your Meta account?
If you remove Klirry in your Meta (Facebook) account settings and ask Meta to delete your data, Meta sends us a signed deletion request. We then erase, for the Meta user it names, the stored access token and everything that came from Meta for that connection: ad spend, ad status, decision cards and attribution matches for those ads. The connection stays visible, disconnected and without credentials, until you delete it or your account. Meta shows you a link to a status page, https://klirry.com/legal/data-deletion/status?code=<your code>, which says whether the request is received, in progress or completed. It shows nothing personal. The rest of your Klirry account, including orders from your store, stays until you delete the account as described above.
Only want to remove Meta access?
Open Connections, choose your Meta ads connection and disconnect it. Klirry stops syncing from that account. You can also revoke Klirry's access in your Meta account's own settings at any time. Data already synced stays in your Klirry account until you delete the account as described above.
Cannot sign in, or not the owner?
Email privacy@klirry.com from the address on the account and ask for deletion. We start the same process once we have confirmed the request comes from the account owner.