Privacy
Last updated: 21 November 2026
The short version
- We read your Stripe customers, subscriptions and invoices, and write subscription values into HubSpot companies and contacts you already have.
- We can only read in Stripe. We never charge, refund or change anything there.
- We keep a small summary of each Stripe customer: their email, their name and the values we write. We do not keep invoices, payments or card details.
- We store the settings of your connections, encrypted sign-in tokens, and counts.
- We never create a contact or a company in HubSpot.
Who we are
MRR Sync is a product of Web IT Solutions. The legal notice names who runs it, with the address and registration number. Contact: support@webitsolutions.net.
For the Stripe customers and HubSpot records you connect, you are the controller and we are your processor (GDPR Article 28). Our data processing agreement is the section “How we process your data” in the terms. For your account details, we are the controller.
What we store
| What | Details | Why |
|---|---|---|
| Your account | HubSpot account (portal) ID, creation date, trial end date, subscription status and price band, and the Stripe customer and subscription IDs of our own billing | To run your account and to bill you |
| The people who sign in | For each person who signs in with HubSpot: their HubSpot user ID, their email address, the date of the first and the last sign-in | To sign you in and to know who can see the account |
| HubSpot connection | A refresh token (encrypted), the permissions you granted, the connection status, the date the properties were created and which of our fields were created | To read and write your records in the background |
| Stripe connection | Your Stripe account ID, whether it is live mode, test mode or a sandbox, an access token and a refresh token (both encrypted), your account’s default currency, the connection status and the progress of the first import | To read your Stripe data in the background |
| A summary of each Stripe customer | The customer’s Stripe ID, email address and name, and the values we write: status, plan name, MRR, ARR, currency, billing interval, next renewal, trial end, last payment date and amount, whether a payment failed, how many attempts failed, the amount overdue and since when, the date the customer first subscribed, when a subscription is set to end or ended, and the cancellation reason and comment your customer gave in Stripe, if any. Nothing else from the invoices, payments or subscriptions | To compute the values, and to add up a company that has several Stripe customers without reading Stripe again |
| Trial memory | The ID of your HubSpot account (portal), the date its free trial ends, and whether it installed before the HubSpot listing (the tester offer). We keep these even after you delete your account, for 2 years after the trial ends, then delete them | So one HubSpot account gets one free trial, not a new one each time an account is deleted and created again, and keeps the tester offer if it had one |
| A Stripe install waiting for your OK | When you install our app from Stripe’s side before you are signed in, we keep the Stripe account ID, whether it is live or test mode, and the access and refresh tokens (encrypted) for about 30 minutes, until you confirm or refuse it in the app. | So the install does not get lost while you sign in, and so nobody can attach a Stripe account to an account by following a link |
| Links | For each customer: the ID of the HubSpot company or contact it was matched to, and how (Stripe ID, email, the contact’s company or domain) | To know which record to update |
| What we last wrote | For each HubSpot record we wrote: its ID, a fingerprint of the values and the time | To write only when something changed |
| Unmatched customers | The Stripe ID of each customer we couldn’t match, the reason and a short detail | To show you the list in the app |
| Waiting list | The Stripe IDs of customers whose values must be refreshed | To update HubSpot after a change in Stripe |
| Stripe event IDs | The ID and type of each Stripe event we received, not its content. Deleted after 7 days | To ignore a message that arrives twice |
| Sync history | Start and end time, number of customers, writes and errors of each run, and an error message. Deleted after 90 days | To show you what happened and to fix problems |
| Visits to this site | For each page view of our public pages: the page address without anything after a “?”, the name of the website you came from, the tag of the link you used if it had one, phone, tablet or computer, your country, the buttons and links you click, which parts of the page you saw, whether you sent a form (not what you typed in it), how far down you scroll, how long the page is visible and how fast it showed. No IP address, no cookie, no id that follows you. Deleted after 13 months. See “What we measure on this site” below | To learn which pages and links help people |
| Sign-up steps | The steps you complete (sign in, Stripe connected, first import done, first values written, checkout opened, paid), with their dates, and the tag of the link you used to reach us if it had one. Deleted after 13 months, or with your account | To learn what helps people finish, and to fix what blocks them |
| Session cookie | One cookie that keeps you signed in: HttpOnly, Secure, SameSite=Lax, with an expiry | Needed for the app to work |
What we do not store
- Invoices, payments, line items and charges. We read them to compute the values, then keep only the values (see the summary above).
- Card numbers and bank details, from you or from your customers. We never see them. Our own billing is handled by Stripe.
- The content of your HubSpot records. We read a contact’s email and a company’s domain to find the match, then drop them. We keep only the record’s ID.
Our logs never contain tokens or customer data.
Permissions we ask for
- Stripe, read only: your Stripe account asks you to accept these permissions when you install our app. We never write to Stripe.
customer_read: Reads your customers (name and email) so each one can be matched to a HubSpot contact or company.subscription_read: Reads each customer's subscriptions to work out plan, status, MRR, ARR and renewal date.invoice_read: Reads open and paid invoices to show failed payments and the date of the last payment.product_read: Reads product names to show the plan name in HubSpot.plan_read: Reads prices, including tiered prices, to compute the monthly amount of each subscription.coupon_read: Reads coupons on subscriptions so MRR is shown after discounts.event_read: Lists and receives events about customers, subscriptions and invoices, so HubSpot is updated within minutes of a change.connected_account_read: Reads the default currency of your Stripe account.
- HubSpot: we read your companies and contacts to find the match, and we write our own property group and fields on the records we matched. We never create or delete a contact or a company.
Who else handles data
| Service | For | Where |
|---|---|---|
| Vercel | Hosting and scheduled jobs | Server functions run in the EU (Dublin, Ireland). Vercel’s network may serve the static pages from the location nearest to you. |
| Supabase | Database for the items in the table above | EU (Ireland) |
| Stripe | The source of your customers and subscriptions, through the Stripe App you install. Also our payments and the billing portal: Stripe is the merchant of record, it sells the subscription to you, collects tax and keeps your card details; we never see them. | EU, United States and India, under Stripe’s own privacy policy |
| HubSpot | The place we write the values to, and where we find your companies and contacts | Your HubSpot account |
Some of these companies are based outside the EU, mainly in the United States, and may access data from there. They protect these transfers as GDPR requires, with the EU standard contractual clauses or the EU-U.S. Data Privacy Framework, as their privacy policies say.
We do not sell your details or give them to other companies for their own use, and we do not use them for advertising. The services listed above handle them only to run MRR Sync. We do not use advertising or tracking cookies. What we measure on this site is described in the next section.
What we measure on this site
We count what happens on our public pages: the home page, the setup guide, the privacy page and the terms. We do it ourselves, so we can see which pages and links help people. We measure nothing inside the app.
- When you open a page: its address without anything after a “?”, the name of the website you came from (not the full address), the tag of the link you used if it had one (for example “?ref=reddit”), whether your screen is a phone, a tablet or a computer, and your country.
- While you are on it: which of our buttons and links you click, which parts of the page you saw, whether you sent a form (not what you typed in it), how far down the page you scroll, how long the page stays visible, and how fast the main part showed.
- No cookie, nothing stored in your browser, no IP address, no id that follows you between pages or visits. Each page view gets a random number that exists only in that page and is gone when you close it. We find your country from your IP address and keep only the two-letter country.
- Not sent when your browser asks not to be tracked (Global Privacy Control or Do Not Track).
- Kept 13 months, then deleted. It stays in our own database in the EU (Ireland), with the visits to our other websites. It is not shared with other companies.
When you sign in, the tag of the link you used is saved once on your account. The steps you complete are saved with their dates for 13 months. Deleting your account deletes them at once.
Why we may use your data
- To provide the service you signed up for (GDPR Article 6(1)(b), a contract): your account, sign-in, connections, the values we compute and write, billing status and support.
- Our legitimate interest (Article 6(1)(f)): the sync history, so we can fix problems. The same interest covers the measurement of our public pages, the tag of your sign-up link and the sign-up steps you completed: we want to know which pages, links and channels help people, so we can improve them.
- Our legitimate interest (Article 6(1)(f)) also covers the trial memory: giving each HubSpot account one free trial, not a new one each time an account is deleted and created again. It holds no name, email or customer data.
Your choices
- Disconnect Stripe in the app at any time. We delete the Stripe tokens, the summary of each customer, the links, the unmatched list and the waiting list. You can also uninstall our app in Stripe, and in HubSpot’s connected apps.
- Delete your account in the app, or email us, and we delete everything we hold about it. The one exception is the trial memory above: your HubSpot account ID, the date its trial ends and whether it had the tester offer, kept 2 years after the trial ends.
- If your trial ends unpaid or you cancel, syncing stops and we keep your account details, connections and customer summaries for 90 days, so you can come back without starting over. After 90 days we delete them.
- The properties and values we wrote stay in your HubSpot account, because they belong to it. You can delete the property group in HubSpot’s property settings.
- Email us to see, correct or delete your account data. We answer within 2 working days.
Your rights
- You can ask to see, correct, delete or receive a copy of your data, to limit how we use it, or object to a use based on our legitimate interest. Email support@webitsolutions.net.
- If you think we handle your data wrongly, you can complain to the French data protection authority, the CNIL (cnil.fr), or to the authority where you live.