Introducing Creative Memory. Pluto now knows what’s inside every ad you run. Read more →

Privacy Policy

Last updated

Pluto Ads is operated by Pluto Holding ApS, a company registered in Denmark with CVR number 46452682.

Pluto Ads (“Pluto,” “we,” “us,” or “our”) is a tool for advertisers to plan, publish, manage and automate their own ads on Meta, LinkedIn and Google Ads. This Privacy Policy describes how we collect, use, store and disclose personal data when you visit our websites (including plutoads.ai and app.plutoads.ai), create an account, or use our products, APIs and services (together, the “Services”).

Please read this policy carefully. If you do not agree with it, do not use the Services or provide us with personal data. You are not legally required to provide personal data, but without it we may not be able to provide the Services.

The Services are designed for businesses, not for personal or household use. We treat the people who use them as business representatives (for example marketers, agency staff and business owners).

1. Roles: controller and processor

Privacy laws such as the GDPR and US state privacy laws distinguish between a controller (who decides why and how personal data is processed) and a processor or service provider (who processes data on a controller’s instructions).

  • Account and prospect data. Pluto is the controller of personal data about people who sign up, manage an account, visit our websites, book a call or contact us.
  • Customer data. Everything an organization puts into Pluto Ads or connects to it, including media, launches, ads, Agent chats, and the data we receive from Meta, LinkedIn, Google Ads and Pluto Profit on its behalf, is processed on behalf of that organization. For that data the organization (our customer) is the controller and Pluto is its processor or service provider, acting on its instructions and our agreement with it.

This matters most for people who are not our users: someone who comments on an advertiser’s ad or submits one of its lead forms. Their data is the advertiser’s, and the advertiser is responsible for giving them notice and for having a lawful basis to process it. If that is you, contact the advertiser first. We will help the advertiser respond, and you can also contact us (section 16).

2. Data we collect

2.1 Account data

  • Your name, email address and user ID. Sign-in is handled by WorkOS, our identity provider. If you sign in with Google or Microsoft, WorkOS passes us the name and email address that provider returns.
  • Your organizations and workspaces, roles, invitations, preferences and notification settings.
  • Your sign-in sessions, and the API keys and connected agents you create.
  • Support messages and feedback you send us.

2.2 Workspace content

  • Media you upload, such as images and videos. Media is stored in Amazon S3 in the United States, encrypted, and is never deleted automatically while your workspace exists.
  • Launches, campaigns, ad sets, ads and their copy, targeting and budgets, including drafts.
  • Comments, reactions and approvals between members and guests of a workspace.
  • Agent chats, the guidance and skills you give the Agent, and loops with their runs.
  • The results of media search and Creative Memory, which describe what is in your media so you can search it and compare it with how your ads performed.

2.3 Data from Meta

A workspace owner or admin connects Meta with Facebook Login for Business and chooses which ad accounts, Pages and Instagram accounts Pluto Ads may use. We then receive and store:

  • For the person who connected: a Meta access token (stored encrypted, never shown in the app or the API), their Meta user ID and name, and the permissions they granted.
  • Ad accounts: name, currency, time zone, status and spending limit.
  • Pages and the Instagram professional accounts linked to them: IDs, names and usernames.
  • Campaigns, ad sets, ads and ad creatives in those ad accounts: names, status, budgets, bids, schedules, targeting and thumbnails hosted by Meta.
  • Insights for those ad accounts: spend, impressions, clicks, results, actions and their values, video metrics and reach.
  • Comments on your ads, on Facebook and Instagram: the comment text, the commenter’s name (Facebook) or username (Instagram), the time, whether it is hidden, and replies. We read comments only on the posts that your ads run as, never on other posts of your Page.
  • Lead form answers: your Pages’ lead forms (name, status, language and questions), and the leads submitted through them, with their answers. Answers can include whatever the form asks, such as a name, email address or phone number. Lead answers are stored encrypted, never appear in lists, activity or notifications, can be opened only by people with edit access to the workspace, and each opening is recorded in the workspace’s activity.
  • Custom and lookalike audiences: their names, descriptions, approximate sizes and status. We never upload customer lists to Meta and never read who is in an audience.

To read comments and lead forms we use a Page access token for that one read only; Page tokens are never stored. When you publish or change ads, reply to a comment, or hide or delete one, we send what you approved to Meta.

