Privacy Policy
Version 5, last updated 2026-11-13
Vibel is a trade name of GetVibel B.V. (KvK 42217195), part of the HAVA Export group. App registrations are currently held by HAVA Export B.V. GetVibel B.V. (KvK 42217195, VAT NL870224293B01) is the data controller for the personal data described in this policy. Until further notice, HAVA Export B.V. (KvK 90977203) handles payments and invoices for Vibel.
Vibel (“Vibel,” “we,” “us”) provides an operations and analytics platform for Shopify merchants. This policy explains what data we collect, why, how long we keep it, and the rights you and your customers have over it. It applies to the Vibel app, its dashboard, and getvibel.com.
Who this applies to
What we collect
Store and commerce data: read via the Shopify API under the scopes you approve at install, orders, products, inventory, fulfillments, and the customer fields needed for order and shipping analytics (name, email, address, order history). We do not request scopes beyond what the product needs.
Connected-tool data: if you optionally connect Klaviyo, Meta, Google Ads, GA4, Search Console, TikTok, Pinterest, Stripe, AfterShip, Gorgias, Zendesk, Monday, or QuickBooks Online, we read performance, ticket, or accounting data from that tool, using the access you grant, solely to power your dashboard, watchers, and reports. We do not push your Shopify or customer data into these tools, we only read from them.
Publishing you approve: if you turn on publishing for a connected account (Facebook Page, Instagram, TikTok, Pinterest, or YouTube), Vibel can publish posts, pins, or videos to that account using the permission you grant:
pages_manage_posts and instagram_content_publish (Meta), video.publish (TikTok), pins:write and boards:write (Pinterest), youtube.upload (YouTube). Vibel only publishes content you created or approved in Vibel, and only after you press Publish or approve a schedule. Nothing is posted by itself. Vibel can edit or delete only posts it published for you. We store the post id and link so you can see what was published. Disconnecting the account deletes the access token; you can also revoke access in the platform's own settings at any time.Comments on your Facebook Page: with
pages_read_user_content, Vibel reads comments people leave on your own Facebook Page posts and shows them in your comments queue, sorted by type (question, complaint, praise). This is read-only: Vibel does not post, hide, or delete comments on Facebook.Page insights: with
read_insights, Vibel reads your own Facebook Page's reach and views for the last 28 days and shows them next to that Page's name inside your dashboard. Only Pages you connected; nothing is posted or changed.Meta (Facebook) Ads: when you connect Meta, we use the Marketing API to read the list of ad accounts you manage (so you can pick which one to connect) and that account's performance data (spend, impressions, clicks, conversions, and ROAS), shown only to you inside your own dashboard. Your Meta access token is stored encrypted in our secrets vault, never exposed to the browser or to other users, and deleted when you disconnect the source.
TikTok Shop: when you connect TikTok Shop, we read the authorized shop ID, name, region and shop cipher, and your shop's orders, including order IDs, dates, status, totals, currency and product line items. The order API response may contain buyer details; Vibel does not store buyer names, addresses or contact details from it. We use the stored fields for your shop dashboard. Creator sample-request records from earlier imports contain a TikTok creator ID, handle, product and request date. New sample-request imports are currently unavailable. These creator records are deleted after 90 days, or when the connection is disconnected, whichever comes first. Synced orders and sample-request records for a connection are deleted when you disconnect it. Access and refresh tokens are kept encrypted in our secrets vault and removed on disconnect when no other connection uses them. To revoke the app's authorization at TikTok, use Seller Center > App Store > My apps. Storage locations and service providers are listed on our subprocessors page. We do not sell this data or use it for advertising or model training.
Usage data: log-in activity, feature usage, and error diagnostics, used to operate and improve the product. We record approximate sign-in location signals to protect accounts against abuse.
Content you send us: if you use the AI assistant or ask-anything bar, the prompts you write and the store data needed to answer them.
How we use it
How we protect your data
Encryption in transit: all traffic between your browser, Vibel, and every connected platform uses TLS (HTTPS); we make no unencrypted requests.
Encryption at rest: all stored data is encrypted at rest in our managed database (Supabase/PostgreSQL). OAuth tokens, refresh tokens, and API keys are additionally stored in an encrypted secrets vault, referenced only by opaque ids, decrypted server-side at the moment of an API call, and never sent to the browser, logged, or exposed to other users.
Tenant isolation: every table is protected by database row-level security, so one merchant's data can never be read by another merchant's account.
Least privilege: we request only read-only scopes from connected platforms, and only the narrowest scopes needed for the features you use.
Access control: production data access is restricted to authorized personnel for support, security, and legal compliance only, and is logged.
Deletion: disconnecting a source deletes its stored credentials immediately. For TikTok Shop and YouTube, disconnecting also deletes the data synced from that source (see their sections above). For every other source, the data already synced stays in your workspace after you disconnect; ask us to delete it through our data deletion page. Uninstalling the app or deleting your account triggers deletion of your stored data (see Retention below).
Incident response: if a breach affects your personal data, we will notify you and the competent authorities without undue delay, in line with GDPR requirements.
Google user data (GA4 & Search Console)
When you connect Google Analytics 4 (scope
analytics.readonly) or Google Search Console (scope webmasters.readonly), we read only aggregated reporting data (sessions, engagement, conversions; query impressions, clicks, and positions) to display it in your own dashboard. This data is used solely to provide the analytics features you see; it is never used for advertising, never sold, never transferred to third parties except the subprocessors listed below as needed to run the service, and never used to train AI models. No human reads this data except with your consent, for security or abuse investigation, or where required by law. Your Google OAuth tokens are protected exactly as described above (encrypted vault, server-side only) and are deleted when you disconnect Google or uninstall Vibel; stored Google reporting data is deleted with your account.YouTube API data
What we read. If you connect your YouTube channel (Settings → Connections → YouTube), we use YouTube API Services with two read-only permissions,
youtube.readonly and yt-analytics.readonly. We read your channel's id and name, the list of your own uploaded videos and Shorts (title, publish date, duration, link), and their results: views, likes, comments, shares, average view duration, and subscribers gained. If you also turn on uploading, Vibel uses youtube.upload to upload a video you approved to your own channel (private by default). Vibel never edits, deletes, or comments on your other videos.Why. To show you which of your videos work, next to your ad and store data, in your own Vibel dashboard and trial board. The data is shown only to you and the team members you invite. It is never sold, never used for advertising, never used to train AI models, and no human reads it except with your consent, for security or abuse investigation, or where required by law.
How long we keep it. The access token is stored encrypted. Video results are refreshed by a daily sync while you are connected. When you disconnect YouTube in Vibel, we immediately revoke Vibel's access at Google and delete the YouTube data we stored for that channel, including synced videos, their metrics and any links to them. The same happens automatically if you revoke Vibel's access in your Google security settings, and we delete any YouTube data that has not been refreshed within 30 days. For everything else, see data deletion, or email privacy@getvibel.com.
How to revoke access. Disconnect YouTube in Vibel (Settings → Connections), or remove Vibel in your Google security settings.
By using the YouTube connection you agree to be bound by the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy.
Product usage events
Legal basis (GDPR)
Data processing agreement
Retention
Subprocessors
| Subprocessor | Purpose | Location |
|---|---|---|
| Supabase | Database, authentication, encrypted secrets vault, file storage | EU (Germany) and US |
| Vercel | Application hosting and edge network | US |
| Anthropic | AI processing (Claude API) for ranking, summaries, and drafted content | US |
| OpenAI | AI-visibility probing: asks a tracked search prompt to check whether your brand appears in the answer | US |
| Google (Gemini) | AI-visibility probing, same purpose as OpenAI above | US |
| Perplexity | AI-visibility probing, same purpose as OpenAI above | US |
| Resend | Transactional email (password reset, digests, alerts) | US |
| Stripe | Payment processing for the Vibel Connect account and the billing flows built on it | US / EU |
| Shopify | App billing (subscription and usage-based charges) and the store connection itself | Global (Shopify-operated) |
Most third-party connectors (Klaviyo, Gorgias, and the rest of the list in our sub-processor list) are sources you choose to read from, not recipients of your Shopify data - we do not push your data into them.
How brand data reaches ad platforms
For this flow, you (the merchant) are the controller and Vibel acts as your processor, sending the data on your instruction and only to the platform(s) you choose to enable, per our Data Processing Agreement. Turning a platform off in Settings stops further sends to that platform immediately. The current destinations:
- Meta: hashed email, phone, name, city, and postcode of the customer who placed the order; order value and currency
- Google: hashed email, phone, name, city, and postcode of the customer who placed the order; order value and currency
- Pinterest: hashed email, phone, name, city, and postcode of the customer who placed the order; order value and currency
- TikTok: hashed email, phone, name, city, and postcode of the customer who placed the order; order value and currency
The Vibel pixel
Vibel Reply (Instagram/Facebook DM automation)
DM-to-order matching. Where you connect both Vibel and Vibel Reply for the same store, Vibel matches a Reply conversation to a Shopify order placed by the same shopper, using signals such as a tracked link click, a discount code, or a matched contact identifier, so you can see which DM conversations led to a sale. This matching runs on your own store's data and is shown only to you; it is not used to build a cross-brand profile of an individual shopper.
Chat checks. Where Reply's AI drafts or sends a reply, Vibel and Reply run automated checks on that content (for example, against Meta's messaging rules and your own configured guardrails) before it sends, and keep a record that the check ran and what it found, to show you why a message was sent, held, or blocked.
Consent for the people you message. Reply records, in an append-only consent log, what a person agreed to, when, and under what wording, before you send them a marketing message; a comment asking for one reply is not treated as marketing consent. See Vibel Reply's own Privacy Policy for the full detail of that record.
Retention. Reply conversation, consent, and DM-to-order match data is kept on Reply's own systems under Reply's Privacy Policy; Vibel stores only the matched order/attribution result, not the DM content itself, and deletes it on the same schedule as the rest of your account data (see Retention above).
Anonymous cross-brand learning
Assignment
International transfers
Shopify GDPR webhooks
customers/data_request: we log the request against the relevant store so you, the merchant, can fulfil your customer's access request; Vibel holds only order-linked fields (name, email, address, order history), not a separate customer profile.
customers/redact: we delete the stored customer's personal data (matched by customer ID or email) from our customer records and derived per-customer views for that store.
shop/redact: sent by Shopify 48 hours after uninstall; we delete that store's order data, product data, customer records, and derived customer projections, and mark the connection disconnected.