Privacy
Last updated: 3 May 2026 · nonoisemetrics.com
This document contains two parts: (1) the Legal Notice (Mentions Légales) required under French law (LCEN Art. 6), and (2) the Privacy Policy required under GDPR and the French loi Informatique et Libertés. Both govern your use of nonoisemetrics.com and the NoNoiseMetrics SaaS platform. This service is intended exclusively for professionals and legal entities acting in a commercial capacity (B2B). French consumer protection rules do not apply.
PART I — LEGAL NOTICE
Mentions Légales — Article 6 LCEN (Loi pour la Confiance dans l'Économie Numérique)
1. Publisher (Éditeur du site)
NoNoiseMetrics
Exploité en tant que micro-entreprise sous le droit français
SIREN: 842 134 223
Email: contact@nonoisemetrics.com
Website: nonoisemetrics.com
Établissement: France (Strasbourg)
Activity: Edition and operation of a SaaS analytics platform for professionals.
VAT: As a micro-entreprise below the VAT threshold, NoNoiseMetrics is not subject to VAT registration (franchise en base de TVA — Article 293B CGI). A VAT number will be indicated here if and when registration becomes applicable.
2. Hosting Provider (Hébergeur)
Hostinger EU (UAB Hostinger International)
Registered address: Jolantos g. 2, Kaunas LT-44329, Lithuania — European Union
Website: hostinger.com — Contact: gdpr@hostinger.com
The NoNoiseMetrics application and associated data are hosted exclusively within the European Union.
3. Publication Director (Directeur de la publication)
The publication director is the individual operator of NoNoiseMetrics (micro-entreprise, SIREN 842 134 223). Contact: contact@nonoisemetrics.com
4. Intellectual Property
The NoNoiseMetrics brand, logo, platform code, interface design, and all content produced by the operator (excluding Customer data) are protected by intellectual property law. Any reproduction, distribution, or use without prior written authorisation is prohibited.
Third-party trademarks (Stripe, Supabase, PostHog, Brevo, Hostinger) are the property of their respective owners and are referenced solely for descriptive purposes.
5. Applicable Law and Jurisdiction
This website and its content are governed by French law.
In the event of a dispute relating to the use of this website or the NoNoiseMetrics service, and in the absence of an amicable resolution, the dispute shall be submitted to the exclusive jurisdiction of the:
Tribunal de Commerce de Strasbourg
Palais de Justice, 3 place du Marché Vert
67000 Strasbourg, France
As a B2B service (professionals and legal entities only), disputes fall under commercial law jurisdiction.
6. Mediation (for EU Consumers — not applicable)
NoNoiseMetrics is a B2B service. The EU Online Dispute Resolution platform (ec.europa.eu/consumers/odr) and consumer mediation requirements do not apply. If you are a professional Customer with a dispute, please refer to Section 5 above and the dispute resolution provisions in the Terms of Service.
7. Contact
For any questions relating to this Legal Notice: contact@nonoisemetrics.com
PART II — PRIVACY POLICY
Politique de Confidentialité — RGPD / Loi Informatique et Libertés
This Privacy Policy applies to the NoNoiseMetrics SaaS platform and website. It describes how we collect, use, store, and protect personal data in accordance with Regulation (EU) 2016/679 (GDPR) and French data protection law. This service is B2B: intended for professionals and legal entities acting in a commercial capacity. If you are an end-user of a company using NoNoiseMetrics, please contact that company directly regarding their data practices.
1. Data Controller
NoNoiseMetrics
Exploité en tant que micro-entreprise sous le droit français
SIREN: 842 134 223
Email: contact@nonoisemetrics.com
Website: nonoisemetrics.com — Établissement: France (Strasbourg)
For all data protection enquiries: contact@nonoisemetrics.com
As a micro-entreprise, NoNoiseMetrics is not required to appoint a formal Data Protection Officer (DPO) under Article 37 GDPR. All data protection requests are handled personally by the operator within 30 days.
2. Our Role: Two Distinct Capacities
2.1 As Data Controller — for our Customers
When you create an account and use NoNoiseMetrics, we act as the data controller for the personal data you provide directly (your name, email address, billing information). This Privacy Policy primarily governs this relationship.
2.2 As Data Processor — for data fetched via Stripe API
When you connect your Stripe account, we make live API calls to Stripe on your behalf. You can connect via one of two authorisation modes:
- OAuth (Stripe Connect): you authorise NoNoiseMetrics through Stripe's hosted authorisation page. Stripe Connect issues a
read_writeaccess token by design — Stripe Connect does not currently offer a read-only OAuth scope. Our application code is hard-coded to call only GET endpoints on connected accounts (/v1/customers,/v1/subscriptions,/v1/invoices,/v1/charges,/v1/refunds,/v1/prices). We never call POST, PUT, PATCH, or DELETE against your Stripe account. - Restricted API key: you generate a restricted, read-only key in your Stripe Dashboard and paste it into NoNoiseMetrics. The key is encrypted at rest.
Any billing data retrieved (which may include personal data of your own customers, such as email addresses or names stored in Stripe) is processed by us as a data processor on your behalf.
Crucially: raw Stripe customer, subscription, invoice, and charge records are not retained between sessions. They are fetched on demand to render your dashboard and cleared from memory when your session expires (30 minutes of inactivity). Aggregate Metrics (e.g. daily MRR totals — figures only, no individual customer records) are persisted to compute trends and forecasts; these can be deleted at any time by disconnecting the integration.
This architecture — read-only data flow, no retention of raw customer records, vault-encrypted credentials — significantly reduces our data footprint and your exposure as data controller.
3. Personal Data We Collect
3.1 Data you provide directly
- Account data: your email address, name, and organisation name provided during sign-up.
- Billing data: payment method details processed by Stripe (we never store full card numbers or CVVs).
- Communications: any messages you send to contact@nonoisemetrics.com.
3.2 Data fetched live from Stripe (session-scoped, not stored)
When you are actively logged in and have connected a Stripe account, we make real-time API calls using your restricted read-only key. The following categories of data are retrieved and held in session memory:
- Subscription data: plan names, pricing, billing intervals, subscription statuses, trial dates.
- Customer records: Stripe customer IDs, email addresses, names, and countries as stored in your Stripe account.
- Invoice and charge data: invoice amounts, statuses, payment dates, refund amounts.
- Product and price data: product names, price configurations.
This data is used exclusively to compute and display your Metrics during your session. It is not written to persistent storage. When your session expires or you log out, this data is cleared from memory.
3.3 Usage and analytics data (PostHog & Google Analytics)
We collect data about how you interact with the NoNoiseMetrics platform and blog via two analytics tools, both loaded only after you give consent via our cookie banner (Tarteaucitron):
- PostHog (EU): product analytics hosted on an EU endpoint (Frankfurt). Tracks feature usage, funnel conversion, and session events on the app. No cross-site tracking.
- Google Analytics 4 (via Google Tag Manager): audience analytics on the marketing site and blog (page views, traffic sources, geographic breakdown). Data is processed by Google Ireland Ltd and may be transferred to Google servers in the USA under Standard Contractual Clauses.
Neither tool fires before you consent. You can withdraw consent at any time using the cookie icon at the bottom-right of any page.
3.4 Technical data
IP address, browser type and version, operating system, device type. HTTP request logs, retained for 12 months for security purposes.
4. How We Use Your Data
| Purpose | Legal basis | Retention |
|---|---|---|
| Provide analytics dashboard | 6(1)(b) — Contract | Session only for Stripe data; account data for duration of account |
| Process subscription payments | 6(1)(b) — Contract | 10 years (French tax law) |
| Send transactional emails | 6(1)(b) — Contract | Duration of account |
| Product analytics (PostHog) | 6(1)(a) — Consent | 12 months |
| Audience analytics (Google Analytics 4) | 6(1)(a) — Consent | 14 months (Google default) |
| Security monitoring | 6(1)(f) — Legitimate interest | 12 months |
| Legal & tax obligations | 6(1)(c) — Legal obligation | 10 years |
| Anonymised benchmarks | 6(1)(f) — Legitimate interest | Indefinite (anonymised) |
We do not sell personal data to any third party. We do not use Stripe billing data or your customers' data to train AI or machine learning models.
5. Legitimate Interest Assessment
Where we rely on legitimate interest (Article 6(1)(f)), we have assessed that our interests do not override your rights:
- Security monitoring: retention of IP addresses and HTTP logs for 12 months is proportionate to the need to protect the platform from abuse and unauthorised access, consistent with ANSSI recommendations.
Analytics (PostHog and Google Analytics 4) are processed on the basis of consent (Art. 6(1)(a)), not legitimate interest. Neither tool loads until you accept via the cookie banner.
6. Third-Party Sub-Processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Supabase | Database & authentication | EU — Frankfurt |
| Stripe | Payment processing & Stripe Connect OAuth | EU / USA (SCCs) |
| PostHog (EU) | Product analytics (app) | EU — Frankfurt |
| Google Ireland Ltd (GA4 via GTM) | Audience analytics (site & blog) — consent only | EU / USA (SCCs + DPF) |
| Loops | Transactional & lifecycle emails | USA (SCCs + DPF) |
| Hostinger EU | Web hosting | EU — Lithuania |
Stripe data (your customers' billing records) is fetched live per session and is not transferred to Supabase or any other sub-processor. The only data stored in Supabase is your account data and computed Metrics (aggregate figures such as MRR totals — not raw customer records).
7. Stripe Data Architecture — Read-Only, No Persistent Customer Records
When you log in to NoNoiseMetrics and view your dashboard, or when our scheduled sync runs:
- An API call is made to Stripe — under OAuth using the access token we hold in our vault, or under the API-key flow using your restricted read-only key.
- The resulting data (subscriptions, customers, invoices, charges, refunds, products) is loaded into the runtime to compute your Metrics.
- Raw customer, subscription, invoice, and charge records are not retained between sessions. They are cleared once Metrics computation completes (or at session expiry, 30 minutes of inactivity).
- Only aggregate Metrics (e.g. "MRR was X on date Y", "active subscriptions = N") are written to our database.
What IS stored in our database:
- Your account data (email, hashed password, organisation, plan).
- Connection metadata (provider type, authorisation mode, label, project assignment).
- Under OAuth: the Stripe Connect access token and refresh token, stored in the Supabase vault (encrypted at rest, accessed only via SECURITY DEFINER RPCs from our edge functions). Plain-text tokens never appear in our database tables.
- Under the API-key flow: your restricted read-only Stripe API key (encrypted at rest with AES-256).
- Aggregate Metrics snapshots — daily figures only, not raw customer records.
What is NOT stored: your Stripe customers' email addresses, names, or personal details; raw invoice or charge records tied to individual customers; any personal data of your end-users beyond what is needed for session display.
Disconnect = deleted. When you disconnect a Stripe integration, we immediately delete the associated OAuth tokens (or API key) and the Metrics snapshots tied to that connection. We also handle Stripe's account.application.deauthorized webhook: if you revoke our access from your Stripe Dashboard, the associated tokens and connection record are deleted automatically without further action on your part.
This architecture means that if our database were ever compromised, the attacker would not have access to your customers' personal data — only your account credentials and aggregate Metrics.
8. Cookies and Tracking Technologies
8.1 Cookies we use
| Cookie | Purpose | Duration |
|---|---|---|
| Supabase session token | Authentication — keeps you logged in. Strictly necessary. | Session / until logout |
| tarteaucitron | Stores your cookie consent choices. Strictly necessary. | 12 months |
| PostHog (ph_*, localStorage) | Product analytics — session continuity and funnel tracking. First-party, EU-hosted. Consent required. | 12 months |
| Google Analytics 4 (_ga, _ga_*) | Audience analytics — page views, traffic sources. Loaded via GTM. Consent required. | 14 months |
8.2 No advertising or retargeting
We do not use advertising cookies, retargeting pixels, or Facebook Pixel. We do not participate in interest-based advertising. Google Analytics 4 is used solely for audience measurement (page views, traffic sources) and is never used for ad targeting.
8.3 Consent and opt-out
When you first visit, a consent banner (powered by Tarteaucitron) appears. Strictly necessary cookies (Supabase session, Tarteaucitron preference) load without consent. Analytics cookies (PostHog, GA4) only load after you click Accept.
You can change or withdraw your consent at any time by clicking the cookie icon at the bottom-right of any page. You can also opt out of Google Analytics across all sites at tools.google.com/dlpage/gaoptout.
9. Your Rights Under GDPR
If you are based in the EU/EEA, you have the following rights regarding the personal data we hold about you as our Customer (your account data):
- Right of access (Art. 15): request a copy of your personal data.
- Right to rectification (Art. 16): request correction of inaccurate data.
- Right to erasure (Art. 17): request deletion, subject to legal retention obligations.
- Right to data portability (Art. 20): receive your account data in a machine-readable format.
- Right to object (Art. 21): object to processing based on legitimate interest (e.g., PostHog tracking).
- Right to restriction (Art. 18): request restriction of processing in certain circumstances.
- Right to lodge a complaint: contact the CNIL (cnil.fr) or the supervisory authority in your country of residence.
To exercise your rights: contact@nonoisemetrics.com. We respond within 30 days.
10. Data Retention
| Data category | Retention period | Basis |
|---|---|---|
| Account data (name, email, org) | Duration of account + 30 days post-closure | Contract; then erasure |
| Stripe data (customer records, invoices) | Session only — cleared on logout. NOT stored persistently. | Not retained; session-scoped |
| Aggregate Metrics snapshots | Duration of account + 30 days post-closure | Contract performance |
| Stripe API key (encrypted) | Duration of account + 30 days post-closure | Contract |
| Billing and payment records | 10 years from transaction date | French tax law (CGI Art. 54) |
| PostHog analytics data | 12 months from collection | Legitimate interest |
| Security logs (IP, HTTP) | 12 months | Legitimate interest |
| Anonymised aggregate data | Indefinite — not personal data | Not personal data |
On account closure, all personal data is permanently deleted within 30 days (except billing records retained under tax law). You will receive email confirmation when deletion is complete.
11. Security Measures
- Encryption in transit: all data transmitted between your browser and our servers uses TLS 1.2+.
- Encryption at rest: Stripe API keys are encrypted with AES-256. Stripe Connect OAuth access and refresh tokens are stored in the Supabase vault (encrypted at rest, accessed only via SECURITY DEFINER RPCs from our edge functions). Account data is encrypted at rest by Supabase.
- Row-Level Security (RLS): Supabase enforces row-level security policies — each Customer can only access their own data.
- No persistent raw Stripe records: customer, subscription, invoice, and charge records are not retained between sessions; only aggregate Metrics are stored.
- Access controls: production system access is restricted to the operator. No third party has standing access to the production database.
- Read-only data flow: under the API-key flow, we ask you to issue a restricted, read-only Stripe key. Under Stripe Connect OAuth, Stripe issues a
read_writetoken by design — Stripe Connect does not currently offer a read-only OAuth scope. Our application code is restricted to GET endpoints (/v1/customers,/v1/subscriptions,/v1/invoices,/v1/charges,/v1/refunds,/v1/prices); we never call POST, PUT, PATCH, or DELETE against your Stripe account, and we never initiate money movement. - Deauthorisation: we listen for Stripe's
account.application.deauthorizedConnect webhook and immediately delete the corresponding tokens and connection record when you revoke access from your Stripe Dashboard.
In the event of a personal data breach likely to result in risk to individuals, we will notify the CNIL within 72 hours (Art. 33 GDPR) and affected Customers without undue delay.
12. International Data Transfers
Our primary infrastructure (Supabase, Hostinger) is hosted within the European Union. Some sub-processors (notably Stripe) may transfer data to the United States. Where such transfers occur, appropriate safeguards are in place: Standard Contractual Clauses (SCCs) and, where applicable, the EU-US Data Privacy Framework.
Stripe session data fetched via the API is processed transiently and is not transferred to any of our other sub-processors.
13. Children's Data
NoNoiseMetrics is a B2B service for professionals. We do not knowingly collect data from individuals under 18. If you believe we have inadvertently done so, contact contact@nonoisemetrics.com and we will delete it promptly.
14. Changes to This Policy
We may update this Privacy Policy from time to time. For material changes, we will notify you by email and/or in-app notice at least 14 days before the changes take effect. Continued use after the effective date constitutes acceptance. Previous versions are available on request.
15. Contact and Supervisory Authority
15.1 Contact
NoNoiseMetrics
Exploité en tant que micro-entreprise sous le droit français
SIREN: 842 134 223
Email: contact@nonoisemetrics.com
Website: nonoisemetrics.com — Établissement: France (Strasbourg)
15.2 Supervisory Authority
You have the right to lodge a complaint with the CNIL:
Commission Nationale de l'Informatique et des Libertés (CNIL)
Website: cnil.fr — 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France
You may also contact the supervisory authority in your country of residence within the EU/EEA.