2.4 Data from LinkedIn

A workspace owner or admin connects LinkedIn by signing in to LinkedIn and allowing access. Pluto Ads then sees the ad accounts and Pages that LinkedIn member has a role on. We receive and store:

  • For the member who connected: LinkedIn access tokens (stored encrypted, never shown in the app or the API), their LinkedIn member ID and name, and the permissions they granted.
  • Ad accounts: name, currency, status and the member’s role on each.
  • Pages: IDs, names and the member’s roles on each.
  • Campaigns, ad sets and ads in those ad accounts: names, status, budgets, bids, schedules, targeting and creatives.
  • Results for those ad accounts, such as spend, impressions, clicks, conversions and leads.
  • Lead form answers, where LinkedIn gives Pluto Ads access to them: your lead forms and the leads submitted through them, stored and protected like lead answers from Meta.
  • Comments on your ads, where LinkedIn gives Pluto Ads access to them: the comment text and the commenter’s LinkedIn ID. Commenters’ profiles (name, headline and picture) are never stored: the app reads them from LinkedIn when it shows a comment.

When you publish or change ads, we send what you approved to LinkedIn. Section 5.2 sets out how we use LinkedIn data and how long we keep it.

2.5 Data from Google Ads

A workspace owner or admin connects Google Ads by signing in with a Google Account and allowing access. Before Google’s sign-in opens, Pluto Ads shows what it will read, what it may change and how it uses the data. We ask Google for access to Google Ads, which reaches the Google Ads accounts that Google Account can use, and for the account’s email address, so the workspace can see who connected. We receive and store:

  • For the person who connected: Google access and refresh tokens (stored encrypted, never shown in the app or the API), their Google Account ID and email address, and the permissions they granted.
  • Google Ads accounts and manager accounts: IDs, names, currency, time zone, status, the manager account an account is reached through, and the person’s access to each. Nothing else is read from an account until someone in the workspace turns it on.
  • Campaigns, budgets, ad groups, ads, assets, keywords and other targeting, and labels in the accounts you turn on: their names, status, budgets, bids, targeting and settings.
  • Results for those accounts, such as cost, impressions, clicks, conversions and their values, and the search terms and keywords reports. Search terms are totals of what people searched for, as Google reports them. Google never tells us who searched.
  • Change history: the changes Google Ads records in those accounts, with the old and new values, the tool used and the email address of the person who made each change, as Google reports it.
  • Lead form answers: the lead forms in those accounts and the leads submitted through them, stored and protected like lead answers from Meta.
  • Audiences, conversion actions and Google’s recommendations for those accounts, when you choose targeting or goals or look at recommendations.

Pluto Ads changes something in Google Ads only when someone in your workspace, or a loop they turned on, asks for it: it creates campaigns, ad groups, ads, assets and keywords, and changes their status, budgets and bids. We send Google only what was approved. Section 5.3 sets out how we use Google user data and how long we keep it.

2.6 Data from Pluto Profit

Pluto Profit is a profit analytics product also operated by Pluto Holding ApS. If a workspace owner or admin connects a Pluto Profit store, we store access tokens (encrypted) and the store’s name, Shopify domain and currency, and we read the store’s profit, order, product, cost and ad figures when the Agent, a loop or your connected agent asks for them. We see only what the person who approved the connection can see in Pluto Profit. Pluto Ads never changes anything in Pluto Profit. The data Pluto Profit itself holds is covered by Pluto Profit’s Privacy Policy.

2.7 Billing data

Payments are handled by Stripe. We store your organization’s plan, billing email, business name and address, tax IDs, invoices and payment status, and a record of AI and storage usage by person, model and date. Card details go directly to Stripe; we never see or store full card numbers.

2.8 Messages and bookings

  • Our contact form collects your name, email address, company (optional), topic and message. For rate limiting we store a one-way hash of your IP address, not the address itself.
  • Booking a demo or a sales call through Cal.com collects your name, email address, company and the time you chose.
  • Emails we send you, such as sign-in codes, invitations, notifications and billing notices, are delivered by Resend, which tells us when an email bounces or is marked as spam.

2.9 Technical and usage data

