Privacy

SeeWith is operated by Nikola Vrdoljak, Ulica Branka Jančića 21, 10291 Gornji Laduć, Zagrebačka županija, Croatia(“SeeWith”, “we”). We are the controller of the personal data described here. For anything on this page, write to support@seewith.io, or by post to the address above.

Google sign-in is the only way to sign in to SeeWith. Email and password sign-in is not enabled on this deployment.

When you sign in, SeeWith receives and stores from Google:

• your name, as Google reports it;
• your email address, and whether Google reports it as verified;
• a link to your Google profile picture. SeeWith never displays it — the interface draws a small glyph from your initials instead, and the picture URL is not sent to the browser;
• an identifier for your Google account, and the scope you granted.

SeeWith never stores Google access tokens, refresh tokens or ID tokens. For each signed-in session SeeWith stores a random session token, when the session was created and when it expires, your browser’s user-agent string, and a pseudonymised network identifier — a one-way keyed hash. Your IP address itself is never written to the database, its backups, or the logs.

To run SeeWith on a video you need an active Core or Plus plan, or a dated allowance SeeWith granted to a closed-beta account. Your use is metered against that allowance: time counts only while SeeWith is actively analysing a playing video for you (each analysis counts the time since the previous one, at least 8 seconds); pausing, closing the tab or losing the connection does not count. When the allowance is used up, SeeWith automatically stops creating new context until your next billing period. Without a plan or a granted allowance, SeeWith does not analyse videos.

SeeWith also records usage counters for each session — which video, how long it ran, how many analyses and provider calls it made, and their estimated cost. They are linked to your account, are never shown to anyone outside SeeWith, carry no name, email address or IP address, and are deleted after 90 days.

On its own server, for your account:

• Watch history — which YouTube videos you opened in SeeWith, your last position in each, and when you last watched.
• Episode state — the topics and context cards generated while you ran SeeWith on an episode.
• Saved topics and your preferences.
• Public metadata about the videos themselves — id, title, author and duration. This is shared across SeeWith and is not linked to any person.
• If SeeWith asked you to accept its Search results terms: whether you accepted them, which version, and when.

Lemon Squeezy (Link, LLC, formerly Lemon Squeezy LLC, United States) runs the checkout and is the Merchant of Record. It processes what you enter at checkout — payment method, billing address and email — as a separate controller, under its own Buyer Terms and privacy policy, which say that this data is stored and processed in the United States, with transfers from the EEA protected by the European Commission’s standard contractual clauses. SeeWith never receives your card number or billing address.

When you start a checkout, SeeWith sends Lemon Squeezy the plan you chose; your account email, only if it is verified, to prefill the form; a time-limited reference that lets SeeWith recognise the purchase as yours; the pages to return to; and when the checkout page expires. When you press Manage, SeeWith asks Lemon Squeezy for a link to your customer portal.

SeeWith stores about your subscription: the link between your account and Lemon Squeezy’s customer reference; the subscription’s reference, plan and status; the end of the current period and whether it ends then; where it applies, the date until which already-paid time can still be used after a failed renewal; when it last changed and was last checked; a log of Lemon Squeezy’s notifications (event type, subscription, time received, whether processed, and a hash — not the content); and, per billing period, the time granted and used, the number of processing steps and SeeWith’s internal cost estimate.

• Your account, sign-in, watch history, episode state, and providing the service you signed up for — performing our contract with you (Article 6(1)(b) GDPR).
• Linking a purchase to your account, granting and metering your allowance, answering billing questions — performing our contract with you (Article 6(1)(b)).
• Handling your privacy requests — our legal obligation (Article 6(1)(c)).
• Linking usage counters to your account to know what SeeWith costs per person and to notice disproportionate use, and keeping subscription records after a subscription ends for payment, refund or dispute claims — our legitimate interests (Article 6(1)(f)).

Without the data needed to perform the contract we cannot provide the service. Nothing on this page relies on your consent.

On a server rented from Hostinger in a data centre in Germany (Frankfurt am Main), in a PostgreSQL database backed up nightly. Backups are encrypted before they leave the server and are held by Backblaze in the Netherlands (Amsterdam), who cannot read them. Both are inside the European Economic Area.

