Privacy Policy

Charlie is an AI marketing copilot available at v2.charliesystem.com (the “Service”). It helps create marketing content, ad copy, campaign plans, and analytics dashboards.

The Service is operated by, and the data controller is, CAP-NET s.r.o., Company ID (IČO) 25466640, registered at Budějovická 234, 381 01 Český Krumlov, Czech Republic, represented by its managing director Milan Litvan (“we” or “the operator”).

Privacy contact: privacy@charliesystem.com.

Account data

• Email address, name, and profile details you provide at sign-up.
• Team/organization membership and assigned roles.
• Authentication and session data (strictly necessary cookies, see section 11).

Payment data

Payments and subscriptions are processed by our payment provider (Stripe). We do not store card numbers - we only have access to subscription status and billing metadata.

Content you create

Briefs, inputs, generated content, client information, and knowledge base data that you enter into or create within the Service.

Data from connected Google and Meta services

If you connect a Google or Meta account, we process the data described in sections 3 to 7.

Connecting a Google account is optional. It is always initiated by the user, separately for each client they manage, through Google's official OAuth consent screen. Charlie requests only the following Google OAuth scopes:

• openid, userinfo.email, userinfo.profile: your Google account's email address, name and profile picture. Used only to show which Google account a connection belongs to.
• Google Analytics (analytics.readonly), read-only: the list of GA4 accounts and properties you can access, and aggregated reporting data of the property you select (e.g. sessions, users, traffic sources, pages, devices, countries, events, conversions and revenue, by date). Used to display traffic and conversion dashboards, compute marketing KPIs, detect anomalies and generate reports for you.
• Google Search Console (webmasters.readonly), read-only: the list of your verified sites and, for the site you select, search performance data (queries, pages, clicks, impressions, CTR, average position, devices, countries) and sitemap status. Used for the SEO dashboard and content recommendations.
• Google Ads (adwords): the list of ad accounts you can access and, for the account you select, the structure and performance of campaigns, ad groups, keywords, search terms, ads and assets (e.g. cost, clicks, impressions, conversions, conversion value) and Google's optimization recommendations. Used for campaign dashboards and automated account audits.

Charlie makes a change to a Google Ads account (for example applying a recommendation, adding negative keywords or pausing a campaign) only after an authorized user has reviewed and explicitly approved that specific change, either in the app or in an approval message Charlie sends to a channel you set up. There is no automatic or unattended write access.

Charlie does not request access to any other Google data, such as Gmail, Google Drive, Contacts or Calendar.

We use data obtained from Google APIs solely to provide the features you request within the Service - primarily to display reports and dashboards and to generate AI analysis and recommendations over your data.

When you ask for an AI analysis, the relevant Google API data is sent to our AI model providers Anthropic and Google (Gemini) solely to generate that result for you. We do not send Google API data to any other AI provider. Neither provider uses this data to train its models.

We do not sell Google API data, use it for advertising, transfer it to data brokers or any other third party, or use it to train generalized artificial intelligence models.

• OAuth tokens: we store the refresh token issued by Google, encrypted with AES-256-GCM. We never see or store your Google password.
• Reporting data: to power dashboards, trends over time and reports, we store aggregated data from Google Analytics, Search Console and Google Ads in our database (totals by day, campaign, page or query, not data about individual website visitors).
• Detailed Google Ads data at ad group, ad and keyword level is deleted automatically after 90 days, campaign-level data after 400 days and raw imported data after 30 days. Other aggregated data, and reports and audits you save in Charlie, are kept for as long as the client exists in the Service.
• Access control: Google user data is visible only to users with access to the client it belongs to (the owner, organization members and client members). This is enforced at the database level (Row Level Security). Our staff access it only when needed for support you request, to investigate security issues or abuse, or to comply with the law.
• In transit, all data is encrypted with HTTPS/TLS. Database backups are encrypted.

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

Connecting a Meta account (Facebook and Instagram) is likewise optional and always goes through Facebook's official login screen. We request only these permissions, and only for the Pages and accounts you grant us:

• Pages (pages_show_list, pages_read_engagement, pages_read_user_content): pick your Page, read its posts, metrics and comments.
• Publishing to Facebook (pages_manage_posts, pages_manage_engagement): publish a post and reply to comments, always on your instruction or through automation you switch on.
• Instagram (instagram_basic, instagram_manage_comments, instagram_manage_insights): profile, media, comments and insights of the connected account.
• Publishing to Instagram (instagram_content_publish): publish a post or story on your instruction or through automation you switch on.
• Advertising (ads_read, ads_management, business_management, read_insights): read campaign performance and apply changes you approve.

Meta access tokens are stored encrypted and used only for the accounts you grant us. You can revoke the connection at any time in the integration settings or in your Meta business settings. You can also request deletion of your Meta data through Facebook; instructions are at v2.charliesystem.com/data-deletion.

We do not sell personal data. To operate the Service we rely on vetted processors, sharing only the minimum data required:

• Hosting and database providers (running the app and storing data).
• AI model providers Anthropic and Google (Gemini): content generation and AI analysis. Only these two receive Google API data, see section 4.
• Perplexity: web search (research, benchmarks). It receives search queries only, never Google API data.
• Stripe: payment processing.
• Email provider: sending transactional emails (e.g. notifications, account verification).

Reports and alerts you set up may contain aggregated Google data; we send them only to the channels you choose (email, chat room, webhook).

We retain data for the duration of your account and as long as necessary to meet legal obligations. Retention periods for Google data are listed in section 5.

When you disconnect a Google service in Charlie (Integrations section of the relevant client, “Disconnect”), we immediately delete the stored token and stop fetching data from that service. Data already synchronized stays with the client until you delete the client or ask us to delete it. You can also revoke Charlie’s access at any time directly in your Google account at myaccount.google.com/permissions.

Deleting a client deletes the Google data synchronized for it. You can request deletion of your account in the privacy settings; we then delete the account within 30 days, together with all clients you own and their Google data. Clients shared with other members of your organization stay with them. You can also request deletion at any time at privacy@charliesystem.com.

You have the right to access, rectify, erase, restrict, and port your data, and the right to object. To exercise these rights, contact privacy@charliesystem.com. You also have the right to lodge a complaint with the Czech Data Protection Authority (uoou.gov.cz).

Data is transmitted encrypted (HTTPS), database access is governed at the row level (Row Level Security) and restricted to authorized users. Access tokens for Google and Meta are stored encrypted.

We use only strictly necessary cookies - authentication/session cookies and a cookie to remember your language. We do not use advertising cookies.

We may update this policy. We will notify you of material changes, and the current version is always available on this page with its effective date.