Privacy

Not in effect. Last updated: August 27, 2026. Version: privacy-draft-2026-08-27-v7. This is a shared working draft for the site and app. Before the next invitation wave, provider and retention facts must be verified, the policy must receive legal approval, and the approved version must be shown to participants.

Igor Ufimtsev is identified as the controller for data connected with the public site, early-access request, incoming emails, and the closed mobile-app beta. Requests can be sent to privacy@letsdao.org. LetsDAO is the project and community name, not a separate legal entity or independent data controller.

The draft covers letsdao.org, the early-access form, emails sent to the team, and the closed Lets mobile-app beta. It includes accounts, profiles, posts, stories, messages, Circles, meetups, notifications, reports, technical data, export, and account deletion.

The early-access form asks for an email address and one answer about who the person would like to start with: friends, family, a team or community, or on their own. The submission also includes page language and address, consent state, time, technical delivery data, IP address, and anti-automation signals. This is used for manual review, contact about an invitation, and form protection.

The team receives the sender address, sender name, subject, message text, attachments, and delivery metadata. Email is used to read and answer the request and protect the mailbox. Do not send passwords, verification codes, payment data, documents, health information, or another person's personal data unless it is necessary.

The current sign-in path requires an email address. Lets also processes an internal user ID, display name, username, bio, avatar, cover, privacy settings, blocks, friends, Circles, devices, sessions, and related security data. These are needed for sign-in, profile display, social features, account protection, and moderation.

Lets processes posts, comments, stories, reactions, selected places, media, messages, replies, Circle and meetup information, questions, and selected answers. This data comes from the participant or is created when the participant interacts with other people and product features.

The current cloud chat mode protects data in transit and at rest but can technically be decrypted by the service and is not end-to-end encryption. Access must be restricted to operational need and audited. Message content must not appear in push payloads, analytics, or ordinary technical logs. Future E2EE is not described as live until implementation, migration, and independent review are complete.

Photos, videos, and audio are processed only when a person selects or creates them for a profile, post, story, chat, Circle, or meetup. A person may choose an approximate place name for a post; precise location is not declared as collected for this release candidate.

The app and infrastructure may process device and installation identifiers, a push-notification identifier, IP address, session details, app and operating-system version, request time, errors, and limited diagnostics. This is needed for sign-in, notification delivery, abuse prevention, reliability, and troubleshooting.

A report or support request may include the specific material selected by the person, reason, explanation, related identifiers, and necessary technical data. These records are used for safety, abuse review, response, and legal obligations. A report must not grant the team general access to private history: the participant deliberately discloses the specific evidence they submit.

Data is used to create and protect an account, show profiles and content to the chosen audience, deliver messages and notifications, support Circles and meetups, apply privacy settings, review requests and reports, prevent abuse, keep the service working, and meet legal obligations. It is not sold to data brokers or used for third-party advertising in the current beta.

The preliminary working model relies on the person's request and future service terms for access and core features, legitimate interests for security and reliability, consent where it is genuinely required, and legal obligations where the law requires processing. Counsel must verify the basis for each category and country before this policy takes effect.

Lets uses Vercel for the public site, Resend and Yandex 360 for access-request delivery and email, Cloudflare Turnstile for form protection, Railway and PostgreSQL for the backend, Cloudflare R2 and CDN services for media, and Firebase Cloud Messaging and Apple platform services for notifications and beta distribution. Each provider's exact role, region, retention, and contract terms are still being verified.

Infrastructure may process data in more than one country. Before approval, the team must record each provider's regions, transfer mechanism, processing agreement, and any Russian-citizen data-localization requirements. The status of any required RKN notice also needs a separate owner and counsel decision.

Account and user content are kept while needed for the account, until deletion, applicable expiry, or a lawful restriction. Sessions and sign-in codes are time-limited. Public and protected media use dedicated retention and deletion processes. Encrypted backups are kept for no more than 35 days. Reports and security evidence may be kept longer under an approved schedule or narrow legal hold. Exact periods for access requests, email, logs, push data, and provider records are not yet confirmed.

A participant can request an export or delete the account in app settings after verifying a code sent to the account email. Deletion ends sessions and removes or anonymizes the profile, posts, stories, and related records under the current rules. It does not mean immediate disappearance from backups, lawful retention, reports, or text written by another person.

Send a request for access, correction, deletion, restriction, or information about processing to privacy@letsdao.org. The exact rights, response time, identity check, exceptions, and complaint path depend on applicable law and must be approved by counsel.

Optional analytics, advertising cookies, marketing pixels, A/B testing, and session replay are disabled on the public website. The early-access form uses Cloudflare Turnstile, which processes browser signals for anti-automation protection. The form contents are sent separately to Lets only after submission.

Lets uses protected connections, access controls, encryption at rest, log restrictions, session protections, and deletion processes. No system can guarantee absolute security. The current cloud chat mode should not be treated as E2EE or complete anonymity.

The closed beta is not currently intended for children and should not knowingly collect their data. A minimum age, age-assurance process, parental consent, and child-data deletion process remain mandatory legal and product decisions before the beta expands.

Each version will have a date and version number. Material changes should be shown before a participant continues, and the app should record the accepted version and time. Until that mechanism is connected, this document remains a draft.

Before approval, the team must close retention periods for requests and logs, the provider register, processing regions, international transfers, Russian localization and notice questions, the age model, rights-request handling, and any mismatch with the store privacy labels for the exact app build.