Last updated August 19, 2026
Privacy policy
LakeTime is a pre-launch lake community service operated in New Hampshire. This policy describes the website, waitlist, private test app, and public plan links in the build dated above.
Who may use LakeTime
LakeTime is for people 13 and older and is not directed to children under 13. The app asks for a birth year and, only when needed at the age boundary, month and day. That calculation happens on the device. LakeTime stores only the resulting 13–17 or 18+ band—not the birth year, month, or day. An under-13 result cannot continue.
Information we collect
- Waitlist and nominations: email address, and any lake name, water type, or region you nominate.
- Account: authentication email, first name, age band, lake connection, preset avatar, and account timestamps.
- Optional profile details: lake tenure, interests, skills, things you want to learn or do, and notification preferences. In first-live these remain private to you.
- Community activity: plans, attendance, plan messages, time-limited statuses, condition observations, lake knowledge, help requests and responses, votes, blocks, and reports you choose to submit.
- Approximate location: a named lake area and generalized map coordinate you choose. LakeTime does not continuously track a device, record a route, or request background location in this build. A host may place a joined-plan Water Pin; it is available only to the host and joined attendees while that plan is open.
- Operations: moderation decisions, rate-limit records, delivery drafts, content-free plan-closure notices, and ordinary security/server logs created by our processors.
What other people can see
Signed-in lake members may see visible plans, first names, approximate lake areas, community posts, and counts allowed for their age band. A public website or shared plan link never shows an attendee-name roster, a plan thread, a Water Pin, or a teen identity.
Teen-only plans and teen statuses are available only to signed-in 13–17 accounts. Adults cannot browse them. In a mixed-age plan, a teen's first name may be visible only inside the closed plan to its host and joined participants so they can coordinate; it is not placed on the public web or adult discovery map. LakeTime has no parent-account system and does not ask a teen for a parent's contact information.
How we use information
We use the information to authenticate accounts, provide and moderate lake activity, enforce age and blocking rules, operate safety and abuse controls, respond to support or legal requests, improve reliability, and decide which lake to open next. We do not use account data for targeted advertising, sell personal information, or include third-party advertising or behavioral-tracking code in this build.
Service providers and external requests
| Provider | What it does | Data involved |
|---|---|---|
| Supabase | Authentication, database, and moderation/account operations | Account email, app records, security metadata, and requests sent to those services |
| Vercel | Hosts and serves the web app | Ordinary request data such as IP address, user agent, requested URL, and server logs |
| OpenFreeMap | Serves live vector map labels and fonts to the map | Your browser's IP address, user agent, and requested map tiles; LakeTime does not send your account profile or activity pins |
| Open-Meteo | Provides server-fetched air temperature, wind, gust, and sunset for the lake | The fixed lake coordinate and LakeTime server request—not your account or device location |
OpenStreetMap data is included in LakeTime's pre-rendered map and credited in the app; the app does not request map data from OpenStreetMap unless you choose to follow its attribution link. Google fonts are downloaded at build time and served by LakeTime, so the app does not contact Google Fonts when you use it. Vercel Web Analytics is not installed in this build.
Moderation and safety
Community content passes through deterministic moderation checks. Rules-safe messages from an adult account in good standing can appear immediately. Rule hits are held for review. Any plan thread with a 13–17 participant is screened before a message is displayed. Users can report content and block another profile; blocking makes both people's plans mutually invisible and does not notify the blocked person.
Retention
| Data | Current retention behavior |
|---|---|
| Account, profile, and authored community content | Kept while the account exists; removed through the in-app account deletion flow. |
| Active plans, statuses, conditions, and help requests | Automatically leave active views when cancelled, ended, or expired. Historical database deletion is not yet scheduled; account deletion removes the account's authored records. |
| Plan messages | Kept with the plan while the account exists. The earlier proposed 90-day automatic deletion is not yet enforced. |
| Moderation, reports, and security records | Raw moderation notes and reported content tied to a deleted account are removed. LakeTime retains a content-free enforcement fact for 24 months after deletion: a secret-keyed one-way account fingerprint, rule key, event time, and outcome—never the email, post, message, report details, reviewer note, or target ID. Expired facts are purged by service-role moderation/deletion maintenance; there is not yet an independent continuous purge timer. A report about another person is not erased because its reporter leaves; the reporter identity is replaced with the private fingerprint. |
| Host-deletion closure notices | If a host deletes an account while you joined or followed one of their active plans, LakeTime keeps a content-free notice for your account for up to 30 days or until you dismiss it. It says that the host account was deleted and how many affected plans closed; it keeps no host identity, plan ID, plan text, location, roster, thread, or meeting point. |
| Waitlist and lake nominations | Kept until removed on request. In-app account deletion also removes records using the same email. |
| Processor logs | Retained under each processor's operational settings and agreements; LakeTime does not yet promise a shorter custom log period. |
Your choices
Settings includes a JSON download of the data associated with a signed-in account and an in-app account deletion control. Deletion removes the profile, authored posts, plan threads, attendance, settings, waitlist entry, lake nominations, and authentication record. It does not erase a report the account filed about somebody else; that report keeps no reporter identity. The limited 24-month enforcement fact described above also survives deletion so deleting and re-registering cannot erase abuse history. If deletion closes a plan that other people joined or followed, each affected person receives only the content-free 30-day notice described above. If the final authentication cleanup fails after app data is removed, the screen says so and provides the contact below. You can edit profile information in the app, withdraw from plans, end a status, cancel your own plan, block people, stop sharing location details, or dismiss a closure notice.
For a waitlist-only deletion, a correction, an export you cannot access, or a privacy question, email hello@laketime.app. We may ask you to verify control of the account or email before acting.
Security and changes
LakeTime uses authenticated, access-controlled application boundaries and service providers configured for encrypted network connections. No internet service can promise perfect security. Material policy changes will be dated here; we will ask for new consent before using personal data for an incompatible new purpose.
Contact
Last updated: August 19, 2026. This text describes the current private-test build; it is not a promise that parked features are live.