Privacy Policy
Last updated: November 16, 2026 · Policy version: v2.5
This Privacy Policy describes how Coppica ("we," "us," or "our") collects, uses, shares, and protects your personal information when you use our AI-powered marketing pipeline platform ("Service").
We are committed to protecting your privacy and handling your data transparently. This policy is designed to comply with the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA/CPRA), and other applicable privacy laws.
1. Data We Collect
1.1 Account Information
When you create an account, we collect your email address, display name, company name, and the plan you select. We also store authentication credentials securely through our authentication provider.
If you reached us from the free copy analyzer at taxonomy.coppica.com, we also store the identifier of the analysis you ran there, so we can tell which analysis led to your signup. It is a reference to your own earlier session, not a profile of you, and it is never used to target advertising. It is recorded whether or not you accepted marketing cookies, because it is carried by the sign-up link itself rather than by any tracker. Write to privacy@coppica.com to have it removed from your account, which does not affect your subscription.
1.2 Intake Form Content
When you or your clients submit intake forms, we collect business information including product/service descriptions, ideal customer profiles, competitor information, brand voice preferences, and any other information entered into intake forms. When you request Competitive Intelligence, we also collect public competitor ads, advertiser identities, delivery dates, page text and reviews, and store source snapshots and the persuasion techniques observed in those ads.
1.3 Bot Outputs
We store all AI-generated outputs (strategy documents, marketing copy, chat histories) created through the Service. These are stored to provide you with access to your generated materials. Market Voices also reads public forum posts, video comments, and reviews to collect verified buyer quotations and source links. No usernames are stored.
1.4 Billing Data
Payment information (credit card numbers, billing addresses) is collected and processed by our payment processor, Stripe. We do not store full credit card numbers on our servers. We receive and store billing metadata such as plan type, subscription status, and transaction history.
1.5 Usage Logs
We collect usage data including pages visited, features used, bot runs initiated, API request metadata, IP addresses, browser type, and device information. This data is used for security, performance monitoring, and service improvement.
For each client account, we also record when it was last used and which team member used it. If nobody uses an account for three days, we pause its automatic analysis (such as daily performance briefs and ad technique tagging) until someone returns, so analysis doesn't run on accounts nobody is using. Your data keeps syncing while the analysis is paused.
1.6 Uploaded Files
If you upload reference materials, documents, or other files to the Service, we store those files to provide context to the AI pipeline.
1.7 Electronic Signature Data
When you use the electronic signature features of the Service, we collect and store data related to each signing event, including: signer name, email address, IP address at the time of signing, browser and device information, timestamp of each signing action, cryptographic document hashes (SHA-256), consent records for electronic signing, and document viewing/access events. This data forms the audit trail required for legal defensibility under the ESIGN Act and UETA. Signed document references and audit trail records are retained for a minimum of seven (7) years.
1.8 Third-Party Platform Integration Data
When you connect a third-party account to the Service, we collect and store data from that platform to provide you with analytics, attribution, and AI-generated content features. The Service supports integrations with advertising and analytics platforms (such as Meta Ads, Google Ads and Google Analytics), document storage (such as Google Drive), website behavior analytics (such as Microsoft Clarity), attribution and conversion tracking services (such as Cortana and Hyros), CRM and marketing automation platforms (such as HubSpot and GoHighLevel), email sending platforms (such as Resend), meeting intelligence services (such as Fathom), communication tools (such as Slack), and other third-party platforms as the Service evolves. For each connected platform, we may collect and store:
- Your account identifier, account name, and connection credentials (encrypted at rest)
- Campaign and ad performance data including impressions, clicks, spend, and conversion actions
- Conversion and attribution data including contact records, conversion events, tracking sessions, UTM parameters, and attribution identifiers (such as fbclid and gclid)
- CRM records including contact names, email addresses, phone numbers, tags, and lifecycle stage data
- Meeting transcripts, call recordings, and participant information from connected meeting intelligence services
- Form submission data from connected CRM or marketing automation platforms
- Website behavior totals from Microsoft Clarity: counts of sessions, dead clicks, rage clicks, quick backs, excessive scrolling and script errors, plus scroll depth and engagement time, aggregated per page, device and ad campaign for one to three day windows. We store these totals only, never recordings or individual visitor sessions, drop query strings from page addresses, and keep the totals for 400 days
- Email activity from a Resend account you connect: sends, deliveries, opens, clicks (the page address and UTM tags of the clicked link, without the rest of its query string), bounces, spam complaints and unsubscribes. Each recipient is stored only as a hashed email address, never as the address itself. We also store broadcast names, subject lines, preview text, sender, status and dates, per-link click totals, and segment names with their contact counts. We never store email bodies or contact lists, and we never send email from that account
- Ad creative identifiers used to link platform data to content generated through the Service
- Sync status and timestamps related to data retrieval
Where a connected platform uses OAuth authentication, tokens are either managed by our integration provider (Composio Inc.) or handled natively by Coppica, depending on the platform. For Composio-managed connections, we store only a reference identifier to the authorized connection. For natively managed OAuth connections, tokens are stored encrypted at rest. Where a platform uses API key authentication, keys are stored encrypted at rest using AES-256-GCM.
We do not use data from your connected third-party accounts to train AI models. Integration data is used solely to provide conversion tracking, performance analytics, attribution insights, and to improve the relevance of AI-generated marketing content for your specific business. Google user data is also subject to section 1.11.
Data controller relationship: You are the data controller for all data flowing into the Service from your connected third-party accounts. Coppica acts as a data processor, processing this data solely according to your instructions and for the purpose of providing the Service. You are responsible for ensuring that you have the legal basis to share this data with Coppica and that your use of connected platforms complies with their respective terms of service and data use policies.
You may disconnect any third-party account at any time through the Service settings. Upon disconnection, we delete the stored account configuration, connection credentials, and reference identifiers. Historical data previously synced (such as conversion events and attribution records) remains in your account unless you request its deletion. If a connected platform sends a data deletion or deauthorization callback, we automatically remove all associated connection data and account configuration from our systems.
1.9 First-Party Conversion Pixel
If you install our JavaScript tracking pixel on your website(s), the pixel collects data from visitors to those websites ("End Users") to provide you with conversion tracking and attribution analytics. In this capacity, you are the data controller for End User data and Coppica acts as a sub-processor.
Data collected by the pixel:
- UTM parameters from the page URL (specifically
utm_content) - Conversion events you explicitly track via the
coppica('track', ...)API (event type, value, reference ID) - A first-party cookie (
_ck_utm, 7-day expiry, Secure, SameSite=Lax) that stores the UTM content parameter to attribute conversions across page views - Timestamp of each tracked event
The pixel does not collect IP addresses, fingerprints, browsing history, or any data beyond the UTM parameter and explicitly tracked conversion events.
Privacy controls:
- Global Privacy Control (GPC): The pixel automatically respects the GPC signal (
navigator.globalPrivacyControl). When GPC is enabled, the pixel deletes any existing tracking cookie and does not send any data. - Programmatic consent: You can integrate the pixel with your cookie consent banner by calling
coppica('consent', false)to disable tracking orcoppica('consent', true)to re-enable it.
It is your responsibility to disclose the use of the Coppica pixel in your own privacy policy and to obtain any required consent from End Users under applicable law (including GDPR and CCPA). We provide the GPC compliance and consent API to support your compliance obligations.
1.10 Meta Platform Disclosures
This subsection consolidates the disclosures relating to data we receive when you connect a Meta account (Facebook or Instagram) to the Service.
Data we collect from your Meta account:
- User identity: Facebook user ID, name, and profile picture, used to label the connection in your Integrations settings.
- Business Manager structure: list of businesses you operate, ad accounts assigned to those businesses, and your role or asset access on each.
- Ad creative: headlines, body text, calls-to-action, destination URLs, and thumbnails for ads in connected accounts.
- Ad insights: impressions, clicks, spend, click-through rate, and conversion actions for ads in connected accounts.
- Facebook Page metadata: page ID, name, category, and your role on managed pages.
- Page post content and engagement: message text, timestamps, and aggregate engagement metrics (impressions, reactions, comments, shares, engaged users) for posts on pages you manage. We do not read individual user comments or private messages.
What we do NOT do with Meta data:
- We do not sell or share Meta data with any third party.
- We do not use Meta data for targeted advertising, audience enrichment, or audience building.
- We do not use Meta data to train AI models.
- We do not retain Meta connection credentials or your Facebook user identifier after you disconnect.
How to delete your Meta data from Coppica:
- In Coppica: open Settings → Integrations → Meta Ads → Disconnect. Connection credentials, account configuration, and the Facebook user identifier are deleted immediately.
- From Facebook: open Settings → Apps and Websites → Coppica → Remove. Facebook calls our Data Deletion Callback, which deletes the same data and returns a confirmation code. You can check the status of your deletion request at
https://coppica.com/deletion-status?code={your_confirmation_code}. - By email: contact support@coppica.com with your account email and a deletion request will be processed within 30 days.
Historical aggregate analyses (such as technique extraction summaries from your own ads) tied to your account remain in Coppica unless you delete your account or request their removal via support@coppica.com.
1.11 Google User Data
Coppica'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.
What we access. When you connect a Google account, Coppica requests only these permissions:
- Google Analytics (
analytics.readonly): the list of GA4 accounts and properties you can access, and read-only report data for the property you choose, such as sessions, users, new users, bounce rate and key events, broken down by date, traffic source and medium, campaign, ad content, landing page and Google Ads campaign and keyword. - Google Ads (
adwords): the list of Google Ads accounts you can access, and read-only reporting data for the account you choose: account currency, campaign and ad group names, ad headlines, descriptions and final URLs, daily cost, impressions, clicks, conversions and conversion value per ad, and the ad behind each Google click identifier (gclid) we already hold for your conversions. Reporting access is read-only. Coppica never creates, edits, pauses or deletes campaigns, ads or budgets in your Google Ads account. The one thing we add to the account is conversion events, and only when you turn on sending for that account, as described in the section on end-client data below. - Google Drive (
drive.file): only the files and folders Coppica creates when you export a draft, and the files you pick in the Google Picker to import. Coppica cannot see any other file in your Drive. - Your Google account email address, name and profile picture, to identify the connected account.
How we use it. We use Google user data only to provide and improve the features you see in Coppica: attribution and return on ad spend reporting for the client you connected, scoring which copy and techniques produced results for that client, answers from Coppica's assistant about that client's performance, writing new copy for that client, and saving or importing documents in Drive.
How we share it. We do not sell Google user data. We do not transfer it to advertising platforms, data brokers or information resellers, and we do not use it to serve, target or retarget ads, or to determine credit-worthiness or for lending. We share it only with the service providers that run Coppica for you, under contracts that require them to protect it: Supabase (storage), Cloudflare (encrypted offsite database backups), Vercel (hosting) and Anthropic (to generate the reports and copy you ask for, without training on it). We also share it when the law requires it, or to investigate security issues or abuse.
AI and machine learning. We do not use Google user data, including data from Google Workspace APIs such as Google Drive, to develop, improve or train generalized or non-personalized AI or machine-learning models, and our AI providers do not train on it.
Human access. Coppica staff do not read your Google user data unless you ask us to for support on specific data, it is needed for security or to investigate abuse, it is required by law, or the data is aggregated and anonymized for internal operations.
Storage and security. Google OAuth tokens are encrypted at rest with AES-256-GCM. Google data is stored in our database in the United States and is encrypted in transit and at rest.
Retention and deletion. You can disconnect a Google integration at any time in Coppica's settings, which deletes the stored tokens. When you disconnect your last Google integration, we also ask Google to revoke Coppica's access. If Google is unreachable at that moment the request can fail, so you can confirm or remove Coppica's access yourself at myaccount.google.com/permissions. To have Google data already synced deleted, email support@coppica.com. Otherwise it is deleted 90 days after your account closes, as set out in section 5.
2. How We Use Your Data
We use your data for the following purposes:
- To provide the Service: Processing your intake form data through our AI pipeline, generating outputs, and storing your results.
- To manage your account: Authentication, billing, subscription management, and customer support.
- To improve the Service: Analyzing aggregate, non-personally-identifying usage patterns to improve performance, features, and user experience. We do not use your individual content (intake forms, bot outputs, or chat histories) to train AI models.
- For security: Detecting and preventing fraud, abuse, and security incidents.
- For communications: Sending transactional emails (account confirmations, billing receipts, service updates). We will only send marketing communications with your explicit consent.
3. Legal Basis for Processing (GDPR)
If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, we process your personal data on the following legal bases:
- Contractual necessity: Processing required to deliver the Service you have subscribed to (intake data processing, output generation, account management).
- Legitimate interests: Security monitoring, fraud prevention, service improvement using aggregate analytics, enforcing our Terms of Service, and providing ad performance analytics for users who connect third-party advertising accounts.
- Consent: Marketing communications and any non-essential cookies. You may withdraw consent at any time.
- Legal obligation: Where we are required by law to retain or disclose data (e.g., tax records, legal requests).
4. Third-Party Service Providers (Sub-Processors)
We share your data with the following sub-processors to deliver the Service. Each sub-processor is bound by contractual data protection obligations:
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Anthropic PBC | AI content generation (Claude API) | Intake form content, user prompts, and data from connected integrations (including Google Analytics, Google Ads and Google Drive data) needed to answer a request | United States |
| Supabase Inc. | Database and authentication | All platform data | United States (AWS) |
| Vercel Inc. | Hosting and edge infrastructure | Request/response data, logs | United States and global edge |
| Stripe Inc. | Payment processing | Billing data, payment information | United States |
| Composio Inc. | OAuth connection management for third-party integrations | Encrypted OAuth tokens, connection identifiers | United States |
| Loops Inc. | Marketing email delivery | Email address, name, contact properties, engagement events | United States |
| E-Signature Service Provider | Electronic document signing and audit trail | Signer names, emails, IP addresses, document contents, signing events | United States |
| Groq, Inc. | Speech-to-text for dictation in browsers without built-in speech recognition | Voice recordings of dictated text | United States |
| Google LLC | AI video transcription and description (Gemini API) | Videos and images from connected ad and social accounts, including any speech, people and on-screen text they contain | United States and other countries where Google maintains facilities |
| SideGuide Technologies, Inc. (Firecrawl) | Reading web pages for website analysis and page reading in chat | Web addresses submitted for reading and the content of those pages | United States |
| SearchApi, LLC (SearchAPI) | Looking up public ads in the Meta Ad Library for Competitive Intelligence and intake enrichment | Brand and competitor names | United States |
| Superdesign Dev Pty Ltd (treg) | Searching public Reddit posts, YouTube comments, Trustpilot reviews and Google ads for Competitive Intelligence and Market Voices | Brand and competitor names and the search words built from your intake answers | Australia |
| Functional Software, Inc. (Sentry) | Error monitoring and session replay | Error details, and replays of sessions where an error occurred, including on-screen text (form inputs are masked) | United States |
| Cloudflare, Inc. | Encrypted offsite database backups (R2) | Encrypted copies of platform data | United States |
| Microsoft Corporation (Clarity) | Session recordings and heatmaps of coppica.com | Clicks, scrolls, page addresses, device and browser details and approximate location. Page text and images are masked on every page outside our public marketing pages, and typed text is masked everywhere | United States |
| Resend Inc. | Transactional email delivery | Email address, name, notification content | United States |
Important note on AI processing: Anthropic processes inputs and generates outputs and does not train on your data under our commercial API agreement. Most requests are not retained; certain premium models retain request data for up to 30 days for safety purposes before deletion, and are never used for training. You can review Anthropic's data processing commitments at anthropic.com/privacy.
5. Data Retention
- Account data: Retained for the duration of your subscription plus 90 days after cancellation.
- Bot outputs and intake forms: Retained for the duration of your subscription. Deleted 90 days after account cancellation.
- Usage logs: Retained for 12 months, then automatically deleted.
- Billing records: Retained as required by applicable tax and financial reporting laws (typically 7 years).
- Third-party integration data: Account configurations, connection credentials, and reference identifiers are deleted immediately upon disconnection or upon receiving a deletion/deauthorization callback from the connected platform. Previously synced data (conversion events, attribution records, contact records, meeting transcripts) is retained per the bot outputs schedule above unless you request earlier deletion.
- Server-side site events: When a customer sends their own site events to Coppica from their server, we record the visitor's consent choices with each event and never store email addresses or phone numbers as plain text. We store two kinds of hash. The first is a keyed hash, which only Coppica can compute and which we use to match the same person across events. The second is the standard unkeyed SHA-256 hash that Meta and Google each document for matching, kept so a customer can send their events to their own ad accounts. We keep the standard hashes only when the visitor has not declined advertising use and, where the law requires marketing consent first (the EEA, the UK and Quebec), has given it. Otherwise only the keyed hash is stored. On the same condition we keep the visitor's IP address and browser details when the customer sends them with an event, and delete them 7 days after the event arrives. When the customer turns on forwarding, we pass those events, on the customer's instructions, to the customer's own Meta and Google Analytics accounts. Page views are deleted after 90 days. Purchases, leads, signups and refunds are retained per the bot outputs schedule above.
- Outgoing conversion reports: The reports our server sends to Meta and Google Analytics about Coppica's own purchases (section 7), and the site events customers forward to their own Meta and Google Analytics accounts, wait in a send queue until delivered. Their contents, which can include an IP address, browser details and a hashed email address, are cleared on delivery, and every queue entry is deleted 30 days after it was created.
- Electronic signature records: Audit trail data, signed document references, and certificates of completion are retained for a minimum of 7 years from the date of execution, regardless of account status. This retention period ensures legal defensibility and compliance with business record retention requirements.
You may request earlier deletion of your data at any time by contacting support@coppica.com.
6. Your Rights
6.1 GDPR Rights (EEA, UK, Switzerland)
If you are located in the EEA, UK, or Switzerland, you have the right to:
- Access: request a copy of the personal data we hold about you.
- Correction: request correction of inaccurate personal data.
- Deletion: request deletion of your personal data (right to erasure).
- Portability: receive your data in a structured, machine-readable format. You can export your data yourself at any time from Settings → Profile → Export your data.
- Objection: object to processing based on legitimate interests.
- Restriction: request restriction of processing while a dispute is resolved.
To exercise any of these rights, contact support@coppica.com. We will respond within 30 days (or the timeframe required by applicable law).
You also have the right to lodge a complaint with your local data protection supervisory authority.
6.2 CCPA/CPRA Rights (California)
If you are a California resident, you have the right to:
- Know: request disclosure of the categories and specific pieces of personal information we collect, use, and disclose.
- Delete: request deletion of your personal information.
- Opt-out of sale or sharing: Coppica does not sell personal information as defined by the CCPA. The Meta Pixel and the server reports to Meta and Google described in section 7 can count as “sharing” for cross-context behavioral advertising under the CCPA. You can opt out at any time on our Required by Law page by turning off marketing cookies. Once you do, the Meta Pixel and new server reports to Meta stop carrying your information, and new reports to Google Analytics are marked as not allowed for advertising. A report about a purchase you already made, or a later refund of it, can still carry the marketing choice you had when you checked out. To have those handled, email us at the address below.
- Non-discrimination: we will not discriminate against you for exercising your CCPA rights.
To exercise your CCPA rights, contact support@coppica.com.
7. Cookies and Tracking
We use the following types of cookies:
- Essential cookies: Session cookies required for authentication, security, and core functionality (including your cookie consent state). These cannot be disabled.
- Preference cookies: Local storage entries for theme preference and UI state (e.g., sidebar collapsed state). These are stored locally and are not transmitted to our servers.
- Analytics cookies: Google Analytics 4 cookies (
_ga,_ga_*) to collect aggregate usage data. Set only with your consent in opt-in jurisdictions (EEA, UK, Quebec). - Session replay (Microsoft Clarity): Across coppica.com, including the app after you sign in, we use Microsoft Clarity (
_clck,_clsk) to record how pages are used: clicks, scrolls, mouse movement and page layout, so we can find and fix the places where people get stuck. On our public marketing pages the recording shows the page as you saw it. Everywhere else, including every page you see while signed in, the text and images on the page are masked before anything leaves your browser, so your clients, your copy and your numbers are never sent to Microsoft. Anything you type is masked on every page. Clarity does receive the address of each page you open, along with your device, browser and approximate location. We tell Clarity only whether a session is signed in or not, never who you are. Recordings are subject to Microsoft's privacy statement. Clarity counts as analytics: it stays off if you turn analytics off in your cookie preferences, and in opt-in jurisdictions it runs only after you allow analytics. - Marketing attribution cookies: Meta Pixel (
_fbp,fr) and Coppica's first-party attribution cookies (_ck_first_touch,_ck_utm) to measure which ads or referring sources brought visitors to Coppica. Set only with your consent in opt-in jurisdictions. - Where you came from, at sign-up: When you create an account, we save the page you first arrived on, the campaign tags on that link (such as
utm_source) and the site that referred you, so we know which ads and links bring people to Coppica. We keep only the page path and those tags, and no other part of the address. We do not save this if you turned marketing off, or if you are in a region where we ask first and you have not said yes.
We do not sell personal data. The Meta Pixel is used to measure Coppica's own ad performance and may be used by Meta to show you Coppica ads on Meta-owned properties (Facebook, Instagram) based on your visit — what's commonly called retargeting. Apart from Meta, Google Analytics and Microsoft Clarity, as described in this section, we do not share your data with advertising or analytics networks. Meta Pixel data is subject to Meta's privacy policy and your consent on Coppica determines whether the pixel fires at all.
When you start or complete a purchase, our server also tells Meta about it directly (Meta's Conversions API), sending a hashed email address, your IP address and browser details, and Meta's cookie IDs if your browser has them, so Meta can tell which ad led to the purchase. The same consent rules apply: if you decline marketing cookies, or you are in an opt-in jurisdiction and have not accepted them, nothing is sent. If we have no record of your choice for a purchase, we send it only with Meta's Limited Data Use setting, and not at all unless we can tell you are outside an opt-in jurisdiction.
When a purchase completes or is refunded, our server also reports it to Google Analytics (the GA4 Measurement Protocol), so a purchase is counted even if your browser blocked the analytics script. We send this only if you accepted analytics cookies at checkout. It carries the Google Analytics ID from your _ga cookie, the session ID, the order ID, the amount, the currency and the plan. It does not include your email address, name, IP address or browser details. Whether Google may use it for advertising follows your marketing choice.
Before these server reports go out, we hold each one briefly in a send queue so it can be retried if Meta or Google is unavailable. A queued Meta report contains your IP address, browser details and hashed email address. We clear those details as soon as the report is delivered and delete every queue entry 30 days after it was created.
For the complete list of every cookie we set, what each does, and how long each lives, see /cookies-are-delicious. To manage your cookie preferences or withdraw consent, visit /required-by-law.
8. Children's Privacy
The Service is not directed at individuals under the age of 18. We do not knowingly collect personal information from anyone under 18. If we become aware that we have collected personal data from a person under 18, we will take steps to delete that information promptly.
9. Data Security
We implement appropriate technical and organizational measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction. These measures include:
- Encryption of data in transit (TLS/HTTPS) and at rest (via our infrastructure providers)
- AES-256-GCM encryption for sensitive credentials (API keys, integration secrets)
- Row-level security (RLS) enforcing multi-tenant data isolation at the database level
- Role-based access controls with service-role key separation between client-side and server-side operations
- CSRF protection on all mutation endpoints
- Rate limiting on API endpoints to prevent abuse
- Input validation and SSRF protection on external URL fetches
- HMAC-based webhook signature verification for inbound integration data
- Regular security audits of our infrastructure and codebase
- Error responses are sanitized to prevent internal system information leakage
No method of transmission or storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.
10. International Data Transfers
Your data is primarily processed in the United States. If you are located outside the United States, your data will be transferred to and processed in the United States where our service providers are located.
For transfers from the EEA, UK, or Switzerland, we rely on Standard Contractual Clauses (SCCs) approved by the European Commission, or other lawful transfer mechanisms, to ensure adequate protection of your personal data.
11. Data Processing for Agency Customers
When agency users process their end clients' data through the Service, the agency acts as the data controller and Coppica acts as a data processor. In this capacity:
- We process end-client data only according to the agency's instructions and for the purpose of providing the Service.
- When a customer connects its own advertising or analytics account, such as a Meta Pixel, Google Ads or Google Analytics, and turns on sending, we send that account the customer's conversion events with hashed email addresses, hashed phone numbers and click identifiers, only on the customer's instruction and only to accounts the customer connects, as set out in section 7.3 of our Terms of Service. We do not send information about a person who has opted out or declined advertising use when that choice reaches us.
- Any paying customer may request a Data Processing Agreement (DPA) by contacting support@coppica.com.
- Our DPA incorporates Standard Contractual Clauses for international transfers, lists all sub-processors with their data processing commitments, and covers data flowing into the Service from connected third-party platforms.
12. Data Breach Notification
In the event of a personal data breach that is likely to result in a risk to your rights and freedoms, we will notify the relevant supervisory authority within 72 hours of becoming aware of the breach, as required by GDPR. If the breach is likely to result in a high risk to you, we will also notify you without undue delay.
For US residents, we will comply with applicable state breach notification laws, including California's requirement to notify affected individuals within 30 calendar days.
13. Changes to This Policy
We may update this Privacy Policy from time to time. If we make material changes, we will notify you by email or by posting a notice on the Service at least 30 days before the changes take effect. The "Last updated" date at the top of this page indicates when this policy was most recently revised.
14. Contact
For questions about this Privacy Policy or to exercise your data rights, contact us at:
Email: support@coppica.com
For GDPR inquiries, you may also contact our designated data protection point of contact at the same email address.