The YouTube video plays in YouTube’s own embedded player, which loads directly from Google as soon as you open an episode and is governed by Google’s privacy policy.

Everything else happens only after you press Start SeeWith. Opening an episode sends nothing to any of these:

• Supadata — the video’s id, to fetch its transcript.
• OpenAI — a short window of transcript around your current position, to detect the topic being discussed.
• Tavily, Wikipedia and Open Library — search terms derived from the detected topic, to find sources and images.
• Wikidata — the same search terms, to identify the people, places and works a topic names.
• Parallel (Parallel Web Systems Inc.) — For most detected topics, SeeWith sends Parallel one short search phrase derived from that topic — it can be a person’s name — to find web sources. The request comes from SeeWith’s server, not from your browser, and does not include your name, email address, account identifier, IP address, watch history or the transcript. The links, titles and short excerpts Parallel returns are shown only to you and kept with the rest of your episode state; SeeWith may reuse them for up to ten minutes to answer the same request from your account again, and never shows them to another SeeWith user. SeeWith uses Parallel for your account only after you accept SeeWith’s Search results terms.

These requests come from SeeWith’s server, not your browser, and do not include your name, email address, account identifier or IP address. Search terms and transcript windows can name people who appear in, or are discussed in, the video.

Parallel processes these requests in the United States, under the EU Standard Contractual Clauses in Parallel’s data processing agreement with SeeWith. Parallel’s terms with SeeWith allow it to use them to train and improve the models behind its services. Deleting your SeeWith account does not reach anything Parallel keeps under its own terms, which are described in Parallel’s privacy policy at parallel.ai/privacy-policy.

Images shown on context cards are fetched through SeeWith’s own proxy, so those image hosts do not see you.

SeeWith sets only the cookies it needs to work: a sign-in session cookie, and a short-lived encrypted cookie during Google sign-in. It sets no analytics or advertising cookies.Your browser’s local database keeps a copy of your episodes so the app keeps working when the connection drops; clearing site data removes it. YouTube’s embedded player, which loads from Google when you open an episode, sets its own cookies under Google’s privacy policy.

• Account, watch history, episode state and saved topics — until you ask for deletion.
• Usage counters — 90 days.
• Subscription records — while the subscription runs and three years after it ends, then deleted.
• Encrypted backups — until they rotate out, normally about two weeks.

• SeeWith does not sell your data, and does not share it for advertising.
• It does not use your data to build a profile of you across other sites.
• It sends you no marketing email. It sends no automated email; it writes to you only in answer to a request of yours.

You have the right to access your personal data, to have it corrected or erased, to restrict its processing, to receive it in a portable form, and to object to processing based on legitimate interests (GDPR Articles 15–18, 20 and 21), and not to be subject to a decision based solely on automated processing that significantly affects you, except as the law allows (Article 22). To use any of them, write to support@seewith.io from the address on your account, or by post to the address above. We answer within one month; if a request is complex we may extend that by up to two further months, and will tell you why within the first month.

You can also complain to the Croatian data protection authority: Agencija za zaštitu osobnih podataka (AZOP), Ulica Metela Ožegovića 16, 10000 Zagreb, azop@azop.hr.

Objecting to the usage-counter link. SeeWith can erase your account from every usage record it already holds; the counters remain, naming nobody. There is no per-account switch that stops the link being made again the next time you press Start; to stop it for good, ask for your account to be deleted.

To have your account deleted, write to support@seewith.io from the address on your account, or by post to the address above. There is no self-serve delete button; deletion is done by hand, in this order: any subscription is cancelled with Lemon Squeezy; your account and everything linked to it is deleted from the live database; subscription records are kept, with the link to your account removed, for the period above — they still carry Lemon Squeezy’s customer and subscription references, so they are not anonymous. Four caveats:

• Public video metadata remains; it names no one.
• Usage counters remain with your account erased from them, and are still deleted at 90 days.
• Encrypted backups are not rewritten. They hold your data until they rotate out, normally about two weeks; they are used only for disaster recovery and never to restore a deleted account.
• Anything kept in your own browser can be removed only by clearing site data for this site.

We will post changes to this page here.