Privacy Policy
Version 2026-10-11
1. Who we are
Recortex is provided by KDI ApS, Danish company registration number (CVR) 46525892, Thors Allé 1, 4673 Rødvig Stevns, Denmark ("we"). Contact for anything about your personal data: hello@klamer-dueholm.com. We have not appointed a data protection officer; write to the same address.
2. Two different roles
For your account and our website, we decide why and how your personal data is processed — we are the controller. Sections 3 and 4 describe that processing.
For the business data your company connects — its shop, ad account or bookkeeping — we process it on your company's behalf, as its processor, under the Data Processing Agreement. Your company decides the legal basis for that data. Section 5 describes what it is, so you know what you are connecting.
3. Personal data we process about you
| What | Why, and on what basis | How long |
|---|---|---|
| Your email address and sign-in activity | To let you sign in. You sign in with a single-use link sent by email; an account we issue ourselves for a specific purpose, such as the test account for a platform's review of our app, signs in with a password instead, which our sign-in provider stores only in a one-way hashed form. Performing our agreement with you (GDPR art. 6(1)(b)); if your employer is our customer, our legitimate interest in providing the service they bought (art. 6(1)(f)). | While you are a member of a workspace. Without a workspace: removed in the first monthly run after 30 days without a sign-in — at the latest 65 days after the last sign-in (our own staff's accounts excepted). |
| Your acceptance of our Terms and Data Processing Agreement: the versions, the time, your email address and the workspace | To document the agreement. Legitimate interest (art. 6(1)(f)). We do not record your IP address. | An exception, kept longer than the rest of your data: at most 3 years after the customer relationship ends — the period within which claims under the agreement can be made. |
| Your workspace: the company name and that you are its owner | To set up your company's account. Performing our agreement (art. 6(1)(b)). | Until the customer relationship ends; deleted within 30 days after that. |
| Invitations: your email address, who invited you, and when the invitation was sent, used and expires | To let a customer add colleagues. Legitimate interest (art. 6(1)(f)). | Removed in the first monthly run after 30 days from when it is used or expires — at the latest 65 days after. |
| Waitlist sign-ups: your email address, the page you signed up on, the referring page if your browser shares it, the consent text and time, and a hashed (not readable) form of your IP address | To tell you when Recortex opens, if you asked us to — your consent (art. 6(1)(a)), which you can withdraw at any time by unsubscribing. The hashed IP address limits repeated sign-ups: legitimate interest (art. 6(1)(f)). Your address is not mailed until you confirm it. | Unconfirmed: at the latest 65 days after sign-up. Confirmed: until you unsubscribe, and at the latest 24 months plus 35 days after you confirmed. After you unsubscribe: at the latest 65 days. The hashed IP address: at the latest 42 days. |
| Emails you send us | To answer you. Legitimate interest (art. 6(1)(f)), or our agreement with you. | Removed in the first monthly run after 2 years from our last correspondence — at the latest 2 years plus 35 days. |
| Technical logs kept by our hosting providers: IP address, time, and the full address requested | To keep the service running and secure. Legitimate interest (art. 6(1)(f)). | Vercel: up to 30 days. Supabase: 7 days. |
A "monthly run" is a deletion we carry out on the first working day of each month; the times given are the latest it happens. Data of these kinds that existed when this version was published — including the IP addresses recorded with acceptances before 23 September 2026 — is deleted by 31 October 2026 at the latest.
Our database provider keeps daily backups for 7 days, so data we delete can remain in a backup for up to 7 days before it is gone.
4. Cookies and browser storage
We use one cookie while you are signed in: the session cookie that keeps you signed in. It is strictly necessary for a service you asked for.
We also store your light/dark theme preference in your browser's local storage. It never leaves your device.
We use no analytics, advertising or tracking cookies, and no third-party trackers.
5. Business data your company connects
Recortex reads from the systems you connect. It makes changes in two of them, only of the kinds named here, and each only if your company's owner has approved that exact change in Recortex. In Meta, it changes the daily budget of a campaign or ad set, within limits the owner has set. In Klaviyo, it moves the planned send time of a campaign that is still a draft, or sets a flow to draft so that it stops sending; it never sends or schedules a campaign and never sets anything live. It sets a flow to draft only if Klaviyo marks none of the flow's messages as transactional and every step of the flow is one Recortex can classify, and it checks this again just before making the change. Recortex then reads the result back and shows what Meta or Klaviyo holds. It never makes such a change by itself, and it changes nothing else in any connected system.
| Source | Status | What we read, and what we keep |
|---|---|---|
| Shopify | Not yet available (awaiting Shopify's approval of our app). | When available: For each order: the amounts (item prices, quantities, discounts, refunds), tax rates, currency and dates. We do not request customer names, email addresses, phone numbers, addresses or product details. We keep only totals per day; individual orders are not stored. |
| Meta (Facebook/Instagram ads) | Available only in a separate, restricted review environment we run for Meta's review of our app, connected to a test business. General access awaits Meta's approval. Connected through Facebook Login for Business: your company's administrator chooses the business portfolio and the ad account in Meta's dialog. | Ad spend and the purchase value Meta attributes to its own ads, for the whole ad account, per day. No ad-level data and no data about individual people. If your company's owner approves a budget change, we keep the record of it: the campaign or ad set, the daily budget before and after, what Meta confirmed, and the email address of the person who approved it and when. Meta requires two Page permissions together with budget changes; Recortex does not read or keep any Page content. The access Meta hands Recortex is stored encrypted. |
| Google Ads | Available to customers taking part in our Google Ads pilot. Connected by signing in with Google: a Google user who can open the ad account approves Recortex's access, and your company chooses one Google Ads account. | For the chosen account, per day: the ad cost, and the conversion value Google Ads reports — the value of every conversion the account counts, at the values set in Google Ads, not only purchases — by date of the ad interaction and by date of the conversion. Up to 16 months of history are read when the account is connected. We also keep the account's id, name, currency and time zone, and the id of the manager account it is reached through. No campaign-, ad- or keyword-level data and no data about individual people; we do not request your Google name, email address or profile. While your company chooses the account, Recortex shows the names and ids of the Google Ads accounts the signed-in Google user can open; it keeps only the one chosen. Google Ads offers a single permission, which also covers making changes; Recortex uses it only to read, and its own code refuses any other request. The access Google hands Recortex is stored encrypted. |
| Klaviyo | Available to customers taking part in our Klaviyo pilot. Connected by signing in to Klaviyo: a user of your Klaviyo account approves Recortex's access in Klaviyo's dialog, and your company chooses the metric that counts as a purchase. | For the connected account, per calendar month in the account's time zone: the conversion value and the number of conversions Klaviyo attributes to your campaigns, and the same for your flows, for the metric your company chose — Klaviyo's own attribution, as totals for all campaigns and for all flows. Up to 16 months of history are read when the account is connected. We also keep the account's id, organisation name, currency and time zone, and the chosen metric's id and name. We do not request profiles, lists, segments or message content, and no data about individual people; the figures per campaign and per flow in Klaviyo's reports are summed while reading and not stored. While your company chooses the metric, Recortex shows the names of the account's metrics; it keeps only the one chosen. Klaviyo's answers also contain information we do not ask for and do not keep — the account's sender name and email address and its postal address, and, when a change to a flow is prepared or checked, the sender, reply-to and copy addresses and subject lines of its emails. We read it while handling a request and do not store it. If your company's owner approves a change, we keep the record of it: the campaign or flow (its id and name), its status and planned send time before and after, what Klaviyo confirmed, and the email address of the person who approved it and when. Klaviyo offers no narrower permission than one that also covers editing campaigns and flows, and Recortex asks for that permission; Recortex's own code refuses every request to Klaviyo other than the reading described here and the two changes above. The access Klaviyo hands Recortex is stored encrypted. |
| e-conomic | Not yet available (awaiting e-conomic's approval of our app). | When available: only the accounts you choose, summed per month into booked marketing cost and booked revenue, plus the company name, agreement number and currency so you can see which books are connected. e-conomic's answers also contain information we do not ask for and do not keep — the signed-in user's name and email address, and the text of individual bookings, which can name people. We read it while handling a request and do not store it. You connect e-conomic by pasting the access token e-conomic shows you, so the token is never part of a web address. |
| Your Playbook answers | In use. | What you tell us about your business in your own words. Please do not enter personal data about other people there. |
The access you grant to a connected system is stored encrypted and is never visible to anyone signed in to Recortex.
Google user data. Recortex's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Ads data only to show your company its own figures and the analyses and proposed actions built on them. We do not sell it, use it for advertising, or use it to train AI models; we transfer it only to the providers in section 7 that run Recortex for us, and never to an AI service (section 6); and people at Recortex look at it only with your company's permission (for example when checking the figures with you during onboarding), to keep the service secure, or when the law requires it.
Klaviyo data. We use what we read from Klaviyo only to show your company its own figures and the analyses and proposed actions built on them. We do not sell it, use it for advertising, or use it to train AI models. Recortex currently sends none of it to an AI service (section 6); before that changes, we update this policy and tell customers as described in section 12. We transfer it only to the providers in section 7 that run Recortex for us.
6. AI
Every number, comparison and proposed action in Recortex is computed by Recortex's own rules. We use one AI service, and only to put some of those results into plain language.
Anthropic (Claude)
Once Shopify can be connected, Anthropic will receive, for recommendations built on your Shopify figures: your Playbook answers, the daily totals the recommendation concerns, and the action Recortex has already computed. It receives nothing from Google Ads, Klaviyo or e-conomic — no figures and nothing calculated from them — and no figures from Meta. Recommendations that rest on those figures are worded by Recortex's own fixed templates, and the software enforces this. One thing derived from Meta can reach it: when a recommendation built on other figures proposes changing your ad spend, and only Meta's ad spend is measured, the AI service may see the size of that change as a percentage of it — never an amount. When Google Ads' spend is part of the measured ad spend, such a recommendation is worded by the templates too. In the restricted review environment for Meta (section 5), no AI service is used at all. Before anything is sent, Recortex checks the text for patterns such as email addresses and identification numbers and refuses to send it if it finds one.
Anthropic processes this as our sub-processor under its commercial terms and data processing addendum. It stores the data in the United States and may process it in the United States, Europe, Asia and Australia; the transfer outside the EU/EEA is covered by the EU Standard Contractual Clauses in that addendum. Anthropic does not train its models on it and deletes it within 30 days — unless its automated safety systems flag it, in which case it can be kept for up to two years.
We use no other AI service on your data. Before we add one, we update this policy and tell customers as described in section 12.
7. Where your data is stored, and who processes it
| Provider | What for | Location |
|---|---|---|
| Supabase | Database, encrypted store for access credentials, sign-in and sign-in emails | Database: Frankfurt, Germany (EU) |
| Supabase | Background processing (reading connected systems, preparing recommendations) | Supabase Edge Functions, which read and write the database in Frankfurt; Supabase may run them in the region nearest to where they are started. In the restricted review environment for Meta (section 5), this runs as a Vercel Function in Frankfurt instead |
| Vercel | Website and application; in the restricted review environment for Meta, also the background processing that reads Meta | Application functions: Frankfurt, Germany (EU); requests pass through Vercel's global network |
| Anthropic | Plain-language wording of recommendations (section 6) | Stored in the United States; may be processed in the United States, Europe, Asia and Australia |
Anthropic stores what it receives in the United States under the EU Standard Contractual Clauses. Supabase and Vercel keep the data in Frankfurt; both are US companies, and their data processing agreements, which include the EU Standard Contractual Clauses, cover any access from outside the EU/EEA. The systems you connect (Shopify, Meta, Google Ads, Klaviyo, e-conomic) are your company's own providers, not ours.
8. How long we keep business data
- While your company is a customer, the daily and monthly figures Recortex computes from connected systems are kept for 24 months, for history, tracking and analysis, and deleted once they are older.
- When the customer relationship ends, everything attributable to the customer is deleted within 30 days — carried out by us when the relationship ends, not in a monthly run. The one exception is the record that the customer accepted our Terms and Data Processing Agreement (section 3).
- The record of an approved Meta budget change or Klaviyo change is kept while your company is a customer, as the account of what was approved and done, and is deleted with the rest when the relationship ends.
The following applies to Meta, Google Ads and Klaviyo now, and to Shopify and e-conomic from the day each becomes available:
- A connection error or expired access does not end anything: the figures already collected are kept, and your company can reconnect.
- When your company disconnects a system, Recortex deletes its access at once and stops reading. The figures already collected stay under the 24-month rule unless your company asks us to delete them sooner, or the platform's terms require earlier deletion — in which case we follow those terms. For Google Ads, Recortex also asks Google to revoke the access; if Google does not confirm it, Recortex says so and you can remove the access in your Google Account. For Klaviyo, Recortex also asks Klaviyo to revoke the access; if Klaviyo does not confirm it, Recortex says so and you can remove Recortex in Klaviyo under Integrations.
- When Recortex is uninstalled in Shopify, its access to the store is deleted at once, and the store's data is deleted when Shopify asks us to (48 hours after the uninstall) and in any case within 30 days, as Shopify's terms require.
9. Your rights, and how to have data deleted
Under the GDPR you have the right to access your personal data; to have it corrected or erased; to restrict or object to its processing; to receive it in a portable format; and, where processing is based on your consent, to withdraw that consent at any time. Email us (hello@klamer-dueholm.com) to use any of these rights. Where we process data on a customer's behalf, we pass your request to that customer and help them answer it.
Deleting data from a connected system (for example Meta or Shopify) — for Shopify and e-conomic once they are available: disconnect it on the Connections page — Recortex deletes its access at once and stops reading — and email us asking for the data already collected from it to be deleted. We confirm when it is done. Removing Recortex's access in the other system (for example in Meta's business settings, in your Google Account under third-party connections, in Klaviyo under Integrations, or uninstalling Recortex in Shopify) also stops all reading.
You can complain to the Danish Data Protection Agency (Datatilsynet), datatilsynet.dk.
10. Security
- All connections to Recortex are encrypted (HTTPS/TLS).
- Access credentials for connected systems are stored encrypted in a separate store that only the service itself can read; they are never shown to anyone signed in.
- Each workspace can see only its own data. The database itself enforces this, not only the application.
- Recortex only reads from the systems you connect, with two exceptions, each only after your company's owner has approved that exact change (section 5): in Meta, the daily budget of a campaign or ad set, within the limits the owner has set; in Klaviyo, the planned send time of a draft campaign, or a flow set to draft. It changes nothing else.
11. What Recortex does not do
We do not sell personal data or share it for advertising, do not build profiles of individual people, make no automated decisions about individual people, and do not use your data to train AI models.
12. Changes to this policy
When this policy changes, the version above changes with it. We tell each workspace owner by email about material changes — a new purpose, a new kind of data, a new provider that processes your data, or a longer retention period — at least 30 days before they take effect.