Skip to main content
GDPR Article 28

Data Processing Agreement

This Data Processing Agreement ("DPA") forms part of the agreement between Cresva, Inc. ("Processor") and the customer ("Controller") for the provision of the Cresva Service. It governs how we process personal data on your behalf.

Last updated: October 18, 2026

Legal name: Cresva, Inc. • DPA inquiries: hello@cresva.ai

For Agency customers and large portfolios

This DPA applies automatically to all customers on paid plans. It covers GDPR, UK GDPR, and CCPA requirements. You can request a countersigned copy or a custom DPA for enterprise needs.

Request a Countersigned DPA →

1. Overview & scope

This DPA applies to the processing of personal data by Cresva on behalf of the Controller in connection with the provision of the Cresva Service. It supplements the Terms of Service and is incorporated by reference.

This DPA covers:

  • Processing of customer marketing data from connected ad platforms
  • Processing of end-user personal data through the Service
  • GDPR (EU), UK GDPR, and CCPA/CPRA compliance obligations
  • Standard Contractual Clauses (Annex) for international transfers

In the event of any conflict between this DPA and the Terms of Service, this DPA shall prevail with respect to data protection matters.

2. Definitions

"Controller"

The customer entity that determines the purposes and means of processing personal data through the Cresva Service.

"Processor"

Cresva, Inc., which processes personal data on behalf of the Controller to provide the Service.

"Personal Data"

Any information relating to an identified or identifiable natural person, as defined by applicable data protection law.

"Subprocessor"

A third party engaged by the Processor to process personal data on behalf of the Controller.

"Data Breach"

A breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to personal data.

"SCCs"

Standard Contractual Clauses approved by the European Commission (2021/914) for the transfer of personal data to third countries.

3. Roles & responsibilities

Controller Responsibilities (Customer)

  • Determine the lawful basis for processing
  • Provide clear and documented processing instructions
  • Ensure data subjects are properly informed
  • Respond to data subject requests (with Processor assistance)

Processor Responsibilities (Cresva)

  • Process data only on documented instructions from the Controller
  • Implement appropriate technical and organizational measures
  • Assist the Controller with data subject rights requests
  • Notify Controller of data breaches without undue delay
  • Ensure confidentiality obligations on all personnel

4. Processing details

The following details the processing activities performed under this DPA:

Subject Matter

Provision of marketing analytics, AI insights, and forecasting services

Duration

For the duration of the service agreement plus retention period

Nature & Purpose

Collection, storage, analysis, and visualization of marketing performance data

Types of Data

Campaign metrics, ad performance, access tokens for connected platforms, usage analytics, and the Controller's store data from a store it connects: orders (totals, line items, discounts, refunds, currency, dates and order source), products, inventory and locations, and the buyer's email address and customer ID where the store provides them, the buyer's visit trail and ad click identifiers for the order, and the buyer's marketing consent on the order. Where the Controller enables Agent Commerce: the shipping address and parcel tracking an agent provides at checkout, a reviewer's name on a product review, the IP address of each caller to the agent storefront, and negotiation session identifiers and the order data they produce.

Data Subjects

The Controller's employees and team members who use the Service, and the Controller's customers whose orders are in the store data the Controller connects

Special Categories

None. We do not process special category data under this DPA.

5. Processor obligations

As Processor, Cresva commits to the following obligations under Article 28 GDPR:

Documented instructions

Process data only on the Controller's documented instructions, including with respect to transfers

Confidentiality

Ensure all authorized personnel have committed to confidentiality or are under an appropriate statutory obligation

Security measures

Implement all measures required by Article 32 GDPR (see Section 6)

Subprocessor management

Engage subprocessors only with prior authorization and binding DPAs (see Section 7)

Assistance with obligations

Assist the Controller with DSARs, DPIAs, and compliance with Articles 32–36 GDPR

Audit rights

Make available all information necessary to demonstrate compliance; allow and contribute to audits

6. Security measures

In accordance with Article 32 GDPR, we implement the following technical and organizational measures:

In transit

TLS for connections to the Service and from the Service to its subprocessors

At rest

Database (Neon) encrypted with AES-256 by Neon; stored files (Vercel Blob) encrypted by Vercel; connected-platform access tokens also encrypted by the Processor with AES-256-GCM. The cache (Upstash Redis) is not encrypted at rest and holds no store order data or personal data of the Controller's customers

Access control

Every request is checked against the user's role in the brand and company it reads; writes to connected ad and store accounts pass one write gate that records the approver

Backups

Point-in-time database history kept by Neon for 7 days

7. Subprocessors

The Controller provides general written authorization for the Processor to engage subprocessors. The current list of subprocessors:

