Data Safety & DPA

Security and privacy at a glance

• Blip does not use customer data to train AI models or to improve models or product features for other customers.
• Blip accesses connected Meta accounts through authorized Meta APIs; Blip does not ask for or store a customer's Meta password.
• Customer content is processed to perform customer-requested workflows and is not sold or disclosed to other customers.
• Optional AI analysis of ad videos will require affirmative customer permission before content is sent to an AI provider.
• Customers may request deletion of account data, creative-strategy records, and associated embeddings.

What Blip processes

Depending on the features a customer enables, Blip processes business contact information; team and account identifiers; authorized Meta ad account, campaign, ad set, targeting-configuration, budget, spend, performance, conversion, and activity data; creative assets and ad copy; templates and drafts; and support communications.

The optional creative-strategy service may process customer-authorized ad videos, images, transcripts, brand and product context, performance data, classifications, embeddings, prompts, and generated insights. These records are logically associated with the relevant customer.

AI data-use commitments

Purpose limitation

Blip uses Google Gemini and Anthropic Claude APIs to perform specific analysis and generation requested for a customer. Blip does not train its own model on customer data, opt customer data into provider model training, or use customer data to fine-tune a provider model.

Consent before creative analysis

Before the upcoming creative-strategy feature sends customer ad videos or other creative content to an AI provider, the Service will provide notice and obtain affirmative permission at the applicable account or workflow level. Declining optional AI analysis will not authorize that content to be sent for the analysis.

Customer isolation

Blip does not disclose one customer's identifiable creatives, account performance, prompts, embeddings, or private insights to another customer, and does not use them to improve recommendations or features for another customer.

Human access

Authorized personnel may access customer insights where reasonably necessary for support or reliability work. Blip personnel do not access the underlying customer creative files for ordinary support.

Security practices

• Transmission: Blip's web application, APIs, and supported provider connections use HTTPS/TLS for transmission over public networks.
• Managed storage: Primary customer and account data is stored using managed Firestore and Neon services, which provide provider-managed encryption at rest.
• Authentication and authorization: Users authenticate through supported identity and platform authorization flows. Blip requests platform permissions needed for enabled workflows and relies on customer-controlled team and connected-account access.
• Infrastructure: The application is hosted using managed Vercel and Railway environments. Secrets used by the application are supplied through managed deployment configuration rather than embedded in the public website.
• Media handling: Media may be temporarily staged or transformed to complete an upload. The creative-strategy service may retain images and thumbnails needed for customer-authorized analysis; analyzed video working copies are designed to be discarded after processing.
• Deletion: Customers can request deletion. Eligible data is removed from active systems, while residual copies may remain until they expire under infrastructure-provider backup cycles or as required by law.

Blip does not currently promise a customer-specific recovery time, recovery point, backup-retention period, penetration-testing cadence, or uptime SLA unless stated in a signed agreement.

Subprocessors and connected services

A subprocessor is a provider that may process personal data on Blip's behalf. Connected advertising and storage platforms may instead process data under the customer's direct relationship and instructions. Actual use depends on the features a customer enables.

Each provider listed below publishes information about a SOC 2 report, attestation, or completed SOC 2 audit. The precise report scope may vary by provider, service, region, and plan. A provider's independent assurance applies to that provider and does not certify Blip itself.

Provider assurance information is available from the official trust or compliance pages for Railway, Vercel, Google Cloud, Neon, Anthropic, Cloudflare, AWS, PostHog, Intercom, Stripe, and Loops.

Customer-directed integrations

Meta, Google Drive, Dropbox, Slack, and TikTok process information when a customer connects or directs use of those services. Their handling of information is also governed by the customer's relationship with them and their applicable terms.

Blip may update this list as the Service changes. Where required by an applicable signed DPA, Blip will give notice before appointing a new subprocessor that materially processes Customer Personal Data and provide a reasonable opportunity to object on data-protection grounds.

Data Processing Addendum

