Privacy notice
Updated:
Who is responsible
Yosava is run by Zinedine Kriaa, its founder, as an individual based in Switzerland. He is the controller responsible for your personal data. Contact: yosava.tge@gmail.com.
What we collect
When you sign in, we send your email address to Supabase Auth to send and verify an email code and create an account if needed. A temporary cookie stores your email during sign-in, and Supabase Auth session cookies keep you signed in.
Your watchlist stores your account identifier, the projects you add and when you added them. It is private to your account.
Vercel request and runtime logs can include IP addresses, user agents, request paths and search parameters, timestamps, response status and application console output. Supabase API logs can include IP addresses, user agents, referrers, request URLs, timestamps and response status. Supabase Auth logs can include email addresses, account identifiers, authentication events, request paths and remote addresses; Auth audit logs can also include user agents. Fields are not populated for every event, and server-side requests may identify our server rather than your device. We do not forward these logs elsewhere or add logging beyond the providers’ standard logs. The application logs fixed sign-in and watchlist failure categories rather than submitted email addresses or codes.
What we do not collect
The application has no analytics, advertising cookies or tracking cookies. It has no functionality to sell personal data or share it for marketing.
Why we use this data
We use your email address and verification code to sign you in, and cookies to complete sign-in and keep your session. We use your account identifier and saved project entries to keep, display and change your watchlist. Fixed failure logs help diagnose sign-in and watchlist failures.
Processors and storage
Yosava uses Supabase for the database and sign-in, Resend for sign-in email and Vercel for hosting.
The production Supabase database, Auth service and backups are hosted in Frankfurt (eu-central-1). Supabase says its logs are ingested and stored in EU data centers, while support and operations can involve processing outside the project region. Vercel functions run in Frankfurt (fra1). Vercel may process its request and runtime logs outside Switzerland and the EU, including in the United States, under its data processing agreement. Resend offers sending regions in North Virginia, Ireland, São Paulo and Tokyo; Yosava uses Ireland (eu-west-1) for sending. Resend stores customer data, including message content and delivery logs, in the United States regardless of the sending region.
Vercel’s DPA provides for EU Standard Contractual Clauses for transfers from the EEA, UK and Switzerland where those clauses apply, with a UK transfer addendum. Supabase says transfers to Singapore and the United States use Standard Contractual Clauses incorporated in its DPA. Resend’s DPA includes EU Standard Contractual Clauses, a UK Addendum and Swiss modifications; Resend also describes the EU–U.S. Data Privacy Framework and UK Extension as an additional transfer mechanism.
How long data is kept
The temporary sign-in email cookie expires after one hour and is cleared after successful code verification. You can remove individual watchlist entries. Deleting an Auth account also deletes its watchlist entries from the database.
We keep accounts until you ask for account deletion and watchlist entries until you remove them or ask for account deletion. We do not automatically delete inactive accounts.
Auth session cookies are set with a maximum age of 400 days when written by the installed Supabase SSR library; this does not make an access token valid for 400 days. The session contains an access token and a refresh token. Supabase’s default access-token expiry is one hour. The server client checks token expiry when loading the session and can exchange the refresh token for new tokens; Yosava’s proxy writes refreshed cookies. Refresh tokens have no fixed expiry and are normally exchanged once, with documented reuse exceptions. Supabase sessions last indefinitely by default until sign-out or another terminating event. We use Supabase’s default session settings.
Vercel documents one hour of runtime-log retention on the Hobby plan Yosava currently uses, and one day on Pro. Supabase Pro includes seven-day API, database and Auth audit log retention and the last seven days of daily database backups. Sign-in audit entries are not written to the production database, and we use no backup or log archive options beyond these.
Resend retains email data and logs for 30 days on Free, Pro and Scale plans, with flexible retention on Enterprise. Its backups persist for seven days. Resend says remaining customer data is deleted within 90 days after termination of the Resend account; dashboard account deletion takes seven days, with backup copies expiring seven days later. These periods concern the Resend account, not deletion of an individual Yosava account.
Cookies
The sign-in email cookie and Auth session cookies are strictly necessary for sign-in and maintaining a session. They are HttpOnly, use SameSite=Lax and are Secure outside development. The temporary email cookie is limited to /sign-in. No cookie consent banner is used.
Your rights and requests
Under the Swiss Federal Act on Data Protection and, where it applies, the EU General Data Protection Regulation, you can ask to access or correct your personal data, delete your account and its watchlist, or request a copy of your data, and ask to restrict or object to processing where applicable. Send requests to yosava.tge@gmail.com. You can also complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC) or, if you are in the EU, to your local data protection authority.
Changes to this notice
Changes will be published on this page with a revised updated date. The updated date is shown at the top of this notice.