Privacy Policy

A note from the owner

I’m the owner of Low Expectations.

I don’t want your data. I don’t want to sell you ads. I don’t want your shit, and I don’t want to sell your shit.

The site collects some information because accounts, email, chat, uploads, games, security, and basic server operation cannot function without it.

My goal is to collect only what the site actually needs, secure it, avoid keeping it longer than necessary, and tell you plainly what happens to it.

Low Expectations does not sell your personal information. It does not use your private activity to build advertising profiles. It does not exist to follow you around the Internet and figure out what brand of toaster you might buy.

This policy explains what the server collects, why it exists, where it may go, and what deletion does and does not remove.

1. Who this policy applies to

This policy applies to lowexpectations.dev and the services operated through it, including:

• Accounts and profiles
• Games and leaderboards
• Chat rooms
• Temporary uploads
• Voice and screen sharing
• Watch-together features
• Low Expectations email
• Timeline of Everything
• Cloud saves
• The blood-pressure tracker
• DaVinci Loader
• Other applications and experiments hosted by Low Expectations

Accounts and interactive services are intended for people 18 years old or older.

2. What Low Expectations does not do

Low Expectations does not currently use:

• Google Analytics
• Behavioral advertising systems
• Advertising profiles
• Data brokers
• Third-party tracking pixels added for marketing
• A system for selling personal information
• A system for selling browsing activity
• Application-level recording of voice or video calls

Third-party websites and embedded services may perform their own tracking when you choose to use them. Those services are explained later in this policy.

3. Accounts and profiles

When you create or use an account, Low Expectations may store:

• Your account ID
• Username
• Display name
• Password hash
• Account status
• Creation and update times
• Avatar
• Chat-name color
• Hosted email address
• Recovery email
• Recovery-email verification status
• Account preferences

Passwords are stored as password hashes. The site does not need to know or store your original password after it has been processed.

Profile information such as your username, display name, avatar, and color may be visible to other users where those features are used.

Account information is kept while the account exists, subject to the deletion and backup limits described below.

4. Sessions, login history, and recovery

To keep you signed in and protect accounts, the site creates session tokens and records information such as:

• IP address
• User agent
• Session creation time
• Last activity
• Expiration time
• Revocation time
• Password-reset status
• Recovery-email verification status

Raw account-session tokens are stored in secure browser cookies. The server stores hashed versions where appropriate.

Normal account sessions are valid for up to 30 days. Expired sessions are normally removed after an additional 7 days. Revoked-session records may remain for up to 30 days.

Password-reset links expire after 30 minutes. Recovery-email verification links expire after 24 hours. Expired or used token records are normally removed within 7 days.

Recovery tokens are removed from the browser address immediately after the page loads so they do not remain visible in normal browser history or server query logs.

5. Cookies and browser storage

Low Expectations uses cookies and browser storage for things such as:

• Authentication
• Theme and accessibility preferences
• Music settings
• Game progress
• Trophies
• Chat identity and room access
• Voting
• Cloud saves
• DaVinci sessions
• Other feature-specific settings

Some cookies expire automatically. Browser local storage may remain until the browser, user, or site clears it.

Account deletion and logout attempt to clear account-related browser data. Some unrelated preferences, game progress, downloaded exports, or data stored in another browser may remain.

Authentication records, chat-room credentials, voice data, DaVinci credentials, and blood-pressure information are excluded from the site’s generic browser-storage export and migration tools.

Anyone with access to your browser profile may be able to access information saved locally by that browser.

6. IP addresses, logs, and security information

The server records technical information needed to operate and protect the Service, including:

• IP addresses
• User agents
• Request paths
• Request methods and status codes
• Referrers
• Login attempts
• Authentication identities
• Mail-routing events
• Failed logins
• Bans
• Rate-limit events
• Request and action timestamps
• Security and service errors

Nginx access logs omit query strings so tokens and other query parameters are not retained in ordinary request logging.

This information is used for:

• Authentication
• Abuse prevention
• Rate limiting
• Troubleshooting
• Intrusion blocking
• Mail security
• Account-session review
• Protecting server and IP reputation

Typical retention includes:

• Nginx logs: 14 daily rotations
• Application journal: no more than 30 days or 2 GiB
• Postfix, authentication, and Fail2ban logs: approximately 4 weeks
• Rspamd logs: 4 daily rotations
• Mail-security events: 90 days

Active bans may last longer than the log entry that originally created them.

