How Seen handles personal data

Who is responsible

The publisher identified below is the controller for Seen. Questions and privacy requests can be sent to hello@seen.is.

Data we process and why

• Authentication and membership. We process your email address, provider subject identifier, login method, session records, and credential-security state to create and protect your Member access. If you choose Google or LinkedIn, that provider supplies the identity assertion to Supabase. Seen does not automatically import your provider biography, employer, or profile content.
• Your Profile and Impact Cards. We store the content you enter, a revision number needed to prevent conflicting writes, publication choices, and aggregate view/share counters so we can provide the service. Only a Profile and Metrics you deliberately publish are delivered publicly.
• Security and abuse prevention. We process bounded request context, correlation identifiers, session activity, and keyed fingerprints derived from network addresses. These support CSRF protection, rate limits, fraud prevention, incident investigation, and reliable retries; raw addresses are not stored in the Seen security-event tables.
• Messages. We process an address and delivery details when sending a magic link, recovery message, security notification, or replying to contact email. Message bodies, login tokens, and raw provider payloads are excluded from general application logs.
• Product analytics. Rybbit, hosted by Seen on Hetzner, records page visits, selected interactions, technical errors, Web Vitals, and privacy-masked session replay so we can understand and improve the service. After authentication, Seen supplies the Member ID and Primary Email so activity can be joined to the Member journey.

The legal bases are performance of the service you request (Article 6(1)(b) GDPR) and the publisher's legitimate interests in service security, abuse prevention, and dependable operation (Article 6(1)(f) GDPR). A different basis may apply where law requires it.

Providers and transfers

Seen uses the following providers for defined operational purposes:

• Supabase for managed authentication and the Frankfurt PostgreSQL project.
• Purelymail for authentication and security email delivery.
• Google or LinkedIn only when you choose that sign-in method. Their own notices also apply to their processing.
• Hetzner for production infrastructure. Separate application-managed backup archives are not currently active.
• Seen's self-hosted Rybbit instance for private product analytics and consent-eligible session replay.

Some providers may process data outside the European Economic Area. Provider entities, processing locations, data-processing terms, and transfer safeguards are reviewed as part of launch configuration and when providers change.

Retention

• Member and private Profile data remain while needed to provide Seen and until deletion is required or agreed after a request.
• One-use callback state stops being accepted within 15 minutes. Seen sessions stop being accepted after a 30-day idle window or 90-day absolute limit unless revoked sooner. Expired database rows may remain in physical storage until an owner-reviewed cleanup process removes them.
• Security-event rows carry a 30-day target timestamp for keyed network-address fingerprints and a 90-day target timestamp for the row. Public-card fingerprints suppress duplicate counting for 24 hours and carry a 7-day row-expiry target. Physical deletion at those timestamps is not currently automated.
• Seen does not currently create separate application-managed backup archives. If that capability is activated later, this notice will be updated before those archives contain Member data.

Cookies and local browser storage

Analytics is enabled by default. Rybbit stores a random visitor ID and, after authentication, a Member identifier in local browser storage. It does not use advertising cookies. Seen also uses secure authentication and CSRF cookies, one-use callback binding, and a local Onboarding Draft you control in your browser. Clearing the draft does not affect a durable authenticated Profile.

Turn analytics off on this browser after JavaScript loads.

Your choices and rights

Depending on the circumstances, the GDPR provides rights of access, rectification, erasure, restriction, portability, and objection. You may also complain to a competent data-protection supervisory authority. Contact us at hello@seen.is so the request can be verified without disclosing Member data to someone else. Automated decision-making with legal or similarly significant effects is not used.

Publisher and contact

Last updated: 3 September 2026.