Privacy Policy

This policy explains how Cago (“Cago”, “we”) handles data when you visit cago.io, create an account, join a workspace, connect a data source or use Cago Inbox (inbox.cago.io).

Cago is a business tool for e-commerce advertisers. When a customer (a brand or agency) connects its ad accounts, order sheets or Facebook Pages, that customer decides what data to connect and is responsible for having a lawful basis to do so. For that data Cago acts as a service provider (processor) and processes it only to provide the service to that customer.

The Arabic version of this policy is available at cago.io/privacy. If the two versions differ, the English version prevails for users outside the Arabic-speaking markets and for platform reviews.

We collect only what we need to run Cago:

• Account data: name, email address, profile picture, sign-in method (email and password, Google sign-in or passkey), two-factor settings and verification status.
• Workspace data: brand name, country, reporting currency, brand image, team members, roles, plan and usage limits.
• Advertising data from the Meta, TikTok and Snapchat ad accounts you connect: account, campaign, ad set / ad group / ad squad and ad identifiers and names, status, targeting countries, spend, impressions, reach, clicks, video and conversion metrics, and hour / placement / age breakdowns.
• Order data from the Google Sheet you choose: the columns you map, such as order ID, date, status, total, currency and the UTM or campaign column used to attribute orders to ads.
• Creative data: images and videos you upload to the creative library, and the thumbnails and preview copies we generate from them.
• Cago Inbox data (only if you connect a Facebook Page): see Messenger data.
• Billing data: plan, subscription status, country and currency. Payments are processed by our payment provider (Polar); we never receive or store full card numbers.
• Usage and security data: IP address, browser and device type, sign-in and session records, audit logs of sensitive actions, error reports and sync logs.

Cago uses Google in two ways, both only after you authorize them:

• Google sign-in gives us your name, email address and profile picture to create and secure your account.
• Google Sheets uses the drive.file scope. This gives Cago access only to the spreadsheets you pick in the Google Picker or that Cago creates for you, never to the rest of your Drive. We read the order rows you mapped to match orders to ad spend, and, if you use Cago Inbox, we append the orders your team records to the sheet you chose.

Limited Use. Cago’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. In particular:

• we use Google user data only to provide and improve the user-facing features described above;
• we do not transfer it to others except as needed to provide those features, to comply with the law, or as part of a merger or acquisition with notice to you;
• we do not use it for advertising, including retargeting or personalized or interest-based ads, and we do not sell it;
• no person at Cago reads it unless you give us permission for a specific support request, it is needed for security (for example investigating abuse), or the law requires it;
• we do not use it to develop, improve or train generalized or non-personalized AI or machine-learning models.

You can remove Cago’s access at any time in your Google account permissions or by disconnecting the sheet in Cago.

When you connect an ad account through the platform’s own authorization screen, Cago receives an access token with the permissions you approve:

• Meta: ads_read and ads_management (to read performance and, when you ask, pause or resume campaigns and ads), business_management and your email. Cago Inbox also asks for pages_show_list, pages_messaging, pages_read_engagement and pages_manage_metadata.
• TikTok and Snapchat: access to the advertiser accounts you select, to read performance and, when you ask, pause or resume campaigns and ads.

Cago only changes a campaign or ad when a member of your workspace with the right role asks it to. We do not create ads, change budgets or spend money on your behalf. Tokens are encrypted and bound to your workspace and platform.

If you connect a Facebook Page to Cago Inbox, Cago receives, through Meta’s Messenger Platform, the messages people send to that Page and the replies your team sends from Cago. For each person who messages the Page we store their page-scoped ID, the name and profile picture Meta shares, the conversation and its attachments.

When your team records an order from a conversation, Cago stores the order details your team enters (for example customer name, phone number, city, address, items and total) and can add the order to your Google Sheet. If you enable it, Cago sends a Purchase event for that order to your own Meta dataset using the page-scoped ID, order value and currency, so your campaigns can measure sales. We do not send names, phone numbers or addresses to Meta.