We automatically collect limited technical data: IP address, browser and device type, the pages and features used, request and error logs, and an activity (audit) log of who did what in each workspace and when. For each AI request we record metadata such as the model, tokens, timings, the tools used and the outcome. We use this to operate, bill, secure and improve the Services.

3. How we use data

We use personal data and customer data to:

  • Provide the Services: publish and change campaigns, ad sets and ads when someone in the workspace asks us to, keep the ad account structure and results up to date, and bring comments and leads into the Agent and Loops where each platform allows it
  • Run the Agent, Loops, media search and Creative Memory for your workspace
  • Authenticate users, manage accounts and permissions, and protect accounts
  • Bill for plans and usage, and enforce the spending limits you set
  • Send service, security, billing and account emails
  • Provide support, and answer messages and bookings
  • Monitor reliability, prevent abuse, and find and fix problems
  • Comply with law and enforce our Terms of Service

We do not sell personal information, and we do not share it for cross-context behavioral advertising. We do not use customer data to contact an advertiser’s customers, commenters or leads on our own behalf.

4. AI features

The Agent, the AI steps in Loops, media search and Creative Memory use AI models. A request contains what you ask, and the workspace data the Agent reads to answer it with your permissions, which can include ad names, settings, results, comments or lead answers.

AI model providers. AI requests are processed by our AI model providers, Anthropic, OpenAI and xAI, as our subprocessors, whichever model you pick. Requests from the Agent and Loops reach them through a gateway operated by Ciresk ApS, also our subprocessor. Media search and Creative Memory also analyze your media with models we run in our own AWS environment.

Where AI requests are processed. The gateway runs in the European Union (Sweden). The AI model providers process requests in the United States and in other countries where they operate, so AI requests are not limited to processing in the United States.

We do not use customer data to train AI models.

Help improve Pluto’s AI. This organization setting is off by default, and only owners and admins can turn it on or off, in the organization’s General settings. While it is off, we keep only metadata about AI runs (tokens, timings, tool names and outcomes), never their text. While it is on, we also keep the text of the organization’s Agent and loop AI runs (questions, answers, and tool inputs and results) and any comment left with feedback, after removing secrets such as keys and tokens, email addresses and card numbers. Our staff use it to find and fix failures and to build test cases. It is never used to train models, by us or by any provider. When the setting is turned off, text already kept is deleted within 30 days.

If you connect your own AI tools to Pluto Ads (for example an MCP client or a script that uses our API), the data they read is sent to that tool and its provider under your own agreement with them. They are not our subprocessors.

5. Data from Meta, LinkedIn and Google

5.1 Meta Platform data

Data we receive from Meta through its APIs (“Platform Data”) is handled under these rules, in addition to the rest of this policy:

  • We use it only to provide the Pluto Ads features that the person who connected Meta, and their workspace, use: showing and managing their ad accounts, Pages, campaigns and ads, their results, the comments on their ads and the leads from their forms, in the workspace that connected it.
  • We never sell Platform Data, and never license, share or transfer it to data brokers, ad networks or other third parties, except the subprocessors in section 7 that host and process it for us.
  • We never use one advertiser’s Platform Data for another advertiser, never combine it across workspaces or organizations, and never use it to build or augment profiles of individuals, to target ads outside the advertiser’s own ad accounts, or to make decisions about anyone’s eligibility for credit, employment, housing or insurance.
  • Access tokens and lead answers are stored encrypted. Page access tokens are never stored. Only people with access to the workspace that connected Meta can see its Platform Data.
  • If an organization has turned on Help improve Pluto’s AI (section 4), the text of AI runs that read Platform Data is kept on the same terms: only to find and fix failures in Pluto Ads, never to train models.
  • We delete Platform Data when it is no longer needed to provide the Services, when you disconnect Meta or delete the workspace, and when you or Meta ask us to (section 10).

Delete your data explains how to remove Pluto Ads from your Facebook account and how to ask us to delete the Meta data we hold about you. We comply with Meta’s Platform Terms and Developer Policies.

5.2 LinkedIn data

