Privacy & GDPR

What Launch Approved stores, where, for how long, and what it sends elsewhere: nothing by default, clear choices for you, and testers who are told.

Your testers’ data stays with you

A test handles personal data: names, e-mails, devices, screenshots, sometimes a video. With Launch Approved, all of it stays in your WordPress, on the server you chose — not at a testing or recording platform.

  • You decide what is recorded, campaign by campaign, and how long it is kept.
  • Your testers are told what is measured before they start, and choose whether they are filmed.
  • Nothing leaves your server by default: the few options that call outside are off and explained.

Launch Approved gives you the tools; the responsibility for your processing and your privacy policy remains yours. This page explains what is stored, what is shared, how long it is kept and what your testers can ask.

On this page

What Launch Approved stores

Data Why Kept, once retention is on
Tester’s name, e-mail, job To invite them and credit their test. 365 days by default, then anonymised (« T1 »).
Device (system, browser, screen, languages, time zone) To reproduce a finding on the same setup. 90 days by default, then erased.
Answers, times, feelings, remarks The results of the test. With the campaign.
Screenshots and findings The proof of each problem. With the campaign, or the time you set.
Positions of clicks, scrolling and mouse The heatmaps. Never what is typed. With the campaign.
Video of the test Only with the tester’s consent. The time you set for screenshots.
Signatures and signed copies The proof of the acceptance. 5 years by default, never touched before.

Retention is off by default: nothing is erased until you switch it on in Launch Approved > Settings > Data kept, with a confirmation. The durations above are the defaults once it is on, and each one can be changed.

What is sent to other services

Nothing, by default. Launch Approved works without any external service: no analytics, no recording platform, and no font or script of its own loaded from another site. A few options can call outside, all off by default and explained where you switch them on:

  • Spam blacklists in the site health — the address of the mail server of the domain is asked to public lists. No personal data.
  • Update check with wordpress.org — the names of the plugins detected on a site are asked to wordpress.org. No personal data.
  • The licence — the address of your site and your key are checked with Remotely License to bring the updates. No data about your testers or clients.

The connector links your own sites only: the agency site and the client site talk to each other with a signed key, nothing goes through a third party.

The country of the testers, without their address

When a campaign checks where its testers are, the country is found with a table kept inside the plugin. The IP address is never stored and never sent anywhere: only the country is noted on the test.

Before starting, the tester reads in the start window what is measured to validate the test: the time spent, the answers, the clicks and mouse moves in the product, the time spent in other tabs. Nothing else is measured. The video is asked separately, and can be refused unless the campaign requires it. A contract, when you use one, is signed before the test and kept with its date.

How long data is kept

Once you switch retention on:

  • Traces — the device and the timing of each move are erased after 90 days by default.
  • Personal data — names and e-mails are anonymised after 365 days by default; the answers stay, without a name.
  • Screenshots and videos — kept with the results, or erased after the time you set.
  • Proof — a signed report and its evidence are kept 5 years by default, never erased before.

Each campaign can also be archived (a ZIP with its report, figures and screenshots), then its screenshots removed from the site.

Testers’ rights, with WordPress’s own tools

Launch Approved plugs into Tools > Export Personal Data and Tools > Erase Personal Data of WordPress. A tester is found by their e-mail address: the export gathers their campaigns, answers and findings; erasing anonymises them. The answers and findings stay, without their name: they are your team’s work and the proof that the tests were done.

From a campaign, you can also remove a tester: their answers are deleted, their findings stay without their name.

Security

  • Personal links — stored as fingerprints, tied to one computer once the test starts, refused after too many wrong tries.
  • Files — screenshots, videos and signatures are served by signed links that expire, never from a public folder.
  • Outside pages — an analysis copy or a deliverable is locked in a sandbox, imposed by the server too: its scripts can never reach your site.
  • Rights — admin, project managers, experts and clients each see only what their role allows; money is shown to the admin only.

Cookies and browser storage

Launch Approved sets one functional cookie for a tester: it ties the test to their computer. The cockpit keeps the progress of the test in the browser, so a reload does not lose it, and each person’s display choice (light or dark). No tracking cookie, no advertising cookie.

If you remove the plugin

Deactivating Launch Approved erases nothing. Deleting it erases the data only if you asked for it in the settings: by default, your campaigns and reports are kept.

Your privacy policy

Launch Approved gives you the tools; the responsibility for your processing remains yours. WordPress’s Privacy Policy Guide includes a suggested text for Launch Approved: what is collected from testers, why, for how long and who sees it. Adapt it to your campaigns, and mention the testers’ contract and the video when you use them.