Deleting an account does not immediately erase every security or rotated log entry associated with it.

7. Chat rooms and messages

Chat may store:

• Room names and identifiers
• Room-password hashes
• Room creators and owners
• Participant profiles
• Messages
• Edit and deletion timestamps
• Display names, avatars, and colors
• Attachment metadata
• Trophy counts
• Room-access information

Chat rooms and messages generally do not expire automatically. A room normally retains up to 200 messages, after which older message metadata may be removed.

Deleting a message removes that message and its referenced attachment from the active service. Deleting a room removes the active room and its referenced attachments.

Deleting an account does not necessarily remove historical chat messages, copied profile information, or rooms created through that account.

Restricted rooms are protected from unauthorized users, but they are not technically inaccessible to the server administrator.

Administrative access may occur when reasonably necessary to:

• Investigate an abuse report
• Repair the Service
• Respond to a security incident
• Enforce the Terms of Service
• Protect users or infrastructure
• Comply with legal obligations

Low Expectations does not promise that chat is end-to-end encrypted or inaccessible to the operator.

8. Temporary chat uploads

When you upload a file through chat, the Service may process:

• The file itself
• Original filename
• Generated storage name
• File type
• File size
• Associated room and message
• Upload and expiration times

Ordinary chat uploads normally expire after approximately 24 hours.

Attachment downloads require valid room-scoped authorization. Knowing or guessing a storage URL is not sufficient to access the file through the normal Service.

Deleting a message or room removes its referenced active attachments.

Reported files or files involved in legal, security, or abuse matters may be quarantined. Quarantined files cannot be downloaded through the normal Service and may be retained beyond the ordinary 24-hour period while the matter is reviewed or handled.

Do not use Low Expectations as permanent storage or as the only copy of an important file.

9. Voice, screen sharing, and watch-together features

Voice, video, screen sharing, and synchronized watching may process:

• Participant and room identifiers
• Display names and avatars
• Presence and connection information
• Network addresses
• WebRTC signaling information
• Stream and share status
• Media URLs
• Playback position
• Queue and watch history
• Temporary room and TURN credentials

Voice and video media may pass through self-hosted LiveKit and TURN services.

Low Expectations does not currently record voice calls, video calls, or screen-sharing sessions at the application level.

Most signaling and presence information is temporary and normally disappears after expiration, room deletion, service restart, or disconnection.

Voice and video are protected during transport but are not configured with application-level end-to-end encryption that prevents the self-hosted media server from technically handling relayed media.

Google STUN may receive public network information during connection setup.

YouTube, Twitch, and other media hosts may receive normal browser information when their media or embeds are loaded.

10. Low Expectations email

The email service processes and stores information needed to receive, send, filter, display, and synchronize mail, including:

• Mailbox addresses
• Aliases
• App-password hashes
• Sender and recipient addresses
• CC and BCC fields
• Message subjects
• Plain-text and HTML message bodies
• Attachments
• Message identifiers and dates
• Delivery and queue status
• IP addresses
• Authentication identities
• TLS status
• Spam scores and filtering results
• Virus-scan results
• Mailbox folders and actions
• Quota and message-count information

Messages are stored in mailbox files on the Low Expectations server until deleted, expunged through mailbox cleanup, or removed because of quota or administrative action.

Deleting a message normally moves it to Trash. Deleting it again from Trash removes it from the active mailbox. There is not currently one universal deadline guaranteeing when every deleted-mail remnant disappears from every server component.

Mail is processed locally by Postfix, Dovecot, Rspamd, Redis, and ClamAV. ClamAV is configured not to retain temporary scan files.

Rspamd keeps a limited recent-message history of approximately 200 entries with subject privacy enabled. Learned spam-filtering data normally expires after approximately 180 days.

Authenticated user submission requires encryption. Delivery between independent mail servers uses encryption when the other server supports it. Email is not automatically end-to-end encrypted.

The mailbox owner can read mailbox content. The server administrator has technical access to mailbox storage and mail-system administration. Low Expectations does not provide a casual administrative mail-reading feature, but technical access may occur when required for operation, security, abuse response, or legal compliance.

Outbound messages and attachments are transmitted to their recipients and the recipients’ email providers. Low Expectations cannot delete copies held by recipients or outside providers.

Remote images are blocked by default. If you choose to load them, the remote image host may learn your IP address, browser information, access time, and message-specific URL information.