Data we receive from LinkedIn through its APIs is handled under these rules, in addition to the rest of this policy and LinkedIn’s API terms:

  • We use it only to provide Pluto Ads to the workspace that connected LinkedIn: showing and managing its ad accounts, Pages, campaigns and ads, reporting their results, and the leads and comments on them.
  • We never sell LinkedIn data, and never share it with data brokers, ad networks or other third parties, except the subprocessors in section 7 that host and process it for us.
  • We never use one advertiser’s LinkedIn data for another advertiser, never combine it across workspaces or organizations, and never use it to build profiles of LinkedIn members, to enrich other data, or to target ads.
  • AI. LinkedIn data is never used to train AI models. When the Agent or a loop works with your LinkedIn ads, the settings, results and leads it reads are sent to the AI model provider that runs it (section 4), only to answer you. Comment text and commenters’ names and profiles from LinkedIn are never sent to AI models, and AI never writes replies to comments on LinkedIn: people in your workspace do.
  • Comments stay in the app. Comment text and commenters’ names and profiles from LinkedIn appear only in the Pluto Ads app. Our API, MCP server, loops, Slack messages, emails and webhooks carry IDs and counts, never the text or the commenter’s name or profile.
  • Retention. Results, and the ad account, campaign, ad set and ad settings we read from LinkedIn, are kept for at most one year. Comment text is deleted 48 hours after we store it. Commenters’ profiles are never stored. LinkedIn’s IDs for accounts, campaigns, ads, comments and commenters may be kept with the workspace’s own records. What the Agent or a loop read from LinkedIn (the settings, results and leads in Agent chats, in loop runs and their history, and in AI run text kept under Help improve Pluto’s AI), and the names and values of changes found on LinkedIn in the events that start loops, are removed one year after they were read. The chat, your messages, the Agent’s answers and each loop run’s outcome stay. The history of changes made through Pluto Ads (who changed what, from what, to what, and when) is Pluto Ads’ own record and stays.
  • Disconnecting. When an admin disconnects LinkedIn, we ask LinkedIn to revoke Pluto Ads’ access and delete the stored access tokens and the connected member’s name at once. Ten days later, unless an admin has reconnected LinkedIn by then, we delete the LinkedIn data synced into that workspace: its ad accounts, Pages, lead forms, campaigns, ad sets and ads, their settings and results, comments, and what the Agent or a loop read from LinkedIn in Agent chats, loop runs, events and AI run text. The connection’s record then keeps only that LinkedIn was connected, when, by whom in Pluto Ads, and when and why it ended. Launches, leads, Agent chats (your messages and the Agent’s answers) and the history of changes made in Pluto Ads stay with the workspace. When a workspace or organization is scheduled for deletion, its LinkedIn access tokens are deleted at once and its LinkedIn data 10 days later.
  • Access removed at LinkedIn. If the member removes Pluto Ads in their LinkedIn settings, or LinkedIn revokes our access, we find out the next time Pluto Ads uses that access, and at the latest the next day. We then delete the access tokens and the connected member’s name, stop syncing and publishing, and ask an admin to reconnect. We treat it as a disconnect: 10 days later, unless an admin has reconnected LinkedIn by then, we delete the same LinkedIn data a disconnect does.
  • Leads. When someone asks LinkedIn to delete a lead they submitted, we delete it, with its answers in Agent chats, as soon as LinkedIn tells us or our regular check finds it gone.
  • Access tokens and lead answers are stored encrypted. Only people with access to the workspace that connected LinkedIn can see its LinkedIn data.

You can withdraw Pluto Ads’ access at any time by disconnecting LinkedIn in Integrations or removing Pluto Ads in your LinkedIn settings. Delete your data explains both.

5.3 Google user data

Pluto Ads’ 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.