This Data Processing Addendum ("DPA") forms part of the agreement between the customer identified in an order or Blip account ("Customer") and the Blip entity identified in that order or account ("Blip") when Blip processes Customer Personal Data on Customer's behalf. It applies only to that processing and does not create a representation that either party is subject to every privacy law.

1. Definitions and roles

“Customer Personal Data” means personal data contained in Customer Content that Blip processes on Customer's behalf. “Data Protection Law” means privacy or data-protection law applicable to that processing. Terms such as controller, processor, business, service provider, data subject, and processing have the meanings assigned by applicable Data Protection Law.

Customer is the controller or business and Blip is the processor or service provider for Customer Personal Data, except where the law assigns a different role. Each party is responsible for its own compliance obligations.

2. Processing instructions

Blip will process Customer Personal Data only to provide and support the Service, follow Customer's documented instructions, protect the Service, and comply with law. The agreement, Customer's use and configuration of the Service, and written support requests constitute documented instructions. Blip will inform Customer if it believes an instruction violates applicable Data Protection Law, unless legally prohibited.

Blip will not sell Customer Personal Data, retain or disclose it outside the parties' direct business relationship, or combine it with personal data received from another source except as permitted for a service provider under applicable law and necessary to provide the Service.

3. Confidentiality and security

Blip will ensure persons authorized to process Customer Personal Data are subject to confidentiality obligations and will maintain appropriate technical and organizational measures designed to protect it against unauthorized or unlawful access, use, alteration, disclosure, or destruction. Current measures are described above.

4. Subprocessors

Customer generally authorizes Blip to use the subprocessors listed on this page. Blip will require subprocessors to protect Customer Personal Data through written obligations appropriate to the services they provide. Blip remains responsible for its subprocessors' performance of data-protection obligations to the extent required by applicable law and the parties' agreement.

5. Assistance

Taking into account the nature of processing and information reasonably available to Blip, Blip will provide reasonable assistance with data-subject requests, security inquiries, data-protection impact assessments, and consultations required by applicable Data Protection Law. Customer is responsible for responding to requests and for costs arising from assistance beyond standard Service functionality unless caused by Blip's breach.

6. Security incidents

Blip will notify Customer without undue delay after confirming a breach of security that results in accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data. Blip will provide information reasonably available to help Customer meet applicable notification obligations. Notice is not an admission of fault or liability.

7. Return and deletion

Upon Customer's request or termination of the Service, Blip will delete or return eligible Customer Personal Data within a commercially reasonable period, unless retention is required by law. Data in backups will be protected and deleted or overwritten through the applicable provider's ordinary backup lifecycle.

8. International transfers

If applicable Data Protection Law requires a transfer mechanism for Customer Personal Data, the parties will cooperate in good faith to implement an appropriate mechanism, such as then-current standard contractual clauses. A customer requiring executed transfer clauses should contact Blip before submitting regulated data.

9. Information and audits

On reasonable written request, Blip will provide information reasonably necessary to demonstrate compliance with this DPA. If that information is insufficient and applicable law requires an audit, Customer may request a narrowly scoped audit no more than once per year, during normal business hours, at Customer's expense, subject to confidentiality and reasonable safeguards against disruption. The parties will first use available documentation and remote review.

10. Processing details

• Subject matter: delivery and support of Blip's ad management, analytics, integrations, and optional creative-strategy services.
• Duration: the Service term plus the limited retention period described above.
• Nature and purpose: collection, retrieval, storage, organization, transmission, analysis, generation, display, support, and deletion according to Customer's instructions.
• Data subjects: Customer's users, personnel, representatives, creators or partners represented in Customer Content, and other individuals whose personal data Customer submits.
• Data types: business contact and account data; identifiers; platform account and campaign data; creative content; support records; and the other information described on this page.
• Sensitive data: the Service is not designed for special-category, highly sensitive, health, financial-account, or government-identifier data, and Customer must not submit such data unless expressly agreed in writing.

11. Order of precedence and contact

If this DPA conflicts with the main agreement regarding processing of Customer Personal Data, this DPA controls. A signed DPA or negotiated agreement controls over this online DPA. Questions or requests for a signed copy may be sent to shree@withblip.com.