Current mailbox limits are 500 messages or 75 MB, whichever is reached first. New accounts must be 24 hours old before creating a mailbox.

11. Games, scores, trophies, and community features

Games and community systems may store:

• Player names and identifiers
• Account associations
• Game modes and status
• Scores and completion times
• Navigation paths
• Challenges
• Favorites
• Votes
• Reports
• User-created routes or content
• Replay videos
• Trophy progress
• Settings and saved progress

Some information is intentionally public, including leaderboard names, scores, completion times, published challenges, public routes, vote totals, and eligible replay videos.

Game and leaderboard information may remain indefinitely unless administratively removed. Deleting an account may remove the account link without deleting the historical score, challenge, game session, public creator name, or leaderboard record.

Froggrid (also called Frogdoku) has its own game-specific policy: https://www.lowexpectations.dev/games/frogdoku/privacy.

Bread Slicer replay videos are retained only while the associated record remains among the eligible top runs.

12. Timeline of Everything

Timeline of Everything may store:

• Event titles and descriptions
• Dates
• Tags
• Locations
• People and organizations
• Source links
• Author information
• Theme and media customization
• Revisions
• Votes
• Browser voter-token hashes
• Submission IP addresses
• Reports and review history
• Audit information

Timeline submissions are normally published immediately and marked unmoderated until the server administrator approves or rejects them. Event titles, descriptions, dates, tags, locations, and submitted source links should therefore be treated as public at submission time.

Pending submissions, contributions, merge requests, vote records, and submission IPs are available to the server administrator. Timeline moderation notes and moderation-history records are not retained.

Timeline records and audit history may remain indefinitely unless administratively removed. Timeline database backups normally remain for approximately 14 days.

13. Cloud saves and blood-pressure information

Account cloud saves may contain:

• Game progress
• Preferences
• Application settings
• User-created JSON data
• Current save versions
• Up to 10 archived versions per save slot

Deleting a cloud-save slot now removes its archived versions as well.

Deleting an account removes current and archived cloud saves from the live account database, but browser copies, exports, logs, or backups may remain according to their own retention periods.

The blood-pressure tracker may store sensitive personal information, including:

• Reading date and time
• Systolic pressure
• Diastolic pressure
• Pulse
• Time of day
• Notes
• Record identifiers and timestamps

Blood-pressure readings and notes are not synchronized to the server unless you explicitly opt in after seeing a privacy warning.

The tracker is an informal personal tool, not a medical provider, medical-record system, or substitute for professional medical advice.

14. DaVinci Loader

DaVinci is available without requiring a permanent Low Expectations account, but activity is isolated through a temporary signed session.

DaVinci may process:

• Temporary session identifiers
• IP and user-agent binding information
• Repository, path, and branch selections
• Commands
• Job status
• Standard output and error logs
• Generated files and CSVs
• Uploaded workspace files
• Timestamps and runtime information

DaVinci signed sessions normally last up to 8 hours. Abandoned sandboxes normally expire after approximately 6 hours of inactivity. Completed jobs and artifacts normally remain for up to 7 days.

Only the owning signed session may normally access its jobs, logs, files, workspace, and terminal.

Do not enter passwords, private keys, access tokens, private repository credentials, medical information, or other sensitive material into DaVinci.

15. Backups

Low Expectations creates backups to recover from server failures, broken deployments, upgrades, and other disasters.

Backups may contain:

• Account and profile information
• Database records
• Chat data
• Game and leaderboard information
• Timeline data
• Mail configuration and metadata
• Application files
• User-generated content
• Information later deleted from the live Service

Ordinary manual backups are normally kept for up to 90 days unless specifically held for recovery, security, legal, or remediation purposes.

Timeline database backups are normally kept for approximately 14 days.

Mailbox data quarantined during account deletion is normally kept for 30 days before removal.

The current remediation backup is being held until explicitly released. OVHcloud snapshot retention is controlled separately through OVHcloud.

Deleting information from the active Service does not immediately rewrite or erase existing backups. Restored backups may temporarily reintroduce previously deleted information until deletion is reapplied.

16. Third parties

Low Expectations does not sell your information to third parties.

Information may still reach third parties when required to provide a feature you use.

These may include:

• OVHcloud: Hosts the server, network, disks, and provider-side snapshots.
• External email providers and recipients: Receive messages, attachments, headers, delivery metadata, and recovery emails.
• Google STUN: May receive public network information during WebRTC setup.
• YouTube and Twitch: Receive normal browser and network information when watch-together embeds are used.
• Other media and iframe hosts: May receive browser and network information when you load user-supplied media.
• jsDelivr: Provides a browser library used by DaVinci.
• MTSudoku: May receive Sudoku-generation requests from the browser.
• Wikipedia: Receives article and API requests, normally from the Low Expectations server.
• GitHub and GitLab: Receive public repository requests made through DaVinci.
• Remote email-image hosts: Receive information only if you choose to load remote images.
• ClamAV update infrastructure: Receives server update requests, not your message contents.

Those services have their own privacy practices. Low Expectations does not control information they collect directly from your browser or through their services.

17. Administrator access

The server administrator has technical access to:

• Databases
• Server logs
• Backups
• Mailboxes
• Chat data
• Uploaded files
• DaVinci workspaces
• Configuration
• Security systems

This access exists because somebody has to operate, secure, repair, and recover the server.

Administrative access may be used for:

• Maintenance
• Security
• Troubleshooting
• Abuse response
• Account recovery
• Data deletion
• Backup restoration
• Legal compliance

Low Expectations does not routinely inspect private messages or files for entertainment, advertising, profiling, or sale.

Not every direct shell, database, or filesystem action currently produces an independent application-level audit record.

18. Account exports

The account-export feature may include:

• Core account information
• Active-session information
• Current and archived cloud saves
• Mailbox settings
• Aliases
• Mail-security events

It does not necessarily include:

• Email message bodies
• Chat history
• Every game record
• Public leaderboard data
• Timeline records
• DaVinci data
• Rotated logs
• Backups
• Copies held by third parties

An export is a useful account-data snapshot, not a guaranteed copy of every byte that has ever been associated with you.

Downloaded exports become your responsibility. Low Expectations cannot protect or delete copies saved on your device or shared elsewhere.

19. What account deletion removes

Deleting an account removes the active account row and associated live information such as:

• Password hash
• Profile information
• Recovery addresses
• Primary sessions
• Recovery and reset tokens
• Current and archived cloud saves
• Live mailbox and alias database records

Associated mailbox files are moved into a path-restricted deletion quarantine. They are normally removed after 30 days. If database deletion fails, the mailbox may be restored automatically to prevent accidental data loss.

Client-side deletion and logout also attempt to clear account-related browser storage.

20. What account deletion may leave behind

Deleting an account does not necessarily remove:

• Historical chat messages
• Rooms
• Public scores
• Trophies
• Votes
• Challenges
• Game history
• Leaderboard records
• Replay records
• Timeline submissions
• Community reports
• Separately stored application data
• Security events
• Rotated logs
• Backups
• Copies on another browser or device
• Downloaded exports
• Messages already delivered to outside recipients
• Information retained by third parties

Some retained records may have their account link removed or may remain under a historical public name.

Reported, quarantined, or legally preserved files may remain until they are reviewed and lawfully released or destroyed.

Low Expectations cannot remotely delete information held by another person, browser, mail provider, hosting provider, or external service.

21. Security

Low Expectations uses measures intended to protect information, including:

• Password hashing
• Hashed session tokens
• Encrypted authenticated connections
• HttpOnly authentication cookies
• Room-scoped attachment authorization
• Query-string-free access logging
• Firewall rules
• Rate limits
• Fail2ban
• Spam filtering
• Malware scanning
• Restricted runtime secrets
• Backups
• Session isolation
• Service-specific access controls

No Internet service is perfectly secure.

Do not use Low Expectations for information that requires guaranteed secrecy, guaranteed availability, or permanent preservation.

22. Legal and abuse disclosures

Low Expectations may preserve or disclose relevant information when reasonably necessary to:

• Comply with applicable law
• Respond to valid legal process
• Report suspected criminal activity
• Protect a person from harm
• Investigate abuse
• Protect Low Expectations, its infrastructure, or its users
• Enforce the Terms of Service

Illegal content may be quarantined and reported to NCMEC, law enforcement, OVHcloud, or another appropriate authority when required or permitted.

23. Changes to this policy

This policy may change as Low Expectations adds, removes, or modifies features.

The date at the top identifies the latest published version.

Material changes may be announced through the website, account interface, or email.

24. Contact

Privacy questions:

privacy@lowexpectations.dev

Abuse reports:

report@lowexpectations.dev

Email abuse:

abuse@lowexpectations.dev

Security problems:

security@lowexpectations.dev