Data we receive from Google through its APIs, including the Google Ads API (“Google user data”), is handled under these rules, in addition to the rest of this policy:

  • We use it only to provide the Pluto Ads features you see and use in the app: showing, launching and managing the Google Ads accounts, campaigns, ads, keywords and lead forms of the workspace that connected Google Ads, reporting their results and changes, and the Agent, loops and Creative Memory you run on them.
  • We never sell Google user data. We transfer it only to provide those features (to the subprocessors in section 7 that host and process it for us, and to the AI model provider that runs the Agent or a loop when you ask it something), when you send it on yourself (for example through our API, an MCP client or a webhook you set up), for security, to comply with law, or as part of a merger, acquisition or sale of assets with your prior consent. We never transfer it to data brokers or information resellers.
  • We never use or transfer Google user data to serve ads, including retargeting and personalized or interest-based ads, and never for our own marketing. Measuring our own Google ads (section 12) uses only data from our own website and app, never data from your Google Ads accounts. We never use it to decide anyone’s creditworthiness or for lending.
  • We never use one advertiser’s Google user data for another advertiser, and never combine it across workspaces or organizations.
  • Google user data is never used to create, train or improve AI or machine learning models, ours or any provider’s. When the Agent or a loop reads it, it is sent to the AI model provider that runs them (section 4) only to answer that request.
  • People at Pluto read Google user data only with your agreement (for example when you ask us for help with it, or in AI run text kept while an owner or admin of your organization has turned on Help improve Pluto’s AI, section 4), when it is needed for security, such as investigating abuse, or to comply with law.
  • Access and refresh tokens and lead answers are stored encrypted. Only people with access to the workspace that connected Google Ads can see its Google user data.
  • Retention. Results, search terms and keywords reports, the settings we read, and the values and email addresses in the change history from Google are kept for at most one year. What the Agent or a loop read from Google Ads (in Agent chats, loop runs and AI run text) is removed one year after it was read. The chat, your messages, the Agent’s answers and each loop run’s outcome stay. Leads stay with the workspace until Google Ads is disconnected, the workspace is deleted or you ask us to delete them.
  • Disconnecting. When an admin disconnects Google Ads, we stop your Google Ads lead forms sending leads to Pluto Ads, ask Google to revoke Pluto Ads’ access, delete the stored tokens and stop syncing, at once. Ten days later, unless an admin has reconnected Google Ads by then, we delete everything synced from Google into that workspace: its accounts, campaigns, ad groups, ads, keywords and assets, their settings and results, search terms and keywords reports, the change history from Google, lead forms and leads, and what the Agent or a loop read from Google Ads. The connection’s record then keeps only that Google Ads was connected, when, by whom in Pluto Ads, and when and why it ended. Turning off one account’s sync deletes what was read from that account the same way, 10 days later. Launches and the history of changes made through Pluto Ads stay with the workspace.
  • Access removed at Google. If you remove Pluto Ads in your Google Account’s settings, or Google ends our access, we find out the next time Pluto Ads uses that access, and at the latest the next day. We then delete the stored tokens, stop syncing and publishing, and ask an admin to reconnect. We treat it as a disconnect: 10 days later, unless an admin has reconnected Google Ads by then, we delete the same data a disconnect does.
  • When a workspace or organization is scheduled for deletion, we ask Google to revoke its access and delete its tokens at once, and its Google user data 10 days later.

You can withdraw Pluto Ads’ access at any time by disconnecting Google Ads in Integrations, or by removing Pluto Ads at myaccount.google.com/connections. To have Google user data deleted sooner, email support@pluto.camp.

6. Legal bases (EEA and UK)

Where the GDPR or UK GDPR applies to data we control, we rely on:

  • Contract: to provide the Services you or your organization signed up for
  • Legitimate interests: to secure, support and improve the Services and to answer business enquiries, in a proportionate way
  • Legal obligation: where we must keep or disclose data under law, for example bookkeeping records
  • Consent: where required, which you may withdraw at any time

For customer data we process as a processor, the legal basis is our customer’s.

7. Subprocessors and sharing

We share data only as needed to run the Services, with the providers below under contractual confidentiality and data protection terms, or when required by law. Our subprocessors are:

  • Amazon Web Services (United States, us-east-1): application servers, media storage (S3), caching, encryption keys, logs, and the analytics database we run in our own AWS account
  • Vercel (United States): hosting of our websites and the web app
  • Neon (United States, AWS us-east-1): our main Postgres database
  • PowerSync (United States): keeps the app in your browser in sync with your workspace
  • WorkOS (United States): sign-in and identity
  • AI model providers: Anthropic, OpenAI and xAI (United States and other countries where they operate): AI models for the Agent, Loops and media analysis (section 4)
  • Ciresk ApS (European Union, Sweden): operates the gateway that relays AI requests to the AI model providers (section 4)
  • Stripe: payments, subscriptions, invoices and tax
  • Resend (United States): delivery of the emails we send
  • Sentry (United States): error monitoring
  • Axiom (United States): application logs
  • Cal.com: booking demos and sales calls

We update this list before we add or replace a subprocessor.

