Privacy guarantee

Private by architecture, not just policy.

Most apps have a privacy policy. Synap has a CI check. Third-party telemetry and analytics SDKs are on a banned-packages list that the build system enforces every pull request — the same way a lint rule prevents you from committing debug code.

What Synap stores

When you subscribe, Synap records three things and nothing more:

• Email address — so we can send your sign-in link and receipt.
• Lesson completions — which lessons you've marked complete. Used to show your progress and drive the streak counter.
• Streak state — the rolling 24-hour window. One timestamp. Nothing else.

Payment details are handled by Stripe. Synap never sees your card number.

What Synap categorically does not collect

• Behavioral telemetry — there are no page-view, scroll, click, or session-duration events.
• Device identifiers or ad IDs.
• Third-party tracking pixels or analytics scripts (Google Analytics, Mixpanel, Segment, Amplitude, and equivalents).
• Crash reporters that phone home (Sentry, Datadog, AppInsights). Error logs stay on the server.
• IP addresses beyond what a standard web server logs for a single request (not aggregated or linked to your identity).

Why the CI check matters

A privacy policy is a promise. A CI check is a constraint. Policies can drift — an SDK gets added under deadline pressure, a dependency pulls in a tracker transitively, good intentions erode over time. Synap's approach is different: the list of banned packages is checked on every commit. Adding a telemetry SDK doesn't just violate a policy; it breaks the build.

Compared to typical learning apps

Most platforms built on engagement need to track engagement. That means knowing when you opened the app, how far you scrolled, what you paused on, which notifications you ignored — all of which gets packaged and sold to advertisers or used to optimize for time-on-screen rather than learning.

Synap's business model is a subscription, not advertising. Knowing how many lessons you completed is sufficient for the product to work. Knowing how long you hovered before clicking is not needed and not collected.

The honest caveat

Synap uses Stripe for payments and Google Fonts for typography. Stripe necessarily processes your payment data under their own privacy policy. Google Fonts is loaded from Google's CDN, which means a font request leaves your browser. Both are industry-standard choices. Neither is a behavioral tracker inside the Synap product.