DitLabs - Version 1.2 - Updated 2026-09-17
Privacy Notice
Integral notice under the Federal Law on Protection of Personal Data Held by Private Parties (LFPDPPP). We collect the minimum needed to run accounts and support. Free tools process files in your browser and do not send file bytes to us.
Some identity fields are pending owner confirmation and are marked in the text.
1. Controller
Controller: Angel Dittrich, acting as an individual (persona fisica). Domicile: [REQUIERE CONFIRMACION DEL PROPIETARIO]. Privacy and ARCO contact: hey.dittrich@gmail.com. Use this email for access, rectification, cancellation, opposition, consent withdrawal, and limitation requests.
2. Data we process
Identity and account: email, name, avatar, username, country, locale, use case, sex, date of birth, verification state, role, ban state. Sex and date of birth are used to confirm the minimum age of 16 and for aggregate statistics; sex can be answered as "prefer not to say" and neither field is shown to other users. Credentials: passwords are stored as hashes, never in clear text in our database; social login tokens are stored server side only if you use Google or GitHub login.
Service data: session token with IP and user agent for security, usage and activity limited to tool id and megabytes without file names or outputs, suggestions with a keyed hash of the sender IP instead of the raw address, email log with safe metadata and no tokens. No payment data is collected today because payments are not offered.
Local only: theme, language, sidebar order, recent tools, guest use counter, cookie choice. Stored in your browser, never sent to us.
3. Purposes
Primary (needed to provide the service): create and secure accounts, verify email, confirm you meet the minimum age of 16, enforce limits and bans, send transactional mail, handle suggestions and support, keep security logs.
Secondary: none today. Marketing, profiling for ads, or model training on your content would require a separate express opt-in and a new version of this notice. You can deny secondary purposes without losing the service when they exist.
4. Files and sensitive data
Every workshop tool runs entirely in your browser: files you process are not sent to our servers, including file bytes, original names, and outputs. Only the tool id and megabytes are logged for history when you are signed in.
Cloud processing is not currently offered, so no file leaves your browser today. If it is ever enabled, files would be transmitted only when you start that operation, without the original filename, and expire automatically. We do not request sensitive data and we keep no database of sensitive data. Avoid uploading IDs, health, or financial documents unless strictly needed, because even temporary processing counts as processing.
5. Suggestions inbox
The suggestion inbox is used to decide which tools to build. Each suggestion stores its title, body, icon, category, and internal status, plus your account if you are signed in or a keyed hash of the sender IP if you are not. Administrators are the only ones who can read suggestions, including the sender account or email when there is one.
Suggestions have no automatic expiry: they are kept until deleted. You can ask for the deletion of your suggestions by writing to the contact email. Please do not include passwords, IDs, sensitive data, or third party personal data in a suggestion; it is not needed to describe an idea.
6. Service providers
To run DitLabs we use the following technology services, each only with the data its function needs: Vercel (hosts the site), Railway Postgres (hosts the database), Resend (sends transactional email: address, subject, and message content), Cloudflare R2 (file storage, only if cloud processing is ever enabled), Stripe (payments, only if paid plans are ever offered, always on Stripe's own pages), and Google or GitHub (login, only if you choose it; they provide authentication under their own policies).
We do not sell data and we run no ad trackers.
7. ARCO, withdrawal, limitation
You can request Access, Rectification, Cancellation, and Opposition, withdraw consent, and limit use, free of charge, by writing to hey.dittrich@gmail.com with your account email, the right you invoke, and a description. We verify identity to avoid leaking data and we respond within the LFPDPPP timelines: a decision within twenty days and, when applicable, effectiveness within the following fifteen days.
You can also limit use at any time from the cookie preferences page or by deleting your account.
8. Retention and deletion
Deleting your account removes your profile, credentials, sessions, subscription record, usage, jobs, keys, and activity from the live database. Suggestions you sent and email records are kept without the link to your account. Deletion applies to the live database; copies that the hosting provider may keep as part of its own backups follow the provider's cycles and cannot be wiped instantly. Legal holds may delay deletion where the law requires retention.
9. Security and incidents
We apply administrative, technical, and physical safeguards proportionate to the service: credential hashing, email verification, rate limits, upload size caps, separation of each user's data, and baseline response headers.
If a breach significantly affects your economic or moral rights, we will notify you promptly with the nature, data involved, and steps you can take, and we will fix causes to prevent recurrence.
10. Changes to this notice
Minor wording fixes apply on publication with a new date. New purposes, new providers, or longer retention bump the major version and, when consent is required, ask for it again. The footer always links the current version.