Privacy policy

Kundr is a customer system (CRM) sold only to businesses. This policy covers three groups: visitors to kundr.io, our customers' staff who use Kundr, and the data Kundr processes on behalf of its customers, including data from Google, Meta, TikTok, LinkedIn, Snapchat and Pinterest. How to delete data: Deleting data. Contact: Contact us.

Who is responsible

Kundr is provided by KUNDR AS (org. no. 924 527 854), Oslo, Norway. For visitors to kundr.io and for the user accounts of our customers' staff, KUNDR AS is the data controller. For data we process on behalf of a customer, the customer is the controller and KUNDR AS is the processor, under the data processing agreement with that customer. Privacy questions: personvern@kundr.io.

1. Visitors to kundr.io

• Visiting kundr.io: IP address and browser in server logs, to run and secure the site (legitimate interest, GDPR art. 6(1)(f)). Deleted within 30 days.
• Demo bookings and enquiries: name, email, chosen time and optionally phone and message, plus IP address and timestamp to prevent abuse. Name and email are required to book; the rest is optional. Used to hold and follow up the demo (art. 6(1)(b), and (f) for the IP address). Deleted 12 months after last contact if you do not become a customer.
• Email news: only with your consent (art. 6(1)(a) and the Norwegian Marketing Control Act § 15). You can unsubscribe in every email. Proof of consent is kept for 12 months after you unsubscribe.
• Cookies and visitor counts: kundr.io sets no cookies and uses no third-party analytics or advertising tools. We count visits ourselves without storing IP addresses and keep only anonymous daily totals. With Do Not Track or Global Privacy Control turned on, you are not counted. The booking window stores only what is necessary in your browser.

2. Staff who use Kundr

Our customers' staff sign in to their business's own Kundr instance. This processing is necessary to provide the service the customer has agreed with us (art. 6(1)(b) and (f)).

• User account: name, email address and role, sign-in links by email, the time, IP address and browser at sign-in, and a log of actions in Kundr, for security and accountability. Retention: when a user is removed, the user account is deleted within 30 days. The action log is kept for 12 months and then deleted.
• When a staff member connects an account: when a staff member connects their business's own Google, Meta, TikTok, LinkedIn, Snapchat or Pinterest account to Kundr, Kundr stores the access tokens (access token and refresh token), the permissions (scopes) granted, the IDs and names of the connected accounts (for example ad account ID, Page ID, Instagram account ID or Google Ads customer ID), the connection status and when it was made.
• Why: only to read and write what the customer has asked for, described in part 3.
• Security: access tokens are stored encrypted on the server and never sent to the browser.
• Retention: until the account is disconnected. Kundr then deletes the access token at once and, where the platform supports it, also revokes it at the platform. See Deleting data.

3. Data we process on behalf of our customers

When a customer connects its own business accounts to Kundr, Kundr processes the data on behalf of the customer, which is the controller. Kundr only reaches the accounts the customer has given access to, acts only on instructions from the customer's staff, and never publishes or spends money without a staff member's approval. The data is stored in the customer's own database at Supabase in the EU (Ireland), separate from other customers' data.

Google

