DropIn Free Beta Privacy Notice
1. Categories, purposes, and legal bases
Account, authentication, profile, and preferences include email, authentication identifiers, display name, avatar, bio, language, and security records. They support registration, login, profile display, and abuse prevention on the bases of providing the requested service and legitimate interests in safety. A phone number is processed only if phone registration is enabled and the SMS provider is verified.
Posts, photos, saved items, messages, mutual aid, and reviews support publishing, search, matching, communication, and completion of mutual aid on the basis of providing the service. Reports, blocking, moderation, appeals, and support data protect the community, enforce rules, and handle disputes on legitimate interests and, where necessary, legal obligations or legal claims. Product feedback is used to fix Bugs and improve the product on legitimate interests.
Consent evidence records the Terms and Privacy versions, time, account, and registration method to prove notice and acceptance. Security and audit logs may include IP address, time, device/browser, and event data for abuse prevention, troubleshooting, and security audit.
2. Required data, visibility, and recipients
Email and authentication data are required for an account and are not public. Display name, avatar, bio, posts, photos, and reviews are visible to other users as indicated in the interface. Messages are visible only to participants; reports, support, and evidence attachments are restricted to the user and authorised reviewers.
Without required account data, registration is unavailable. Optional profile data only affects the related display or personalisation. Do not submit unnecessary identity documents, card data, health information, precise home addresses, or another person's private data in posts, messages, or attachments.
3. Retention
Account and profile data remain while the account is active. After 24 months without activity, DropIn reviews inactivity and sends a warning; if there is no response within 30 days, the account enters closure and deletion. Deleted profile data, posts, or a closed account stop being publicly visible immediately, with a 30-day target for removal from active systems.
Messages, mutual aid, and reviews remain while the account is active and have a 30-day deletion or irreversible anonymisation target after closure. If linked to an open safety case, only the necessary part remains until six months after closure of that case. Reports, moderation, appeals, and support remain for 24 months after case closure; product feedback remains for 24 months and is then deleted or anonymised.
Consent evidence remains during the account and for up to five years after closure where necessary for compliance evidence or legal claims. Security and audit logs roll for no more than 12 months. A legal hold extends only the disputed minimum and is reviewed. Backup copies are not used for normal operations and age out through the verified provider rotation cycle.
4. Service providers
Supabase supplies authentication, database, and file storage; Vercel supplies hosting, server runtime, and technical logs; Resend sends verification, notification, and support transactional email. Google processes OAuth data only when Google sign-in is selected. DeepL receives text only when a user requests translation.
The free Beta uses no advertising or behavioural profiling. Phone authentication stays disabled until the real SMS provider, processing location, and terms are verified and added to this Notice. Providers receive only the data needed for their function.
5. International processing
Providers may process data outside the EEA or China, including in the United States. Resend states that customer data is stored in the United States and relies on its DPA, EU Standard Contractual Clauses, and stated transfer mechanisms. The actual Supabase project region, Vercel runtime, and other paths are determined from current production configuration.
Where GDPR applies, transfers use an adequacy decision, Standard Contractual Clauses, or another applicable safeguard. Where China's PIPL applies, required notice, separate consent, or another mechanism will be completed according to the real transfer path and scale. Safeguard information can be requested by email.
6. Your rights
Email hellodropin666@gmail.com to request access, correction, erasure, restriction, portability/export, objection to legitimate-interest processing, or withdrawal where consent is the basis. DropIn normally responds within one month and requests only the minimum identity verification needed, not an identity-document image by default.
Rights are not absolute. If minimum data must remain for another person's rights, an open safety case, a legal duty, or legal claims, DropIn explains the scope and reason. EU users may complain to the CNIL: https://www.cnil.fr/fr/plaintes.
7. Security, cookies, and automation
DropIn uses HTTPS, access controls, Supabase row-level permissions, private evidence storage, restricted administration, and audit records, updating measures according to risk. A breach likely to create high risk is notified as required to authorities and affected users.
The free Beta uses only login, language, currency, and security cookies or local storage, with no advertising trackers. Automated rules may screen manifestly high-risk content, but a significant account restriction can receive human review; there is no solely automated profiling decision with legal or similarly significant effect.
8. Anonymous product measurement and error aggregation
DropIn uses daily anonymous aggregate counts without personal identifiers to understand page use, search outcomes, and whether product flows work. It does not use a cookie, local-storage identifier, user ID, IP address, email address, or cross-site identifier to link a person or session.
Error monitoring stores only a non-reversible error fingerprint, fixed route group, fixed error category, occurrence count, first and last observation time, and application release. Product and error aggregates are retained for no more than 90 days. They do not record post or message content, raw search text, form content, URL parameters, access tokens, or images. Accounts, posts, messages, and other business records keep the separate retention rules described elsewhere in this Notice.
9. Changes and renewed acceptance
A company formation, charging, advertising/profiling, a major new data category or purpose, or a material transfer change triggers a new version and renewed acceptance. Minor clarification updates the date and is communicated on the page, in-app, or by email.