Privacy Policy

Last updated: October 28, 2026

This policy explains what personal data BetterPopup handles, why, and what control you have over it. It covers both the data we hold about our own customers and the visitor data we process on their behalf: two different roles with two different sets of rules, set out in section 2.

Privacy at a glance. Signup emails and phone numbers are encrypted in our database. We do not store visitors' IP addresses. Decisions about who sees a popup are made in the visitor's own browser, so their visit history stays on their device. Browsers that send Global Privacy Control get no lasting identifier from us. We load no Google Fonts and no advertising trackers on your store.

1. Who we are

BetterPopup is operated by Digitonica SRL, a Romanian company registered with the Trade Register under J18/1195/2022, fiscal code (CUI) 46142569, registered office at Str. Dr. Victor Gomoiu, Craiova, Dolj, Romania. Our representative is Marius Claudiu Limban.

For privacy questions, write to [email protected] or call +40 756 029 780. We are not required to appoint a Data Protection Officer under Art. 37 GDPR, and because we are established in Romania, an EU member state, no Art. 27 EU representative is required.

2. The two roles we play, and why it matters

BetterPopup handles personal data in two very different capacities. Almost every question about your data has a different answer depending on which one applies, so this policy is built around the distinction.

Whose dataOur roleWhat that means
Our customers: the people who sign up for a BetterPopup account, and visitors to betterpopup.comControllerWe decide why and how this data is processed. Sections 3 to 6 and 8 to 14 describe it.
Our customers' visitors and subscribers: people who see or sign up through a popup on a customer's siteProcessorThe customer is the controller and decides what is collected and why. We only act on their instructions. Section 7 describes it.

If you signed up through a popup on a shop and want your data removed, contact that shop. They control it. We hold it on their behalf and cannot decide to delete or disclose it without their instruction. If you are not sure who to ask, email [email protected] and we will point you to the right controller.

3. Data we collect as controller

Account data

Your name, email address, the URL of the site or store you connect, your company or workspace name, and your authentication credentials. Sign-in is handled by Clerk; we never see or store your password in plain text.

Billing data

Your plan, subscription status, billing period and invoice history. Card payments are processed by Stripe, or by Shopify if you installed through the Shopify App Store. We never receive or store full card numbers. We keep the customer reference and subscription status needed to run your account.

Usage and technical data

How you use the dashboard and builder, which features you open, plus server logs and diagnostic information needed to keep the service secure and working. Product analytics run through PostHog and are only enabled where you have consented (see section 8). We also keep a log of who in your team viewed or exported your subscriber list, so you and we can answer "who accessed this data?".

Onboarding and brand data

When you complete the first-run wizard we store your answers and the brand details we detect from your site (such as your logo and colours) so we can pre-fill your first popup.

Support and marketing data

Messages you send us and our replies, and, where you have opted in or we are otherwise permitted, the marketing source that brought you to us (referrer and UTM parameters).

You must be at least 16 years old to create an account. We do not knowingly collect data from children.

5. How we use data, and what we never do

We use the data above to operate and secure the service, to bill you, to support you, and to make the product better.

We do not sell personal data. We do not share it with advertising networks, do not use it to build advertising profiles, and do not use your subscribers' data for any purpose other than delivering the service to you. We may publish aggregated statistics, such as average opt-in rates across stores, that cannot identify you, your visitors or your subscribers. We do not carry out automated decision-making or profiling that produces legal or similarly significant effects (Art. 22 GDPR).

6. Who we share data with

We share personal data only with the providers below, who process it on our behalf under a data processing agreement and may not use it for their own purposes.

ProviderPurposeLocationSafeguard
ClerkAuthentication and account managementUnited StatesSCCs / EU-US DPF
StripePayments and subscription billingUnited States / IrelandSCCs / EU-US DPF
ShopifyApp installation, billing and store integration, for Shopify installs onlyCanada / United StatesSCCs
ResendTransactional and notification emailUnited StatesSCCs / EU-US DPF
PostHogProduct analytics and error tracking, consent-basedUnited StatesSCCs / EU-US DPF
CloudflareCDN, DNS and abuse protection for our site and embed script, and storage of encrypted database backups (R2)Global edge network; backups in North AmericaSCCs / EU-US DPF
HetznerApplication hosting and database infrastructureUnited States (provider incorporated in Germany)SCCs

The current list is maintained in our DPA, which also explains how we notify customers before adding a new sub-processor.

