Owner: g04t
Email: freepartylab@gmail.com
Website: freepartylab.com
This privacy policy is governed by Regulation (EU) 2016/679 GDPR and Spanish data protection law.
Short answer: Practically none — with one narrow exception for attacks (section 2b).
Free Party Lab does NOT collect, store, or process personal data of the people who use it. The one exception is requests that are plainly attacks on the site, described in section 2b. Specifically:
To know which tools are used and from where, the server counts page views. For each page it serves it adds one to five daily totals: the page, the country the connecting IP address resolves to, the domain of the site that linked here (if any), the browser's preferred language, and the day. Nothing in the page does this — there is no script and no pixel — and nothing is stored about you when you view a page: no IP address, no user agent, no cookie, no identifier.
Unique visitors are estimated, not tracked. The IP address and browser signature are run through a one-way hash together with a secret that is generated fresh every day (UTC) and discarded after it, and the result is fed to a probabilistic counter that keeps a count, not the values. The same person is one visitor for a day and a stranger again the next; nothing links two days together. The IP address exists in memory for the length of that single operation.
The country lookup uses a database held on our own server (IP Geolocation by DB-IP, CC BY 4.0); no address is sent anywhere. Daily totals are kept for 13 months and then expire.
Automated scanners constantly ask every website for files that are not there — /.env, /.git/config, /wp-login.php, ../../etc/passwd — and sometimes send methods a static site does not speak. For requests that match such patterns, and only those, the server records the IP address, the user agent, the requested path and the day, and adds the request to daily totals by type and by country. An ordinary visit, a mistyped address or an old bookmark matches none of these patterns and leaves no trace.
The purpose is defence and improvement of the service: seeing what is being attacked, from where, and whether to block it. The legal basis is our legitimate interest in the security of the site (GDPR Art. 6(1)(f)). The address, user agent and path are deleted automatically after 30 days; the totals by type and country, which identify no one, are kept for 13 months. This log is read only by the site's operator, is stored on our own server and its Redis store, and is never shared, sold or used to identify or profile visitors.
We use browser localStorage only for:
freepartylab-lang.This data:
All audio processing occurs 100% in your browser using:
No intermediate servers, proxies, or data transmission. Your file enters and leaves your browser, period.
Since we do not process personal data, GDPR does not apply in our case. This is an advantage for you:
Hosting servers: The site is hosted on Heroku. Heroku may log standard HTTP access (IP, browser, timestamp) for security and maintenance reasons. We do not share user data.
Contact form (Formspree): The contact form is delivered by Formspree. If — and only if — you choose to submit it, the name, email address and message you type are sent to Formspree, which forwards them to us by email. Nothing is sent while you simply read the page, and the tools themselves never use this route. Formspree processes that submission under its own privacy policy.
External resources: None. FFmpeg, fft.js and both brand fonts are served from this site itself, and the Content-Security-Policy permits no external script, style or font host. No CDN receives a request, so no third party sees your IP address while you use the tools.
No data sharing: We do not sell, rent, or share personal data with advertising, analytics, or third-party partners. The visit counts in section 2a are computed on our own server and never leave it.
Under GDPR, you have the right to:
To exercise these rights or make inquiries, contact freepartylab@gmail.com.
If we implement analytics, advertising, or other data processing in the future, we will update this policy and communicate transparently. Users will be notified before any material changes.
Last updated: November 9, 2026