Reconnecting

The current page stays visible while onset.to reconnects in the background.

onset.to

Data privacy

This page describes which services onset.to uses, what data the app stores, and where third-party services are involved.

onset.to is a small, non-commercial hobby project. The list below reflects the current app and public site.

Services we use

Cloudflare provides DNS and redirects onset.to to www.onset.to.

bunny.net hosts the website and runs background jobs in Frankfurt. It delivers the public site over HTTPS.

The Fly.io hosting instance is stopped and retained as a fallback.

Aiven for PostgreSQL stores the application data.

PostHog is used for public-page analytics.

Brevo is used for transactional account email delivery.

OpenRouter routes bounded source text and metadata to the configured model provider for link classification and summaries. The selected model provider can change with the processing configuration.

onset.to also fetches content from external sources such as websites, RSS feeds, YouTube, and Reddit-linked URLs as part of crawling, ingestion, and preview workflows.

Provider addresses

Cloudflare, Inc.
101 Townsend St
San Francisco, CA 94107
USA

BunnyWay d.o.o. (bunny.net)
Dunajska cesta 165
1000 Ljubljana
Slovenia

Fly.io, Inc.
2261 Market Street #4990
San Francisco, CA 94114
USA

Aiven Oy
Antinkatu 1, 6th floor
00100 Helsinki
Finland

PostHog Inc.
2261 Market Street #4008
San Francisco, CA 94114
USA

Brevo / Sendinblue SAS
106 boulevard Haussmann
75008 Paris
France

OpenRouter, Inc.
169 Madison Avenue
New York, NY 10016
USA

Data we store

We store newsletter email addresses when someone subscribes through the public site.

We store account email addresses, hashed passwords, confirmation timestamps, and related account timestamps for registered users.

We store session and login tokens for authentication, including remember-me and email-login flows.

We store submitted links and related content metadata such as URL, source id, title, summary, author, publication date, tags, language, format, publication status, and technical pipeline state.

We store read-state information that marks which links a signed-in user has already read.

We store public link suggestions and reports, including comments, proposed edits, report reasons, and review status.

We store processing logs and crawl logs so background jobs, ingestion runs, and failures can be debugged and audited.

HTML processing sends at most 60,000 characters of extracted source content to the configured model. Processing logs omit that source body and store extraction details and a content hash instead.

Technical and analytics data

Server-side request logging may include technical request metadata such as IP address, forwarded headers, host, path, and user agent.

Public pages can load PostHog analytics. PostHog may use browser-side persistence for anonymous analytics, and logged-in users may be identified there as user:<id>.

Phoenix also uses session cookies, CSRF protection, and optional remember-me cookies to keep authentication and form flows working.

Questions

If you have questions about privacy or data handling, visit Contact , write to hello@onset.to , or reach out on r/onset .