Google Fonts in the builder

When the popup builder previews a font, your browser loads it from Google Fonts, so Google receives your IP address as part of that request. This happens only in our dashboard. Popups on your store use fonts served from our own CDN and never contact Google.

Integrations you choose to connect

When you connect an email or SMS platform (Klaviyo, Mailchimp, Omnisend, Attentive, Postscript, Drip and others), we send captured signups to it at your instruction. Those platforms are not our sub-processors: they act under their own agreement with you, and their own privacy policies govern what happens to the data once it arrives. You choose whether to connect them and can disconnect at any time.

We may also disclose data where the law requires it, to enforce our terms, or in connection with a merger or acquisition, in which case we will notify affected customers.

7. Visitor and subscriber data: what the popup collects

This section describes data we process on behalf of our customers. Each customer is the controller and decides what to collect; the technical detail below is what our software is capable of collecting when a customer runs it.

What a signup records

  • the email address or phone number the visitor enters, and any other field the customer added to the form. Email addresses and phone numbers are encrypted in our database;
  • a consent record: how consent was given, the page it was given on, and when;
  • where the customer has enabled double opt-in, a confirmation token and the time the visitor confirmed.

What the embed script sends us

To choose which popup to show, the script sends us the site key, whether the screen is mobile-sized, and a random visitor id. When a popup is shown, closed or submitted, it also sends the page path (never the query string), the screen size and the random session and visitor ids. We add an approximate country from a network-level header supplied by Cloudflare.

Everything else used for targeting, such as the pages visited in this visit or whether the visitor already arrived from one of the customer's emails, is worked out in the visitor's own browser and is not sent to us.

Values stored in the visitor's browser

These are first-party values on the customer's own site. They are not used for advertising and are never read across other websites.

KeyStoragePurposeLifetime
bp_sessionsessionStorageA random id for this browsing sessionUntil the tab is closed
bp_visitorlocalStorageA random per-browser id that keeps A/B test variants stable across visits. Not set when the browser sends Global Privacy ControlUntil cleared by the visitor or the browser
bp:visitlocalStorageWhen the visitor was first seen, the times of this visit, up to 50 page paths and the visit's UTM source, used for audience targeting. Never sent to us. Not set when the browser sends Global Privacy ControlUntil cleared
bp:seen:*localStorageWhether a popup was closed or submitted, so it is not shown againUntil cleared
bp:su:email, bp:su:smslocalStorageWhen this browser last signed up, so subscribers are not asked twiceUntil cleared
bp:cd:*localStorageWhen a countdown offer started, so the timer stays honest across pagesUntil cleared
bp:cartsessionStorageThe cart item count, for cart-based triggers on ShopifyUntil the tab is closed

To recognise visitors who are already subscribers, the script can also read cookies the customer's email platform sets on their site (such as Klaviyo, Omnisend or Mailchimp). It does not change those cookies or send them to us.

What we deliberately do not do. We do not store visitors' IP addresses in our database. An IP is used only in memory, for a few seconds, to rate-limit abusive requests, and is then discarded. Campaign reports are built from daily counts of impressions, closes and signups per popup. To debug and improve delivery we also keep a raw event log (event type, page path, screen size, country and the random session and visitor ids) for 90 days; it contains no email address, phone number or IP address. We do not track visitors across other websites, do not build advertising audiences, and do not sell or share this data. Known search-engine and AI crawlers are filtered out and never shown a popup.

Pixels and code the customer turns on

If a customer turns on third-party pixels or custom signup code in their settings, then when a visitor signs up, the popup passes the signup event, and where the pixel supports it the email address or phone number, to those tags already running on the customer's page (for example Meta or Klaviyo). This happens in the visitor's browser at the customer's instruction, and those providers process the data under their agreement with the customer.

Privacy signals

Our script honours Global Privacy Control. When a browser sends it, the script stores no lasting identifier or visit history, sends no analytics events, and does not fire the customer's pixels on signup. We do not act on the older Do Not Track signal, which is deprecated. Because the customer is the controller, it is their responsibility to configure campaigns and their cookie banner in line with the law that applies to them.

8. Cookies on betterpopup.com

On our own website we use essential cookies for sign-in and security, a bp_region cookie that records only whether consent is legally required where you are, and, with your consent, PostHog analytics cookies.