Hosting and infrastructure

  • Vercel: Application hosting, CDN, file storage (Vercel Blob) and web analytics. Data: All application traffic; files you upload or we generate; page views with identifiers removed from URLs. Region: Singapore (application functions, sin1) and the United States (browser extension functions, iad1); pages are served from the edge nearest the visitor. Retention: Request logs per Vercel's plan retention; files until deleted.
  • Inngest: Background job orchestration. Data: Job identifiers and ids of the records a job works on. Region: Per the vendor's data processing terms. Retention: Per Inngest's event retention.
  • jsDelivr: Public script CDN for charts, previews and code sandboxes the agents generate. Data: The viewer's IP address and browser headers when a generated preview loads a script. No content you create is sent. Region: Global. Retention: Per jsDelivr's terms.
  • Tailwind Labs: Stylesheet CDN for landing page mockups the analyzer generates. Data: The viewer's IP address and browser headers when a generated mockup is opened. No content you create is sent. Region: Global. Retention: Per Tailwind Labs' terms.

Data storage

  • Neon: Primary PostgreSQL database. Data: All account, brand and connected-platform data. Region: Singapore (AWS ap-southeast-1). Retention: Until deleted by you or by our retention schedule; Neon keeps point-in-time history for 7 days, so deleted data leaves backups within 7 days.
  • Cloudflare R2: Storage for generated video creatives. Data: Video, image and audio assets generated for your creatives. Region: Global. Retention: Until deleted.
  • Upstash: Cache and rate limiting (Redis). Data: Cached query results, answers and generated pages, keyed by brand. Region: United States. Retention: Each entry expires, between 4 hours and 30 days.

AI services

  • OpenAI: Language, vision, embedding and image models. Data: Your questions, the brand data needed to answer them, and generated content. Region: United States. Retention: Chat and response requests are sent with store set to false, which turns off OpenAI's stored completions, and a pseudonymous tenant identifier. OpenAI keeps API inputs and outputs for abuse monitoring for up to 30 days unless zero data retention is agreed; embedding and image requests carry no such setting. Training: Not used to train OpenAI models unless the customer opts in; API data kept up to 30 days for abuse monitoring (developers.openai.com/api/docs/guides/your-data).
  • Anthropic: Language models for agents, planning and research. Data: Your questions, the brand data needed to answer them, and agent working context. Region: United States. Retention: Per Anthropic's commercial terms; requests carry a pseudonymous tenant identifier. Training: Not used to train Anthropic models by default (privacy.claude.com, "Is my data used for model training?").
  • Google (Gemini API): Image and video generation and AI visibility checks. Data: Generation prompts, reference images and product queries. Region: United States. Retention: Per Google's Gemini API terms. Training: Paid services: not used to improve Google products. Unpaid services: used to improve them (ai.google.dev/gemini-api/terms).
  • Perplexity: AI visibility checks. Data: Brand, category and product queries. Region: Per the vendor's data processing terms. Retention: Per Perplexity's API terms. Training: Not retained and not used to train models (docs.perplexity.ai/guides/privacy-security).
  • Replicate: Image generation. Data: Image prompts. Region: Per the vendor's data processing terms. Retention: Inputs, outputs and logs are removed by Replicate after one hour. Training: Its terms do not say API data is used for training; inputs, outputs and logs are deleted after one hour.
  • Sync Labs: Lip-sync for generated video. Data: Generated video and audio for a creative you requested. Region: Per the vendor's data processing terms. Retention: Per Sync Labs' terms. Training: Its terms do not say; lip-sync is switched off for every brand, so nothing is sent today.
  • ElevenLabs: Voice generation for video creatives. Data: Script text for a creative you requested. Region: Per the vendor's data processing terms. Retention: Per ElevenLabs' terms. Training: May be used to improve ElevenLabs models unless the account opts out (help.elevenlabs.io, "Is my data used to improve ElevenLabs AI models?"); voice-over is switched off for every brand, so nothing is sent today.

Observability

  • Langfuse: AI request tracing. Data: Model name, token counts, latency and pseudonymous identifiers. Prompt and answer content only if we enable content capture, and then redacted. Region: European Union. Retention: Per our Langfuse project settings. Only when Langfuse keys are configured.
  • Sentry: Error tracking. Data: Error details with secrets and personal data redacted, and account identifiers. Region: United States. Retention: Per our Sentry project settings.
  • Better Stack: Log storage. Data: Application logs, with secrets redacted and email addresses replaced by a hash. Region: Per the vendor's data processing terms. Retention: Per our Better Stack source settings. Only when a Better Stack source token is configured.

Analytics

  • PostHog: Product analytics. Data: Usage events and page paths with identifiers and query strings removed. Region: United States. Retention: Per our PostHog project settings. Only after you consent to analytics.
  • Google Analytics, Google Tag Manager and Meta Pixel: Advertising and analytics measurement on public cresva.ai marketing pages. Data: Marketing page views and clicks. Never loaded inside the signed-in app. Region: United States. Retention: Per Google's and Meta's terms. Only after you consent to analytics or marketing cookies.

