Legal documents
Privacy policy
What data PostShip processes, why, on what basis, for how long, with which providers — and how to exercise your rights.
In force since 14 articles10 min read
This English translation is provided for convenience. The is the one that applies.
This policy describes how PostShip processes personal data, under Regulation (EU) 2016/679 of 27 April 2016 (the "GDPR") and French law no. 78-17 of 6 January 1978 on data processing, files and freedoms. Capitalised words have the meaning given in article 1 of the Terms.
Article 1. Controller
The controller is PostShip's publisher: Thibault Morretton EI, sole trader, 19 route de Lyon, 42400 Saint-Chamond, France, RCS Saint-Étienne 130 466 931. Full details are in the legal notice.
The publisher has not appointed a data protection officer, as it is not required to. For any question about your data: contact@postship.fr, subject "Personal data".
Article 2. Scope
This policy covers the postship.fr site, the application, the service's emails, the API and the command-line program. It concerns people who visit the site, create an account, subscribe to news or write to the publisher.
It does not cover the sites our customers monitor, nor the data PostShip processes on behalf of its customers: that is described in article 9, and falls under the privacy policy of the customer concerned.
Article 3. Data processed
Account
- Data
- email address, full name, username, company, phone if provided, automatically generated avatar (no photo is ever asked for), time zone, language
- Where it comes from
- you
Sign-in
- Data
- one-time codes, passkeys (the public part only), Google or GitHub identifier if you sign in with those services, IP address and time of sign-in
- Where it comes from
- you, your device, Google or GitHub
Billing
- Data
- billing name and address, plan, payment history and invoices, last four digits and expiry date of the card
- Where it comes from
- you, Stripe
Projects
- Data
- name, monitored addresses, journeys, alert rules, connected channels (Slack or Discord webhook addresses), tokens of the integrations you grant
- Where it comes from
- you, your integrations
Check results
- Data
- HTTP status, response time, HTML metadata (title, canonical tag, presence of structured data), timestamp; screenshots of monitored pages for visual regression and the social-card archive
- Where it comes from
- the service
API keys and terminal
- Data
- name of the key or machine, creation and last-use dates (the key itself is only kept as a hash)
- Where it comes from
- you
Server log
- Data
- IP address, date, page requested, referring page, declared browser
- Where it comes from
- your browser
Audience measurement
- Data
- page views and visits, with a cookie identifier and a truncated IP address, only if you accept it
- Where it comes from
- your browser, Google Analytics
Correspondence
- Data
- your messages, emails and support requests; for a quote request: first name, last name, company, email address, phone, website, volume to monitor and need
- Where it comes from
- you
News and digest
- Data
- email address, language, subscription and unsubscription dates
- Where it comes from
- you
Documentation feedback
- Data
- the page rated, yes or no, the language and, if you write one, a comment; no account, no cookie, no IP address attached to it
- Where it comes from
- you
Trial without an account
- Data
- the address of the site tried, and your IP address for as long as the anti-abuse counters
- Where it comes from
- you
Checks only cover the addresses you configure: PostShip does not crawl your site beyond them, and keeps no page body.
Article 4. Purposes and legal bases
| Purpose | Legal basis (article 6 of the GDPR) |
|---|---|
| Creating and managing your account, signing you in | performance of the contract |
| Providing the service: checks, alerts to the channels you connect, status pages, reports | performance of the contract |
| Invoicing, collecting payment, keeping accounts | performance of the contract and legal obligation (French Commercial and Tax Codes) |
| Sending the service's emails: sign-in codes, alerts, receipts, messages about your subscription | performance of the contract |
| Answering your requests and complaints | performance of the contract or pre-contractual steps |
| Improving the documentation from your feedback | the publisher's legitimate interest in making its documentation useful |
| Keeping the service secure, preventing fraud and abuse: server log, rate limits, protection against diverted requests | the publisher's legitimate interest in protecting the service and its users (recital 49 of the GDPR) |
| Sending the weekly digest and news | consent, withdrawn with the unsubscribe link in every email |
| Measuring the site's audience | consent, given and withdrawn in the banner or on the Cookies page |
| Establishing, exercising or defending legal claims | legitimate interest |
No data is used for advertising, commercial profiling or automated decisions producing a legal effect on you.
Article 5. Retention
| Data | Duration |
|---|---|
| Account and projects | as long as the account exists; deleted immediately and in full when it is deleted |
| Detail of each check | 14 days at most, then hourly totals |
| Check history | 7 days (Discover), 30 days (Pro), 90 days (Pro Plus), purged automatically every night |
| Screenshots | the length of the plan's history |
| In-app notifications | 30 days |
| Server log | 90 days at most |
| Anti-abuse counters (IP address) | 2 days at most |
| API keys of a terminal | until revoked, and at most 90 days after last use |
| Invoices and accounting records | 10 years, in accordance with article L. 123-22 of the French Commercial Code |
| Correspondence and complaints | the time needed to handle the request and follow it up, then the applicable limitation period |
| News and digest | until you unsubscribe; the unsubscribed address is kept, with no other data, so you are not written to again |
| Documentation feedback | 1 year |
| Cookie choice | 6 months |
| Database backups | one copy per night, the last seven kept; one copy per week, in separate storage with the same host, in the European Union |
Backups are used only to restore the service after an incident. Deleted data disappears from the daily backups after seven days; it is never extracted from a backup for any other use, and if a backup ever had to be restored, deletions made since its date would be applied again.
Article 6. Recipients and processors
Your data is accessible only to the publisher and, for what concerns them, to the following processors, bound by a contract compliant with article 28 of the GDPR. No data is sold to third parties.
Oracle Cloud Infrastructure
- Role
- hosting the site and application, running checks, backups
- Location
- Paris, European Union
Supabase
- Role
- database and authentication
- Location
- Paris, European Union
Stripe
- Role
- payment and invoicing
- Location
- Ireland and United States
Resend
- Role
- sending emails
- Location
- United States
Vercel
- Role
- standby hosting of the application; hosting of status pages published on a customer's domain, whose visitors it receives
- Location
- United States and European Union
Google (PageSpeed Insights)
- Role
- performance measurement of monitored pages: receives the page's address, nothing else
- Location
- United States
Google (Analytics)
- Role
- audience measurement, only if you accept it
- Location
- United States
Google, GitHub
- Role
- signing in with those services, if you choose to
- Location
- United States
Vercel, Netlify, Cloudflare, GitHub
- Role
- receiving deployments, if you connect your host or repository
- Location
- United States
Slack, Discord
- Role
- delivering alerts, if you connect one of these channels
- Location
- United States
The publisher may also disclose data to an authority that requests it under the law.
Article 7. Transfers outside the European Union
Some processors listed in article 6 may process data in the United States. These transfers are covered by the standard contractual clauses adopted by the European Commission and, where the provider participates, by the EU–US Data Privacy Framework, found adequate by the Commission's decision of 10 July 2023. A copy of the applicable safeguards can be obtained at contact@postship.fr.
Article 8. Server log and abuse prevention
Like any web server, PostShip's records each request: the IP address, the date, the page requested, the referring page and the browser, as announced by the User-Agent header. This log stays on our server, in Paris; no geolocation service is involved, and it is not linked to any account.
- Legal basis: legitimate interest (article 6.1.f of the GDPR) in keeping the service secure and preventing fraud and abuse, a purpose recital 49 of the GDPR expressly recognises. This data is used neither for advertising, nor profiling, nor resale.
- What is not collected: no browser fingerprint (canvas, WebGL, fonts), no cross-site identifier, no advertising tracker. These techniques would require your consent and serve no security need.
- Retention: the log is erased automatically after 90 days at most.
- Objection: you may object to this processing on grounds relating to your particular situation (article 21 of the GDPR), by writing to contact@postship.fr.
Rate limits — the number of sign-in codes, trials or terminal sign-in requests per hour — rely on counters per IP address, erased after two days.
Article 9. Data processed on behalf of our customers
For some features, PostShip processes data on behalf of a customer, who is the controller; PostShip is then their processor, under article 8.2 of the Terms.
- Status page subscribers: the email address of a person who subscribes to a status page's updates, confirmed by a link before anything is sent, and removed with the unsubscribe link in every message.
- Real-user monitoring: when a customer enables it on their site, their visitors' browsers send the page's address, speed measurements and, where applicable, the page's error messages. The IP address is only used for anti-abuse counters.
- Screenshots: monitored pages are captured as a visitor sees them; they may show data a customer publishes there.
If you are affected by any of this processing, first contact the customer whose site or status page you are visiting. The publisher forwards to the customer any request it receives about it.
Article 10. Cookies and trackers
PostShip sets a session cookie after sign-in, remembers your display choices and, only if you accept it, measures its audience. Each item — name, purpose, duration, legal basis — and the way to change your mind are on the Cookies page.
Article 11. Your rights
You have the following rights over your data:
Access
- What it lets you do
- know whether data about you is processed and get a copy
- GDPR article
- 15
Rectification
- What it lets you do
- have inaccurate data corrected or incomplete data completed
- GDPR article
- 16
Erasure
- What it lets you do
- have your data deleted, in the cases provided by law
- GDPR article
- 17
Restriction
- What it lets you do
- have the use of your data temporarily frozen
- GDPR article
- 18
Portability
- What it lets you do
- receive your data in a machine-readable format, or have it transmitted
- GDPR article
- 20
Objection
- What it lets you do
- object to processing based on legitimate interest
- GDPR article
- 21
Withdrawal of consent
- What it lets you do
- withdraw a consent at any time, without affecting what was done before
- GDPR article
- 7.3
Instructions after death
- What it lets you do
- decide what happens to your data after your death
- GDPR article
- article 85 of the French Data Protection Act
11.1Exercising them yourself
- Export your data: Account → Summary → Your data → Export.
- Correct your profile: Account → Profile.
- Delete your account: Account → Danger; deletion is immediate and irreversible.
- Unsubscribe from an optional email: the link at the bottom of every email.
11.2Exercising them in writing
For any other request, write to contact@postship.fr, subject "Personal data". You get an answer within one month, which may be extended by two months for a complex request; you are told if so. If there is reasonable doubt about your identity, additional information may be requested — never an identity document when your account's address is enough.
11.3Complaint
If you believe your rights are not respected, you can lodge a complaint with the French data protection authority (CNIL), at cnil.fr.
Article 12. Security
The publisher applies technical and organisational measures appropriate to the risk:
- encryption of every connection (HTTPS), including between the server and the database;
- access to data restricted within the database itself, account by account, by row-level security rules;
- passwordless sign-in, by one-time code or passkey, with two-factor authentication that a workspace owner can require;
- API keys kept as hashes, revocable at any time;
- protection against requests diverted to internal networks during checks;
- nightly backup, weekly copy off the machine, restore tests;
- administrative access reserved to the publisher, and logged.
If a data breach poses a risk to your rights, the publisher notifies the CNIL within 72 hours of becoming aware of it and, if the risk is high, tells you directly, in accordance with articles 33 and 34 of the GDPR.