Where consent is required we ask before setting anything non-essential, and nothing analytics-related runs until you choose. You can change or withdraw your choice at any time from the Cookie preferences link in the footer. Every cookie and storage key is listed in our Cookie Policy.

9. How long we keep data

DataRetention
Account and profile dataWhile your account is active. Erased within 30 days of closure, plus up to 30 further days in encrypted backups
Campaigns, popups and templates you createdUntil you delete them or close your account
Subscriber data captured through your popupsFor as long as you instruct. Erased within 30 days of account closure, or sooner on your instruction
Shopify store data after uninstallDeleted 48 hours after uninstall, when Shopify sends its shop deletion request
Campaign analytics (daily impression, close and signup counts)While the account is active; aggregate and not linked to an individual
Popup event log (random ids, page path, country)90 days
Log of who viewed or exported subscriber dataAbout 13 months (400 days)
Shopify compliance request log24 months, as a durable audit record that a data request was received and fulfilled
Support conversations24 months after our last contact
Invoices and accounting records10 years, as required by Romanian law
Cookie-consent choiceStored in your browser until you change it or clear it
Database backupsTaken hourly, encrypted, kept 30 days
Server and security logsUp to 6 months
Rate-limiting dataHeld in memory only, seconds to minutes; never written to disk

10. International transfers

We are established in Romania, and some of our providers and infrastructure, including our database servers and backups, are located in the United States. Where personal data is transferred outside the EU/EEA we rely on the European Commission's Standard Contractual Clauses and, where the provider is certified, the EU-US Data Privacy Framework, together with additional technical measures such as encryption in transit and at rest.

You can request a copy of the safeguards that apply to a specific transfer by writing to [email protected].

11. How we protect data

We use encryption in transit (TLS) and at rest, encrypt the email addresses and phone numbers your popups collect, encrypt the access tokens for the integrations you connect, apply least-privilege database roles so the public capture endpoint can only insert records, log every view and export of subscriber data, restrict administrative access to the people who need it, and rate-limit public endpoints against abuse. Payment card data never reaches our systems.

No system is completely secure, but we maintain appropriate technical and organisational measures, review them regularly, and will notify affected customers and the competent authority where a breach requires it under Art. 33 and 34 GDPR. The measures are described in more detail in our DPA.

12. Your rights

If we are the controller of your data, you can ask us to: give you access to it (Art. 15); correct it (Art. 16); erase it (Art. 17); restrict or object to how we use it (Art. 18 and 21); provide it in a portable, machine-readable format (Art. 20); and withdraw consent at any time without affecting processing that already happened (Art. 7(3)).

Email [email protected], or delete your account yourself from your settings. We respond within one month, and will tell you if we need longer because a request is complex.

If you think we have handled your data badly, please tell us first so we can put it right. You also have the right to complain to a supervisory authority: for us that is the Romanian National Supervisory Authority for Personal Data Processing (ANSPDCP), or you can go to the authority where you live or work.

13. US state privacy rights

If you live in California, Colorado, Connecticut, Virginia or another US state with comprehensive privacy legislation, you may have rights to know what personal information we collect, to access, correct or delete it, to opt out of its sale or sharing, and not to be discriminated against for exercising those rights.

We do not sell personal information and do not share it for cross-context behavioural advertising, as those terms are defined under the CCPA/CPRA and similar laws. To exercise a right, email [email protected]. You may use an authorised agent, and we will verify the request before acting on it.

For data we process on behalf of a customer we act as a service provider or processor, and we will forward your request to the relevant business.

14. Shopify merchants

If you install BetterPopup from the Shopify App Store, we receive your store domain, store name and store contact email, and an access token scoped to what the app needs: creating the discount codes your popups show in your store's Discounts, and saving each signup to your store's Customers with the marketing consent the visitor gave. We support Shopify's mandatory privacy webhooks (customer data requests, customer redaction and shop redaction) and keep an audit record of each request and when it was fulfilled. Uninstalling the app stops the popups, and 48 hours later, when Shopify sends its shop deletion request, we delete your store's data, including your subscriber list. Export it first if you want to keep it.

15. Changes to this policy

We may update this policy as the service and the law develop. If we make material changes we will post a prominent notice on this page and update the date at the top, or contact account owners directly where required.

16. Contact

Digitonica SRL
Str. Dr. Victor Gomoiu
Craiova, Dolj, Romania
CUI 46142569 · Trade Register J18/1195/2022
Privacy: [email protected]
Phone: +40 756 029 780