Communications

  • Resend: Transactional and report email. Data: Recipient addresses and message content. Region: United States. Retention: Per Resend's terms.
  • Email relay (SMTP): Sign-in links and team invitations. Data: Recipient address and the message. Region: Per the vendor's data processing terms. Retention: Per the vendor's terms.
  • Slack: Alerts and reports to the Slack workspace you connect. Data: Message content you asked to receive in Slack. Region: United States. Retention: Per your Slack workspace settings.

Payments

  • Stripe: Subscription billing. Data: Billing name, email and payment details, and your account id. Region: United States. Retention: Per Stripe's terms.

Integrations

  • Composio: Connections to third-party apps you choose to link. Data: The authorization you grant and the requests you make through it. Region: Per the vendor's data processing terms. Retention: Until you disconnect the app.

Research and search

  • Google (Custom Search, PageSpeed and Chart APIs): Image search, page speed checks and QR code images. Data: Search queries, public page URLs, and the text of a QR code you ask for. Region: United States. Retention: Per Google's API terms.
  • ScreenshotOne: Screenshots of public web pages for page analysis. Data: The public URL to capture. Region: Per the vendor's data processing terms. Retention: Cached by the vendor for 24 hours.
  • Tavily: Web search for research and competitor monitoring. Data: Search queries. Region: Per the vendor's data processing terms. Retention: Per Tavily's terms.
  • Brave Search: Image search. Data: Search queries. Region: Per the vendor's data processing terms. Retention: Per Brave's API terms.
  • SerpAPI: Search result checks for AI visibility. Data: Search queries. Region: Per the vendor's data processing terms. Retention: Per SerpAPI's terms.

Security

  • Cloudflare Turnstile: Bot protection on public forms. Data: A challenge token and your IP address. Region: Global. Retention: Per Cloudflare's terms.

New subprocessors: We will notify the Controller at least 30 days before engaging a new subprocessor, providing the Controller with the opportunity to object. If no objection is raised within 14 days, consent is deemed given.

8. International transfers

Personal data may be transferred to the United States where Cresva operates. We ensure adequate protection through:

Standard Contractual Clauses

EU Commission-approved SCCs (2021/914) are incorporated into this DPA as an Annex. Module Two (Controller to Processor) applies.

UK International Data Transfer Addendum

For UK GDPR, the UK IDTA is incorporated alongside the SCCs.

Supplementary Measures

Encryption, pseudonymization, access controls, and Transfer Impact Assessments as recommended by the EDPB.

9. Breach notification

Breach Notification Timeline

  • Without undue delay: Processor notifies Controller of a Data Breach without undue delay, and no later than 72 hours after becoming aware of it
  • Notification includes: Nature of breach, categories of data, approximate number of data subjects, likely consequences, and measures taken
  • Ongoing cooperation: Processor shall cooperate with Controller and take reasonable steps to mitigate the breach

10. Data subject requests

Cresva will assist the Controller in fulfilling its obligations to respond to data subject requests (DSARs) under applicable data protection law:

  • If we receive a DSAR directly, we will promptly redirect it to the Controller
  • We will provide technical assistance to fulfill access, rectification, erasure, portability, and restriction requests
  • An owner or admin can download everything Cresva holds for the company, or for one brand, as a JSON file from Settings, Company, Export your data, at any time while the account is open.
  • Response assistance will be provided within 10 business days of the Controller's request

11. Data return & deletion

Upon termination of the service agreement or at the Controller's written request:

At termination, at the Controller's choice:

  • Data export: An owner or admin can download everything Cresva holds for the company, or for one brand, as a JSON file from Settings, Company, Export your data, at any time while the account is open. We will also send an export on written request.
  • Deletion: When the Controller deletes the company in Settings or asks us in writing, we delete its personal data within 30 days (the deletion runs 7 days after it is asked for, so it can be stopped), and a connected store's data within 30 days after the Controller uninstalls our app for that store
  • Inactive companies: A company with no paid plan and no sign-in for 12 months is erased. Its owners and admins are warned by email 30 days and 7 days before. Signing in, using an API key or starting a paid plan cancels it.
  • Backups: Deleted data leaves the database backups as they roll over, which takes 7 days
  • Certification: Written confirmation of deletion available upon request

Exceptions: Data required by law to be retained (e.g., billing records for tax compliance) will be retained for the legally mandated period and then securely deleted. Where a Controller's brand has a completed Agent Commerce transaction (an accepted negotiation with an order reference), we retain that transaction's records as a matter of ordinary commercial record-keeping, even after termination.

12. How to execute a DPA

Need a signed DPA?

This DPA applies automatically to all paid plans. For a countersigned copy, custom amendments, or enterprise DPAs, contact us.

Email: hello@cresva.ai (subject: "DPA Request")

Company: Cresva, Inc.

Turnaround: Countersigned DPA within 5 business days