Privacy

Privacy Policy

Summary of what data we process, why, how long we keep it, and how you can get it back or delete it.

Data controller

Surya Marketing s.r.o., Company ID 23240253, registered office Korunní 2569/108, Vinohrady, 10100 Prague 10, Czech Republic. Data Protection Officer: info@suryatool.io.

What data we process

  • App user data: email, name, role, job title. Purpose: providing the service and communication.
  • OAuth tokens: encrypted access to Google (Ads, Analytics, Search Console, Merchant Center), Sklik and Meta Ads. Purpose: reading data and (with your approval) writing to ad accounts.
  • Ad account and website data: campaigns, keywords, search terms, performance metrics, web analytics, organic search data and product feeds. Purpose: analysis and report generation. Data from Google accounts is described in detail in the Google user data section. The scope, history and retention of this data are described in the Terms of Service, Section 6.
  • Audit log: a record of actions, approvals and executed changes, without IP addresses, retained for the duration of the agreement. Purpose: forensic reconstruction, rollback.
  • Comparable settings: campaign settings converted into a unified form, without identifying the customer, its clients or advertisers. Purpose: deriving patterns, comparisons and recommendations across customers; outputs never contain data that would allow another customer or its client to be identified. Details in the Terms of Service, Section 6.

Google user data

When you connect a Google account in Surya, you grant the permissions listed below. Surya uses each of them only for the features described next to it.

  • Google Ads (scope adwords): reading account structure, campaigns, ad groups, keywords, ads, assets, search terms, conversion actions, change history and performance metrics, and keyword ideas from Keyword Planner. Purpose: performance reports, AI analysis and change proposals. Surya writes to a Google Ads account only to execute a change that a user approved in Surya, or a change covered by an auto-apply rule that an organization owner or admin explicitly turned on for low-risk change types (negative keywords and labels).
  • Google Analytics (scope analytics.readonly, read only): the list of GA4 properties and daily sessions, users, page views, bounce rate, conversions, revenue, traffic sources, channels and landing pages. Purpose: website reports and comparing conversions reported by ad platforms with your analytics.
  • Google Search Console (scope webmasters.readonly, read only): the list of sites, search queries, pages, clicks, impressions, click-through rates and positions, sitemaps and URL inspection results. Purpose: organic search reports, finding overlap between paid and organic search, and landing page checks.
  • Google Merchant Center (scope content): the list of Merchant Center accounts, products and their approval status. Purpose: product feed diagnostics, product labels for shopping campaigns and Performance Max audits. Surya does not modify products or feeds in Merchant Center. The only write request is the one-time developer registration that Google requires before the Merchant API can be used.
  • Email address (scope userinfo.email): to show which Google account is connected and to detect a reconnection with a different account.

How we use and share it

Google user data is used only to provide and improve the user-facing features of Surya described above. We do not sell it, do not transfer it to advertising platforms, data brokers or information resellers, and do not use it to serve ads or to determine creditworthiness or for lending purposes.

To produce analyses and change proposals, relevant parts of the data are processed by Anthropic (Claude), and short text excerpts derived from it (for example summaries of change proposals) are converted to vector embeddings by OpenAI. Both act as our subprocessors under API terms that exclude using the data to train their models. Surya does not use Google user data to train generalized AI or machine learning models. Learning from optimization results across organizations uses only aggregated statistics that do not identify any client, campaign, keyword, spend amount or account (see Terms of Service, Section 6).

Storage and security

Refresh tokens are stored encrypted (AES-256-GCM) in our database hosted by Railway in Frankfurt, EU. Access tokens are not stored in the database; short-lived access tokens are obtained when needed and kept only in memory. All data is transferred over encrypted HTTPS connections.

Human access

As the provider of the service, people at Surya Marketing s.r.o. do not read our customers' Google user data, except with the customer's explicit consent (for example when you ask for support with a specific account), when needed for security purposes such as investigating abuse or a bug, to comply with applicable law, or when the data is aggregated and used for internal operations.

Disconnecting and deletion

You can disconnect Google at any time in the client's integration settings. The stored tokens are deleted immediately. You can also revoke Surya's access in your Google Account at myaccount.google.com/permissions. Data that has already been synchronized stays in your account so that historical reports keep working. You can delete Google Ads data together with the ad account, or ask us at info@suryatool.io to delete any of it, and we will do so within 30 days. After the agreement ends, all data is deleted as described under Retention.

Limited Use

Surya'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.

Retention

We keep data for the duration of the agreement. After a client is deleted in the Application, we irreversibly erase its data within 30 days at the latest. After the agreement ends, we delete the entire organization at your request. The audit log is retained for the duration of the agreement.

Subprocessors (Article 28)

  • Cloudflare — DNS, CDN. Frankfurt, EU.
  • Railway — API and database hosting (Frankfurt, EU) and the Memgraph graph database.
  • Anthropic — AI inference (Claude). Zero retention, no training.
  • OpenAI — embeddings (vector search). No full reports.
  • Resend — transactional email. Frankfurt, EU.
  • Stripe — payments and subscription billing.
  • Apify — collection of publicly available web data for market and competitor analyses.

Your rights

You have the right to access, correction, erasure, restriction of processing, portability, objection, and complaint to ÚOOÚ (Czech DPA). Send requests to info@suryatool.io, response within 30 days.