Meta, LinkedIn, Google and Pluto Profit receive and hold data under their own terms when you connect them and when you publish or change ads through Pluto Ads. We do not control their independent practices.

We may disclose data if required by law, regulation, legal process or a governmental request, or to protect the rights, safety and security of Pluto, our users or the public. If Pluto is involved in a merger, acquisition or sale of assets, data may be transferred as part of it, subject to this policy.

8. International transfers and storage location

Pluto Holding ApS is based in Denmark. Pluto Ads’ production systems and data are hosted in the United States, mainly in Northern Virginia (AWS us-east-1). If you use the Services from outside the United States, your data is transferred to and processed in the United States, and in other countries where our providers operate. AI requests are processed by our AI model providers in the United States and other countries, and those from the Agent and Loops pass through a gateway in the European Union (Sweden) (section 4). Where required, we use appropriate safeguards for these transfers, such as the European Commission’s standard contractual clauses or, where a provider is certified, the EU-U.S. Data Privacy Framework.

9. Retention

  • Account data is kept while your account exists.
  • Workspace content, including media, is kept while the workspace exists. Older history (for example finished jobs and loop runs) moves from our main database to our archive, and is kept for as long as the workspace.
  • Data from Meta is kept while Meta is connected and the workspace exists. When Meta is disconnected, the access token and the comments and leads we stored are deleted; ad account structure and results already synced stay in the workspace until it is deleted or you ask us to delete them.
  • Data from LinkedIn is kept for at most one year, including what the Agent or a loop read from it in Agent chats, loop runs and AI run text, and comment text for 48 hours. Synced LinkedIn data is deleted 10 days after LinkedIn is disconnected or access is removed at LinkedIn, as described in section 5.2. Leads stay in the workspace until it is deleted or you ask us to delete them.
  • Data from Google Ads is kept for at most one year, including what the Agent or a loop read from it, and everything synced from Google is deleted 10 days after Google Ads is disconnected or access is removed at Google, as described in section 5.3.
  • AI run text is kept only as described in section 4.
  • Billing records, usage records and the activity (audit) log are kept after an account, workspace or organization is deleted, as bookkeeping law and security require, with names, email addresses and free text removed so they no longer identify anyone.
  • Backups expire on a rolling schedule, generally within 30 days. A media file you replace or delete stays recoverable for 30 days, then is deleted.

10. Deleting your data

  • Your account. In the app, open your account and choose Delete account. It happens at once. Your profile, preferences and private Agent chats are deleted, your API keys, agents and sessions stop working, and work you created stays with your team, attributed to “Deleted user.” Export my data, on the same page, gives you a copy first.
  • A workspace or organization. A workspace can be deleted in its settings, and an organization by its owners. Both are scheduled for deletion in 30 days, can be restored until then, and are then deleted for good, with their content, media (every version) and the Meta, LinkedIn and Google Ads data they hold. Ads already live in Meta, LinkedIn or Google Ads keep running; nothing is deleted there.
  • Meta. Disconnect Meta in Integrations, or remove Pluto Ads in your Facebook settings. You can also ask Facebook to have Pluto Ads delete your data: we then delete your access token and connection details in every workspace you connected, with the comments and leads stored for them, and Facebook shows you a confirmation code and a link to the status of your request. Delete your data explains each way.
  • LinkedIn. Disconnect LinkedIn in Integrations: we ask LinkedIn to revoke our access and delete the access tokens at once, and the LinkedIn data synced into the workspace 10 days later (section 5.2). You can also remove Pluto Ads in your LinkedIn settings: syncing stops, and the LinkedIn data synced into the workspace is deleted 10 days later, as for a disconnect.
  • Google Ads. Disconnect Google Ads in Integrations: we ask Google to revoke our access and delete the access tokens at once, and the Google Ads data synced into the workspace 10 days later (section 5.3). You can also remove Pluto Ads in your Google Account’s settings: syncing stops, and the Google Ads data synced into the workspace is deleted 10 days later, as for a disconnect.
  • Anything else. Email support@pluto.camp from the address you sign in with.

11. Security

