Blip logo
Blip
Blip logo
Blip
Bulk Launch Ads
Post ID Scaling
Partnership Ads
AI Placement
Instagram Whitelisting
Drive & Dropbox
Saved Templates
Analytics
Pricing
Blog

Privacy

Privacy Policy

This policy explains what Blip processes, why we process it, and the choices available to customers and users.

Last updated August 10, 2026

1. Scope and roles

This Privacy Policy applies to Blip's websites, applications, and related ad-management and creative-strategy services (collectively, the "Service"). “Blip,” “we,” and “us” refer to the Blip entity identified in your order, subscription, or account.

Blip generally acts as a processor or service providerwhen it handles advertising data and content on a customer's instructions. Blip acts as a controller or businessfor account administration, billing, product analytics, support, security, and its own business operations. Customers remain responsible for their instructions to Blip and for their own legal basis, notices, and permissions.

2. Information we process

  • Account and contact data: name, email address, profile information, organization or team membership, account identifiers, and support communications.
  • Connected-platform data: identifiers and access credentials needed to connect authorized Meta, Google Drive, Dropbox, TikTok, Slack, or other accounts; selected ad accounts; campaign, ad set, ad, audience-configuration, budget, spend, delivery, conversion, and performance data; and platform activity records made available through authorized APIs.
  • Customer content: images, videos, copy, landing-page URLs, naming conventions, templates, drafts, brand materials, product information, and other files or instructions submitted to the Service.
  • Creative-strategy data: customer-authorized ad content, transcripts, classifications, embeddings, performance context, prompts, generated insights, recommendations, and other outputs produced for the customer.
  • Billing and transaction data: subscription status, plan, invoices, and related transaction metadata. Payment card details are handled by our payment provider rather than stored by Blip.
  • Usage data: configured feature interactions, workflow and session events, diagnostic events, and cookie or similar-technology identifiers where enabled.

Blip does not intentionally request raw personal information about individual ad viewers. Advertising platforms may provide aggregated reporting, audience segments, and conversion metrics selected by the customer.

3. How we use information

  • Provide, operate, secure, troubleshoot, and support the Service.
  • Authenticate users and connect to customer-authorized advertising and storage platforms.
  • Create, upload, organize, and manage ads and related campaign settings as directed by the customer.
  • Display analytics and generate customer-specific recommendations, summaries, classifications, and creative insights.
  • Process payments, communicate about accounts, and respond to support requests.
  • Monitor reliability, understand feature usage, prevent abuse, and comply with legal obligations.

4. AI processing and customer isolation

No model training: Blip does not use customer content, connected Meta account data, Google user data, prompts, embeddings, or AI outputs to train foundation models or to improve a model for the benefit of other customers.

Blip may use Google Gemini and Anthropic Claude APIs to perform customer-requested analysis or generation. Data is sent only as needed to produce the requested result for that customer. Blip does not sell customer data or disclose one customer's identifiable content, performance data, or private insights to another customer.

Before a feature sends ad videos or other customer content to an AI provider for creative-strategy analysis, Blip will provide notice and obtain affirmative permission through the Service or a written agreement. Customers may decline that optional processing. Blip does not use customer data to fine-tune a provider model.

5. Google API data

When a user selects files from Google Drive, Blip accesses only the files the user selects and processes them to complete the requested action, such as transferring media to an advertising platform. Blip does not use Google user data for advertising, model training, or unrelated analytics.

Blip's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Temporary working copies created to complete a user-requested transfer are removed after the transfer workflow finishes, subject to operational logs and provider backup cycles.

6. When information is disclosed

Blip may disclose information:

  • to infrastructure, database, AI, analytics, support, payment, communications, and storage providers that help operate the Service;
  • to Meta and other connected platforms when a user directs Blip to retrieve information or create or modify ads;
  • to members of the customer's organization according to the customer's account and team configuration;
  • when required by law, legal process, or to protect rights, safety, and the integrity of the Service; or
  • in connection with a merger, financing, acquisition, or sale of assets, subject to appropriate confidentiality protections.

Blip does not sell customer personal information or customer content. The current vendor list and processing purposes are available on the Data Safety & DPA page.

7. Support access and confidentiality

Personnel may access account information and customer insights when reasonably necessary to provide support, maintain the Service, investigate security or reliability issues, or comply with law. Blip personnel do not access customer creative files for ordinary support. Personnel with access are expected to handle nonpublic customer information confidentially and only for authorized purposes.

8. Retention and deletion

Blip retains information while an account is active and as reasonably necessary to provide the Service, maintain business and security records, resolve disputes, and comply with law. Different records may have different retention periods based on their purpose.

A customer may request deletion of its account data, creative-strategy records, and associated embeddings by contacting us. Blip will delete eligible data from active systems within a commercially reasonable period, subject to legal obligations, fraud-prevention records, and provider backup cycles. Backup copies may remain until overwritten or expire under the applicable provider's schedule.

9. Security

Blip uses safeguards appropriate to the nature of the Service, including HTTPS/TLS for network transmission, authenticated access, provider-managed encryption at rest for primary databases, scoped platform permissions, and managed cloud infrastructure. No method of transmission or storage can be guaranteed completely secure. More information is available on our Data Safety page.

10. Cookies and analytics

Blip uses cookies, local storage, sessions, and similar technologies for authentication, workflow continuity, preferences, security, support, and product analytics. Our website and application may use services such as PostHog, Google Tag Manager, and Intercom. Browser settings can limit some technologies, but doing so may affect Service functionality.

11. International processing

Blip and its providers may process information in the United States and other countries where they operate. Where applicable law requires transfer safeguards, Blip will use an appropriate contractual or legal transfer mechanism.

12. Privacy choices and rights

Depending on applicable law, individuals may have rights to request access, correction, deletion, restriction, objection, or portability. Because Blip often processes data on a customer's behalf, we may direct a request to the relevant customer. Users can revoke a connected platform's access through that platform's settings and can contact Blip at shree@withblip.com.

13. Children

The Service is intended for businesses and is not directed to children. Blip does not knowingly collect personal information from children under 16.

14. Changes and contact

Blip may update this policy as the Service and applicable requirements change. We will update the date above and provide reasonable advance notice of material changes when appropriate. Questions and requests may be sent to shree@withblip.com.

shree@withblip.com
Blips use and transfer of information received from Google APIs to any other app will adhere to Workspace API User Data and Developer Policy, including the Limited use of user data.
Privacy Policy | Blip