• Google Ads (read): after the customer clicks “Connect Google Ads”, signs in with Google and chooses an Ads account, Kundr reads cost, impressions, clicks, conversions and conversion value per campaign and day, plus the names and IDs of the account and its campaigns. The figures are aggregated per campaign. We read no information about the individual people who saw or clicked the ads. Kundr never changes campaigns, budgets, ads or settings in Google Ads.
• Gmail in Innboks: if the customer connects a Gmail mailbox to Innboks (Kundr's shared inbox), Kundr reads the messages in the mailbox's inbox and sent mail (gmail.readonly), so staff can read and answer enquiries from their own customers in one place, and sends the replies a staff member writes (gmail.send). Kundr does not read drafts, spam or trash, and only sends when a staff member sends.
• Google Calendar: Kundr checks that the chosen calendar belongs to the admin and can create Google Meet links, reads only whether times are free or busy, and creates, updates and deletes events for bookings made in Kundr: title, time, attendees' name and email as given in the booking, and the Google Meet link. Kundr does not read the content of other events.
• Why: to show the customer what its ad spend returns in bookings, members and revenue, to let staff handle email in one place, and to avoid double bookings. Google data is used for nothing else.
• Retention: reporting figures and email for as long as the business is a customer, or shorter if the customer asks. The access token is deleted when the customer disconnects.
• Revoking access: disconnect in Kundr, or remove Kundr's access at myaccount.google.com/permissions.

Kundr'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. The use of information received from Google Workspace scopes (Gmail and Calendar) will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements. Kundr does not sell Google user data, does not use it for advertising, does not transfer it to anyone except as needed to provide the features above, and does not let any person read it without the customer's consent, unless needed for security or required by law. Kundr does not use data from Google Workspace APIs to develop, improve or train generalised (non-personalised) AI or machine learning models.

Meta (Facebook and Instagram)

• Access: the customer gives Kundr access to its own ad accounts, Facebook Pages and Instagram professional accounts, in its own Meta business portfolio (system user) or by signing in with Facebook.
• Publishing ads and posts: when the customer approves an ad or a post in Kundr, Kundr uploads the image or video to the customer's own account, creates the campaign, ad set and ad, or publishes the post, and changes budgets or pauses ads on the customer's instruction.
• Reading ad results: campaigns, ad sets, ads and their creatives (text, images and videos); daily results per ad (spend, impressions, reach, clicks, video views, conversions); results broken down by placement, region, age group and gender, which Meta only provides in aggregate; and the ad account's change history, including the name of the person who made each change.
• Organic posts: the posts on the customer's Facebook Page and Instagram account, their metrics (such as reach, likes, comments and saves) and follower counts.
• Innboks: if the customer turns on Innboks, Messenger and Instagram conversations with the customer and comments on its posts and ads, with the sender's name and profile ID as Meta provides them. Staff can reply from Kundr; Kundr sends a reply only when a staff member sends it.
• Customer lists and conversions: if the customer asks, Kundr uploads a list of its members to its own ad account as a Custom Audience, and can send bookings and new memberships to its own Meta pixel (Conversions API). Contact details are hashed (SHA-256) before they leave Kundr.
• Storage: ad images and videos are kept in the customer's private storage area; thumbnails of public organic posts in a public one. The ads and posts themselves stay on Meta.
• Revoking access: remove Kundr's system user or app in your Meta business settings, or remove Kundr under Business integrations in Facebook.

TikTok

• Access: an admin connects the customer's own TikTok account and ad accounts by signing in with TikTok (OAuth).
• Publishing: a video the admin has prepared, published to the customer's own account only after the admin has previewed it and chosen the privacy, interaction and commercial-content settings themselves, or sent to the account's TikTok inbox as a draft. On approval, Kundr uploads ad creatives and creates or changes ads in the customer's own ad account, and can send bookings and memberships to the customer's own TikTok pixel (Events API) with contact details hashed.
• Reading: the account's display name and profile picture, the status and metrics of videos posted through Kundr, and for ad accounts the campaigns, ad groups, ads and aggregated daily results per ad. We do not read followers, private messages or information about individual viewers.
• Revoking access: disconnect in Kundr, or remove Kundr under apps and services in the TikTok account's security settings.

LinkedIn

• Access: an admin connects by signing in with LinkedIn (OAuth).
• Publishing: posts the admin writes or approves, to the Company Page they choose, and on approval campaigns and creatives in the customer's own ad account. Kundr can send bookings and memberships to the customer's own LinkedIn conversion tracking (Conversions API) with contact details hashed. Kundr never posts to members' personal profiles.
• Reading: the Pages the member administers, the Page's posts with aggregate engagement (impressions, reactions, number of comments), Page statistics, and for ad accounts the campaign groups, campaigns, creatives and aggregated daily analytics per creative. Kundr does not store commenters' profile data.
• Revoking access: disconnect in Kundr, or remove Kundr under Permitted services in LinkedIn's settings.

Snapchat

• Access: an admin connects the customer's own Snapchat ad accounts and public profile by signing in with Snapchat (OAuth).
• Publishing: ads and posts the customer has approved, in its own ad account and profile.
• Reading: campaigns, ads and creatives, and aggregated daily results per ad (spend, impressions, clicks, conversions). We read no information about the individual people who saw the ads.
• Revoking access: disconnect in Kundr, or remove Kundr under connected apps in your Snapchat settings. Snap also processes data under Snap's Privacy Policy.

Pinterest

• Access: an admin connects the customer's own Pinterest business account and ad accounts by signing in with Pinterest (OAuth).
• Publishing: Pins and ads the customer has approved, in its own account.
• Reading: boards, Pins, campaigns and ads, and aggregated daily results per ad (spend, impressions, clicks, saves, conversions). Pinterest data is used only for the customer's own analytics and trains no AI models.
• Revoking access: disconnect in Kundr, or remove Kundr under apps in your Pinterest security settings.

Messages from our customers' customers (Innboks)

Innboks collects enquiries to the customer from email (Gmail, Microsoft 365 or IMAP), Messenger, Instagram and comments. Kundr stores the message, the sender's name and contact details or profile ID, and the replies staff send, for as long as the customer decides, under the data processing agreement. If you have sent a message to a business that uses Kundr, that business is the controller. Please contact the business for access or deletion. If you write to us, we pass the request on to the right business.

AI-assisted drafts

When a staff member asks Kundr to draft a post, an ad or a reply, or uses the assistant bar, the text Kundr needs, including from emails and messages, is sent to an AI service. Names, email addresses, phone numbers and handles are replaced with placeholders first. Kundr uses three routes, all in the US: OpenRouter, where Kundr only uses model providers marked for zero data retention, and which itself does not store prompts and responses; SubQ, which deletes inputs and outputs within 60 days; and TypeSafe, which does not state how long inputs are kept but says it does not train on them. See Sub-processors. Nothing is published or sent until a staff member approves it. Kundr does not use platform data to train AI models.

Applies to all platforms

• Purpose: the data is used only to provide the features above to the customer it belongs to.
• No sale or sharing: we never sell platform data, do not share it with third parties beyond our service providers, do not use it for advertising outside the customer's own accounts and do not combine it across customers.
• Retention: for as long as the business is a customer, or shorter if the customer asks. The data is deleted when the customer relationship ends, under the data processing agreement. Published content stays on the platform until the customer deletes it there.

4. Service providers and transfers

We use Vercel (hosting), Supabase (database and storage, Ireland), Resend (email), Google (email and calendar) and OpenRouter (routing of AI requests, see above). The full list is under Sub-processors. They process data only on our instructions. Transfers to the US rely on the EU Standard Contractual Clauses (SCCs) in the providers' data processing agreements, see the table. We never sell personal data and make no automated decisions about you.

Sub-processors

These providers process data on behalf of Kundr and its customers. The platforms a customer connects itself, such as Meta and Google, are described in part 3 and are not listed here.

5. Deleting data

Disconnect in Kundr

An admin at the customer opens Settings → Integrations in Kundr and chooses Disconnect next to the service. The access token, permissions and status are deleted at once, and Kundr fetches no more data. Where the platform supports it, Kundr also revokes the access at the platform.

Remove access at the platform

• Meta: remove Kundr's system user or app in your business settings, or remove Kundr under Business integrations in Facebook.
• Google: remove Kundr at myaccount.google.com/permissions.
• TikTok: remove Kundr under apps and services in the TikTok account's security settings.
• LinkedIn: remove Kundr under Permitted services.
• Snapchat and Pinterest: remove Kundr under connected apps in your account settings.

Once access is removed, Kundr can no longer read or write anything at the platform.

Ask for deletion

Disconnecting stops collection but does not delete data already fetched. To have it deleted, write to personvern@kundr.io from an admin at the customer and include:

1. the name of the business and the address of its Kundr instance (for example business.kundr.io),
2. which platforms it concerns (Meta, Google, TikTok, LinkedIn, Snapchat, Pinterest or all),
3. whether you want an export of the data before it is deleted.

How long it takes

We confirm receipt within five working days and delete the data within 30 days. We let you know by email when the deletion is done. Copies in backups are overwritten within 30 days after that.

What is deleted, and what is not

• Deleted: access tokens, account IDs, reporting figures, ads and creatives we have stored (text, images and video), posts and their metrics, and email, messages and comments from the platform, in the customer's Kundr instance.
• Not deleted by us: posts and ads published on the platform. They stay there until the customer deletes them on the platform.
• Kept by law: invoices and other records we must keep under the Norwegian Bookkeeping Act.

If you have sent a message to a business that uses Kundr, ask that business to delete it. You can also write to personvern@kundr.io and we will pass the request on to the right business and help it delete the data.

6. Your rights

You can ask for access, correction, deletion, restriction and a copy of your data, object to processing and withdraw consent. Write to personvern@kundr.io and we will reply within one month. You can also complain to Datatilsynet, the Norwegian Data Protection Authority.

7. Contact us

Company

KUNDR AS

Org. no.

924 527 854

Postal address

Pilestredet 47a, 0350 Oslo, Norway

Email

personvern@kundr.io

Website

kundr.io

Want to see Kundr? Book a demo in the calendar on the front page.

8. Changes

We update this policy when Kundr changes how data is processed, and the date at the top shows the latest change.