We use technical and organizational measures appropriate to the risk. Every connection uses TLS 1.2 or later. Data is encrypted at rest, and our own stores use keys we manage in AWS Key Management Service. Provider access tokens are sealed with AES-256-GCM, and lead answers are stored encrypted. Access to customer data is limited to each workspace’s members and permissions, changes are recorded in an audit log, and webhooks from providers are verified. No method of transmission or storage is perfectly secure. We have not completed a SOC 2 examination or ISO 27001 certification as of the date above and do not claim them.

12. Cookies and advertising

We use these cookies and similar technologies:

  • Necessary: the app’s cookies that sign you in and keep your session secure, and a cookie that remembers whether your country needs your consent before anything optional runs. We read the country from your connection; we don’t keep your IP address for this. Your light or dark theme choice stays in your browser’s storage.
  • Your cookie choice: whether you chose Accept or Reject, kept for 12 months.
  • Partner link (the pluto_ref cookie): remembers which partner’s link brought you here, so the partner can be credited if you sign up. 90 days. Set only with your consent.
  • Google tag and Google Ads conversion measurement: tells us which of our Google ads lead to visits, sign-ups, trials and purchases. When you arrive from a Google ad, we keep its click ID in a cookie for up to 90 days and store it with your account if you sign up. When you first pay for a plan, we report that purchase, its amount and currency to Google Ads with the click ID. With your consent, the app also sends Google a hashed (SHA-256) form of your email address with a sign-up or trial (enhanced conversions), so Google can match it to an ad you saw. Google receives the hash, not the email address.

When you open a booking, Cal.com’s scheduler loads and may set its own cookies under Cal.com’s policy.

Your choice. In the EEA, the UK and Switzerland, nothing optional runs until you choose Accept. Elsewhere it runs until you choose Reject. You can change your choice at any time with Cookie settings at the bottom of our website or in the app’s account menu. When your browser sends a Global Privacy Control or Do Not Track signal, nothing optional runs and we treat it as your opt-out. Blocking necessary cookies in your browser stops sign-in from working.

13. Your rights and choices

Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict certain processing, and to withdraw consent. You can:

  • Update your profile and settings in the app
  • Export your data with Export my data on your account page
  • Disconnect Meta, LinkedIn, Google Ads and Pluto Profit at any time
  • Delete your account, a workspace or your organization (section 10)
  • Email support@pluto.camp with any other request

EEA and UK. You may lodge a complaint with a supervisory authority, such as the Danish Data Protection Agency (Datatilsynet) or the authority where you live or work.

US state privacy rights. If you live in California or another US state with a consumer privacy law, you may have the right to know what personal information we collect, use and disclose, to access, correct and delete it, to receive a portable copy, and to opt out of its sale, its sharing for cross-context behavioral advertising, and targeted advertising. We do not sell personal information. Measuring our Google ads (section 12) may count as sharing for cross-context behavioral advertising under some of these laws. To opt out, choose Reject, or Cookie settings at any time; we also honor Global Privacy Control as an opt-out. We do not use sensitive personal information to infer characteristics about you. We will not discriminate against you for exercising your rights. You may use an authorized agent, and if we decline your request you may appeal by replying to our answer.

In the past 12 months we collected the categories of personal information described in section 2: identifiers (such as name, email address and IP address), commercial information (plans, invoices and usage), internet and network activity, professional information (your organization and role), and the content you and your team put into the Services. We collected them from you, from your organization, from the platforms you connect, and automatically. We used them for the purposes in section 3 and disclosed them only to the subprocessors in section 7 for those purposes.

To protect your data we verify requests, usually by asking you to write from the address you sign in with. We answer within the time the applicable law requires. For customer data we process as a processor, such as comments or lead answers, we may direct your request to the advertiser or act on its instructions.

14. Children

The Services are not directed to children under 16, and we do not knowingly collect personal data from them. If you believe a child has provided us personal data, contact us and we will delete it.

15. Changes

We may update this Privacy Policy from time to time. We will change the “Last updated” date when we do. Material changes may also be communicated in the app or by email. Continued use of the Services after an update means you accept the revised policy.

16. Contact

Questions about this Privacy Policy, or privacy and data deletion requests:

Pluto Ads
Pluto Holding ApS, CVR 46452682
Sommerfugleengen 66, 8600 Silkeborg, Denmark
Phone: +45 25 73 66 00
Email: support@pluto.camp
Message: plutoads.ai/contact
Data deletion: plutoads.ai/data-deletion