--- title: "PeppolStatus Privacy" description: "The PeppolStatus privacy policy: server logs and IPs for security and rate limiting, PostHog analytics, Clerk accounts on the app console, API-key usage records, Stripe billing, hosting on Cloudflare. Operated by E-Invoice BV." canonical: "https://peppolstatus.com/privacy/" last-updated: 2026-08-17 --- # Privacy at PeppolStatus. PeppolStatus is a mostly read-only site for measuring the Peppol network. It collects very little about you. This is the privacy policy for peppolstatus.com and its subdomains: it says plainly what we process, why, with whose help, and what your rights are. Last updated 2026-08-17. ## Who is responsible PeppolStatus is operated by **E-Invoice BV** (trading as e-invoice.be), the data controller: E-Invoice BV Brusselsesteenweg 119/A, 1980 Zemst, Belgium Enterprise number (KBO) 1018.265.814 ยท VAT BE 1018.265.814 RPR Brussels, Dutch-language division For any privacy question or request, email [privacy@e-invoice.be](mailto:privacy@e-invoice.be) or write to the address above. ## What this site processes The public website, dashboard, and docs on peppolstatus.com are read-only and do not ask you to sign in. Across peppolstatus.com and its subdomains, we process: - **Server logs and IP addresses.** Requests to the site and to the API at [api.peppolstatus.com](https://api.peppolstatus.com) are logged. IP addresses are processed to keep the service secure and to enforce per-IP rate limits on the API. The lawful basis is our legitimate interest in operating and protecting the service. - **Account data on the app console.** The app console at [app.peppolstatus.com](https://app.peppolstatus.com) uses [Clerk](https://clerk.com) for authentication. If you create an account, Clerk processes your sign-in credentials and profile on our behalf so you can log in and manage access. - **API-key usage records.** When you use an API key, we record its usage to apply your plan's rate limits and quotas and to protect the API from abuse. Usage records are tied to the key and the account that owns it. - **Product analytics.** The public website uses [PostHog](https://posthog.com) (EU region, served through our own domain) to understand how visitors use the site. We look at pages viewed, referrers, and approximate location derived from your IP. This sets cookies; see [the cookies section](https://peppolstatus.com/privacy/#cookies) below. The API also reports errors to PostHog server-side; that reporting sets no cookies and contains no visitor profile. - **Advertising and conversion tracking.** We run ads on [LinkedIn](https://www.linkedin.com) and load LinkedIn's Insight Tag on the public website. It lets us measure which ads lead to visits and show ads to people who have visited before. The Insight Tag sets cookies through LinkedIn; see [the cookies section](https://peppolstatus.com/privacy/#cookies) below. LinkedIn processes this data under [its own privacy policy](https://www.linkedin.com/legal/privacy-policy). - **Billing data.** If you buy a paid plan, payment runs through [Stripe](https://stripe.com)'s hosted checkout. We receive your organisation's billing details (name, email, VAT number, plan); your card details go to Stripe, not to us. Plans agreed on invoice are billed by E-Invoice BV directly. We advertise on LinkedIn, as described above, but we do not sell or rent personal data to anyone. ## Cookies These are the cookies actually in use across peppolstatus.com and its subdomains: | Cookie | Set by | Where | Purpose | | --- | --- | --- | --- | | `ph_*` | PostHog (via our own domain) | public website | Analytics: recognises your browser across visits so we can count visitors and understand how the site is used. | | `li_*`, `bcookie`, `lidc`, `UserMatchHistory` | LinkedIn (Insight Tag) | public website | Advertising: measures LinkedIn ad conversions and lets us show ads to people who have visited the site. | | `__session`, `__client_uat` | Clerk | app console | Strictly necessary: keeps you signed in to your account. Set only when you use the console. | | various | Stripe | Stripe's checkout pages | Payment processing and fraud prevention on Stripe's own hosted pages, under [Stripe's privacy policy](https://stripe.com/privacy). | The site currently shows no cookie banner: the analytics and advertising cookies are set on your first visit. You can block or delete cookies in your browser at any time. The site keeps working without them. We plan to add a consent banner for the analytics and advertising cookies; when it ships, they will only be set after you agree. ## The Peppol data we display The network data shown on PeppolStatus (participants, access points, SMPs, certificates, and change events) is derived from **public Peppol infrastructure** (the SML and SMP directory) and from **official business registries**. It is public-register information about organisations on the network, not data that individuals submit to us. Where the Peppol Directory or a business registry exposes contact details of natural persons, we suppress those fields rather than republish them, and we honour the non-diffusion status that registries attach to individual records. If a record about your organisation looks wrong, or you believe we display personal data we should not, email [privacy@e-invoice.be](mailto:privacy@e-invoice.be) and we will look into it. ## Hosting and processors We rely on a small set of processors, each handling data on our behalf for the purpose described: - **[Cloudflare](https://www.cloudflare.com)**. Hosts and serves the site, API, and databases, and processes request data (including IP addresses) as our infrastructure provider. - **[Clerk](https://clerk.com)**. Handles authentication and account data for the app console. - **[PostHog](https://posthog.com)**. Product analytics and API error reporting, hosted in PostHog's EU region and served through our own domain. - **[Stripe](https://stripe.com)**. Payment processing for paid plans. For fraud prevention on its checkout pages, Stripe also acts as a controller in its own right under [its own privacy policy](https://stripe.com/privacy). Some of these providers process data outside the European Economic Area. Where they do, transfers rest on an adequacy decision or the European Commission's Standard Contractual Clauses. ## How long we keep data We keep personal data no longer than the purpose requires. Server logs and request records are kept for a limited period for security, rate limiting, and abuse investigation, then deleted or aggregated. Account data lives for as long as your account exists; when you delete your account, we delete it except where invoicing and accounting law requires us to keep billing records longer. API-key usage records are kept while the key's account exists, for quota enforcement and billing. ## Your rights Under the GDPR you have the right to access, rectify, or erase your personal data, to restrict or object to processing, and to data portability. This applies whether you hold a console account, use an API key, or simply visit the site. To exercise any of these, email [privacy@e-invoice.be](mailto:privacy@e-invoice.be) or write to E-Invoice BV, Brusselsesteenweg 119/A, 1980 Zemst, Belgium. You also have the right to lodge a complaint with the [Belgian Data Protection Authority](https://www.dataprotectionauthority.be). ## Changes to this policy When our data practices change (a new processor, a new purpose, a consent banner) we update this page and its "last updated" date. For material changes affecting account holders, we also notify you by email or a notice on the service. - [privacy@e-invoice.be](mailto:privacy@e-invoice.be) - [Terms of Service](https://peppolstatus.com/terms/) - [Data licensing terms](https://peppolstatus.com/data-licensing/) - [Contact](https://peppolstatus.com/contact/)