Messenger data belongs to the business that owns the Page. We use it only to show conversations to that business’s team and to run the features above. We never use it for our own marketing, never sell it and never share it with other customers.

We use data to run accounts and workspaces; sync the sources you connect; match ad spend to orders; calculate cost per purchase, return on ad spend and other performance figures in your reporting currency; show creative performance; generate the PDF reports you request; send service emails (verification codes, security alerts, invitations, billing notices); provide support; enforce plan limits; keep Cago secure and prevent abuse; and understand how Cago is used so we can improve it.

We do not sell personal data or brand data, and we never use one customer’s data to run or target ads for another customer.

We use the following providers to run Cago. Each receives only what it needs for its task, acts on our instructions and is bound by confidentiality and security obligations:

• Vercel (web application hosting), Railway (background sync and realtime services), Neon (database), Amazon Web Services (S3 and CloudFront storage for creatives);
• Polar (payments and subscriptions), Resend (email delivery);
• PostHog (product analytics, see Cookies), Sentry (error monitoring, with cookies, request bodies and tokens removed before sending).

We also exchange data with the platforms you choose to connect (Google, Meta, TikTok, Snapchat), only as needed to perform the sync or action you requested and within the permissions you granted. We may disclose data if the law requires it, to protect the rights and safety of our users or Cago, or as part of a merger or acquisition, with notice to you.

Every workspace’s data is logically isolated and every query is scoped to its workspace. Access is role-based, all connections use HTTPS, and OAuth tokens are encrypted with a key bound to the workspace and platform. Owners and admins must use two-factor authentication, sensitive actions require recent re-authentication, you can review and end your sessions, and new-device sign-ins trigger an email alert. Cago staff access customer data only when needed to operate or support the service.

No system is 100% secure. We review our safeguards regularly and ask you to protect your account and not share sign-in details. If a breach affects your data we will notify you as required by law.

We keep account and workspace data while you use Cago. When you disconnect an integration, syncing stops, we revoke the token with the platform where it allows this, and we delete it from our database; data already synced stays in the workspace until the workspace is deleted. When an account or workspace is deleted, we delete its data from our live systems, except what we must keep for legal, tax, billing or fraud-prevention reasons. Backups are overwritten on a rolling basis within a limited period.

To delete your data:

1. Disconnect any integration from the Integrations page in Cago, or remove Cago from your Google, Facebook, TikTok or Snapchat account settings.
2. To delete your account, a workspace, or Messenger data received through Cago Inbox, email privacy@cago.io from the email address on the account (or, for Messenger data, include the Page name). We confirm and complete the request within 30 days.

If you messaged a business’s Facebook Page and want your data removed, you can contact that business or email us and we will pass the request to the workspace owner and delete the data on their instruction.

Depending on where you live, you may have the right to access, correct, export or delete your personal data, to restrict or object to its use, and to withdraw consent. Email privacy@cago.io. We may need to verify your identity and your role in the workspace first. Where a customer controls the data (for example its order sheet or Page conversations), we may forward your request to that customer.

We use essential cookies to sign you in, protect your session and remember your settings; Cago does not work without them. We use PostHog to measure how the site and product are used (pages and clicks, linked to your Cago account once you sign in). Text on the page and anything you type are masked, and session recordings are limited to the marketing and sign-up pages with every field hidden. Nothing from Cago Inbox or your customers’ messages is sent to PostHog. We do not use advertising cookies.

Our providers may process data outside your country, including in the United States and the European Union. Where the law requires it, we rely on appropriate safeguards such as standard contractual clauses. Cago is for businesses and is not intended for anyone under 18.

We may update this policy as Cago or the law changes. We will update the date at the top and give reasonable notice of material changes. For privacy questions or requests email privacy@cago.io; for general support email support@cago.io.