Syllonaut BETA
Privacy

Privacy and personal data (GDPR)

This page explains which personal data Syllonaut processes, why it is needed, how long it is retained and what rights you have.

Version 1.24 · effective from 5 November 2026

1. Data controller

Václav Loubek
Business ID: 88878431
Slepá 868
289 24 Milovice – Mladá
Czech Republic

The controller operates Syllonaut at syllonaut.com. For privacy-related questions, contact vaclav@syllonaut.com or by phone at +420 733 377 199.

2. Data we process

  • Teacher account: email address, technical account identifier, entitlement data and AI usage-limit data.
  • Lessons and teacher work: briefs, generated lessons, edits, folder names and other saved content.
  • Lesson source materials: text extracted in the browser. The original file does not leave the device and the extracted text is not permanently stored by Syllonaut.
  • Syllonaut Help: the text of your question and of the earlier messages in the open Help panel, your plan and allowance usage, and the name of the app page you ask from. We do not store the conversation text. For each message we record only the time, the app page (without a lesson or live-lesson identifier), the question topic, the processing status, the AI cost and your rating of the answer, if you give one.
  • Live lessons: student display name, responses, team assignment, results, submission times and related operational data; if the teacher turns on anonymous messages in a lesson, also students’ messages to the teacher and the teacher’s answers; in lessons with teams, also team chat messages.
  • Security and operations: technical data needed for sign-in, abuse prevention, error diagnostics and security, and for a teacher’s sign-in session also the IP address and browser identification (user agent). Server error logs contain only technical identifiers and a short description of the error, not lesson content, student responses or email addresses. When you sign up or set a new password, we check whether the password has appeared in known data breaches using the Pwned Passwords service (Have I Been Pwned): only the first 5 characters of the password’s fingerprint (SHA-1) are sent; neither the password itself nor your email leaves our servers.
  • Terms acceptance: technical account identifier, Terms version / acceptance key and server acceptance time. The audit record does not duplicate the email address or another direct identifier.
  • Acknowledgement of the Free single live use notice: when you close the Free plan notice that each lesson can be used live once (with “OK, got it” or the close button), we record the technical account identifier, the lesson where you closed it, the version and exact text of the notice, the language, how it was closed and the server time. The email address or another direct identifier is not duplicated in the record.
  • Attempts to start an already used lesson on the Free plan: when on the Free plan you open a lesson that can no longer be started live again, or the server refuses such a start, we record the technical account identifier, the lesson, the kind of event and the server time (opening the same lesson at most once every 30 minutes).
  • Organisation DPA acceptance: for Team / School / Campus orders we record the active DPA version / acceptance key, server acceptance time and the technical account identifier of the person who accepted the DPA on behalf of the organisation.
  • Paid individual contract evidence: technical account identifier, plan, billing period, price and currency, Terms version / acceptance key, document language, the express request for immediate start of service, an immutable HTML snapshot of the contract information and model withdrawal form, integrity hash, server timestamp and technical Stripe Checkout link. The email address is not duplicated in this archived snapshot.
  • Subscription payments and billing: you enter the payment directly with Stripe, which processes your name, email, billing address and payment details. Syllonaut stores the Stripe customer and subscription identifiers, billing country, plan, billing period, subscription status, payment amounts and currency, refunds and any disputes. The card number never reaches us.
  • School licences (Team / School / Campus): the organisation’s name and registered name, company ID, VAT ID, billing email, billing address and country, orders, issued invoices and received payments; for card payments Stripe also processes the payer’s name and address.
  • Organisation invitations: the invited person’s email address, role, invitation language, who sent the invitation, its status and times. The invitation link is stored only as a one-way hash.
  • Bank transfer payments for school licences: the bank’s notification of a payment received to Syllonaut’s account, which may contain the payer’s name and account number, the amount, the payment reference and a message to the recipient. From the notification we store only the payment reference (variable symbol), amount, currency, transaction reference and time of receipt, to match the payment to the order automatically.
  • Online contract withdrawal: consumer name, electronic contact for confirmation, contract-snapshot identifier, plan and period, exact submission content, server date and time, integrity hash, confirmation-email delivery status and technical identifiers of the related refund process.
  • Marketing email consent: whether you opted in to news, case studies and offers, the consent date and the version of the consent text.
  • Contact form: the email address and message you submit. To protect the form, we temporarily retain only pseudonymised hashes of technical identifiers for rate limiting, not their readable form.
  • Referral program: if you sign up through another teacher’s link or code, we record the link between your account and the referring teacher’s account, a one-way hash of a random device identifier (the same one we already use for trusted devices and Free plan limits) and the referral status (pending, rewarded, capped, rejected, expired). To check the conditions we use data we already process: email verification, the number of participants who submitted an answer in an ended lesson and the subscription status. The referring teacher never sees your name or email address, only numbers. For the referring account we record its referral code and the bonus lessons credited. The program adds no new cookie or browser storage.
  • Analytics: only after consent, Google Analytics 4 may process website visit and usage data within the configured GA4 scope.

3. Purposes and legal bases

PurposeLegal basis
Registration, sign-in, lesson storage and provision of service featuresPerformance of a contract or steps taken at the user’s request before entering into a contract (Art. 6(1)(b) GDPR)
Recording acceptance of the Terms, paid-contract content and protecting legal claimsPerformance of the contract and legitimate interest in evidencing the formation and content of the contractual relationship and in establishing, exercising or defending legal claims (Art. 6(1)(b) and (f) GDPR)
Recording that you were informed about the single live use of a lesson on the Free plan and protecting legal claims (for example in a complaint)Legitimate interest in evidencing the information provided and in establishing, exercising or defending legal claims (Art. 6(1)(f) GDPR)
Assessing how often Free teachers reach the single live use of a lesson and improving the plan offerLegitimate interest in improving the service and the offer (Art. 6(1)(f) GDPR)
Referral program: crediting the reward to the referring teacher and protecting the program against misuse (for example the same device, the same email address or a disposable email address)Legitimate interest in the fair operation of the referral program and in protecting it against misuse (Art. 6(1)(f) GDPR)
Receiving a withdrawal, confirming it to the consumer, terminating the contract and settling paymentPerformance of the contract, compliance with consumer-protection legal obligations and legitimate interest in evidencing the settlement process (Art. 6(1)(b), (c) and (f) GDPR)
Recording an organisation’s acceptance of the Data Processing Agreement (DPA)Performance of the contract and legitimate interest in evidencing the binding controller–processor arrangement under Art. 28 GDPR and protecting legal claims (Art. 6(1)(b) and (f) GDPR)
Syllonaut Help: AI answers to questions about using the app, plans and allowances, and recording its use for the monthly message limit and budgetPerformance of the contract (Art. 6(1)(b) GDPR); analysing topics and answer ratings to improve Help is based on legitimate interest (Art. 6(1)(f) GDPR)
Service security, abuse prevention and technical diagnosticsLegitimate interest in secure and reliable operation (Art. 6(1)(f) GDPR)
Payments, invoicing, matching bank transfer payments and bookkeepingPerformance of the contract and legal obligation under accounting and tax law (Art. 6(1)(b) and (c) GDPR)
Delivering an organisation invitation to the person entered by the organisation’s administratorPerformance of the contract with the organisation and legitimate interest in delivering the invitation and protecting it against misuse (Art. 6(1)(b) and (f) GDPR)
Compliance with legal obligationsLegal obligation (Art. 6(1)(c) GDPR)
Website analytics using GA4Consent (Art. 6(1)(a) GDPR); GA4 does not load without consent
News, case studies and promotional offers by emailVoluntary consent; registration is not conditional on this consent
Handling an enquiry submitted through the contact formSteps taken at the user’s request before entering into a contract where the enquiry concerns purchase or cooperation; otherwise legitimate interest in responding to an incoming enquiry

4. Marketing emails

During registration you can separately and voluntarily consent to receiving news, case studies and promotional offers. The checkbox is not preselected. Consent can be withdrawn at any time; every marketing email must provide a simple unsubscribe option. Withdrawing consent does not affect use of your account or operational emails related to the service.

If you have given consent, we send marketing emails based on how you use the service: your plan and plan changes, interface language, creating your first lesson, starting your first live lesson and use of your AI allowance. For this we share your email address, language, plan and the relevant event with our provider Resend. Without consent, or after you withdraw it, we do not send these events to Resend and you receive no marketing emails.

Loading your settings…

5. Cookies and Google Analytics 4

We use essential cookies and browser storage for sign-in, security, abuse prevention, language, taking part in a live lesson and storing your cookie choice. Analytics cookies are disabled by default, and refusing analytics does not restrict use of the service. On student pages (joining a lesson, the student lesson view and the classroom projection) we show no cookie banner and Google Analytics does not load.

TechnologyPurposeDuration
syllonaut_cookie_consent_v1Stores your cookie choice; essential.Up to 180 days.
Neon Auth (__Secure-neon-auth.session_token, __Secure-neon-auth.local.session_data)Teacher sign-in and secure session verification; essential. The second cookie is a short-lived signed copy of the session data.Until sign-out or session expiry; the session-data copy 5 minutes.
syllonaut_localeRemembers the chosen interface language; essential.1 year.
syllonaut_device_v1Random device identifier of a signed-in teacher for trusted-device limits and the free AI allowance per device; set only on sign-in or registration; essential.1 year.
ep_participant_<session>Links a student to their participation in a specific live lesson so they can submit responses; essential.Up to 24 hours from joining; the “Leave the lesson” button deletes it immediately.
syllonaut_live_resume_<session>The teacher’s fallback access to the live lesson they are running; used only during a brief outage of the sign-in service; HttpOnly; essential.Up to 10 hours; deleted on sign-out.
Browser storage: IndexedDB (syllonaut-live-v1)Offline queue of student responses, individual and team answer drafts and the latest live-lesson state so answers are not lost when the connection drops, the page is reloaded or the tab is closed; essential.24 hours: after that they are no longer used and are deleted on the next visit to any Syllonaut page; the “Leave the lesson” button deletes them immediately.
Browser storage: sessionStorage (syllonaut-live-control-v1:…, syllonaut-team-draft-v1:…, syllonaut-answer-draft-v1:…, syllonaut-teacher-message-panel-v1:…, syllonaut-team-chat-panel-v1:…, syllonaut_revision_highlight_v1:…, syllonaut_pending_share_import_v1)Access to real-time live-lesson control, individual and team answer drafts, whether the student opened or minimised the anonymous-message and team chat panels, highlighting of changes after an AI edit, a pending import of a shared lesson and one-off technical flags (e.g. that a notice was already shown); essential.Until the browser tab is closed or access expires; lesson and teacher-account data is also deleted when leaving the lesson and on sign-out.
Browser storage: localStorage (syllonaut_last_lesson_v1)A copy of the teacher’s most recently opened lesson so it can be restored after the browser crashes or closes; essential.Until sign-out or sign-in with another account.
Browser storage: localStorage (syllonaut_guide_v3:<account>)The state of the in-app guide (which steps you completed or closed); contains no lesson content; essential.Until the browser data is cleared.
Browser storage: localStorage (syllonaut-pending-email-verification-v1)The email address of a new account waiting to be confirmed with the emailed code, so the code form reopens even after the page is reloaded or closed; essential. It is stored only in your browser and deleted once the email is confirmed or you sign in.Up to 24 hours.
Cloudflare TurnstileAbuse protection only on the sign-in and registration forms; it loads only once those forms are opened and may use technical identifiers required for security.According to the security session and provider settings.
_ga, _ga_*Google Analytics 4 — measurement of traffic and service usage; only after consent.Approximately 13 months in Syllonaut’s configuration.

Google Analytics 4 loads only after active consent and only when measurement is configured in production. In this version, GA4 advertising signals and ad personalisation are disabled. If remarketing, Google Ads or other marketing tracking is added later, these notices will be updated and new consent will be requested where required.

You can change your choice at any time using the Cookie settings link in the footer. When analytics consent is withdrawn, Syllonaut blocks further measurement and attempts to remove existing GA cookies on the Syllonaut domain.

6. AI and uploaded source materials

AI processes text needed to create, edit or evaluate a lesson. Current AI paths enforce zero data retention at the Vercel AI Gateway level. For supported source materials, text extraction happens in the browser; the original file is not sent to the Syllonaut server and extracted text is not permanently stored as a file archive.

Syllonaut Help: When you ask Help a question, we send the question text, the earlier messages in the open panel and your plan and allowance usage through Vercel AI Gateway with zero data retention to the AI model provider, only so that it can write the answer. We do not store the conversation; it disappears when you close the panel or reload the page. Help has no access to your lessons, student responses or payments and changes nothing in your account. Do not enter student names or responses in Help.

Do not include personal data that is unnecessary for teaching in briefs or source materials, especially sensitive student data.

Automated decision-making: Syllonaut does not make decisions based solely on automated processing that produce legal effects for students or teachers or similarly significantly affect them (Art. 22 GDPR). Points suggested by AI for student responses are only a suggestion: they count toward the score and ranking only after the teacher confirms them, and the teacher always decides the final points. A notice that AI may have been used to write a response is only a signal for the teacher; it does not change points and is not proof. We provide this information under Art. 13(2)(f) GDPR.

7. Students and school use

A student does not need a full account to join a live lesson. They enter a display name and may submit responses during the lesson. Teachers should request only the student identifier needed for the specific lesson.

The student’s name and responses are visible to the teacher running the lesson. For open, team and exit-ticket responses, AI may suggest points and short feedback. The suggestion does not award points: it counts only after the teacher confirms it, and the teacher can change it. Syllonaut may notify the teacher that AI may have been used to write a response; the notice does not change points and the teacher decides what to do. Student pages show no cookie banner and do not load Google Analytics. On a shared computer a student can click “Leave the lesson”: the browser forgets their connection to the lesson and the lesson data stored in the browser; their responses stay with the teacher. Live-lesson data is deleted according to the school’s rules and the retention periods in section 9.

Anonymous messages to the teacher: if the teacher turns them on in a lesson, a student can send the teacher a message without their name. The teacher sees only the message text and the writer’s number in that lesson (e.g. “Anonymous 3”). Syllonaut records which connection a message came from only to deliver the answer and to apply limits against misuse (at most 3 messages per minute and 20 per lesson; the teacher can mute a writer); the app does not show this link to the teacher, the school or other students. The teacher can answer the writer only or the whole class: then every student in the lesson sees the message text and the answer, without a name or the writer’s number. Messages are not sent to AI or to the real-time live-lesson copy. Within one conversation the student and the teacher can react to messages with an emoji (e.g. 👍); only the two of them see the reactions, the teacher still only with the writer’s number, and they are deleted together with the message.

Team chat: in a lesson with teams, members of one team can write to each other during the lesson. A message and its writer’s name (the display name in the lesson) are visible only to members of the same team. The teacher, the school and other students have no access to the team chat; the teacher can only switch the chat off for the lesson. Syllonaut records which connection a message came from so it can show it to the team and apply limits against misuse (at most 5 messages per minute and 150 per lesson). Messages are not sent to AI or to the real-time live-lesson copy. Team members can react to messages with an emoji (e.g. 👍); only team members see who reacted, and reactions are deleted together with the message. Because nobody outside the team sees the content, nobody moderates it.

For Team / School / Campus plans, where the organisation determines the purposes and means of processing student or staff personal data and uses Syllonaut for that processing, the organisation is the controller and Syllonaut is the processor. This relationship is governed by a binding Data Processing Agreement (DPA), expressly accepted by an authorised representative when the organisation places the order. From Terms 1.11 the same DPA also applies to individual Free, Teacher and Teacher Pro accounts where the teacher uses Syllonaut to process students’ personal data in teaching; the controller is then the teacher, or the school for which they teach. For Syllonaut’s own purposes – in particular billing, accounting, security, fraud prevention and contract evidence – Syllonaut acts as an independent controller. Current DPA.

8. Service providers

  • Neon (Databricks, Inc.) — production database, sign-in (Neon Auth) and Data API; data is stored in the EU (AWS Frankfurt).
  • Vercel — application hosting and AI Gateway.
  • Cloudflare — Turnstile only on the sign-in and registration forms; Workers and Durable Objects for real-time control of live lessons (student name, lesson content, student and team responses); the Durable Objects run and store data only in the EU jurisdiction and the data is automatically deleted 7 days after the lesson’s last activity.
  • Stripe — payments and subscription management. CZK payments are processed by Stripe Payments Europe, Limited (Ireland); for EUR and USD payments the merchant of record is Sold through Link, LLC, part of the Stripe group. Stripe processes payment data on our behalf and, for its own purposes (fraud prevention, regulatory compliance), also as an independent controller.
  • Resend — transactional emails, marketing mailings based on granted consent, delivery of contact-form enquiries and receipt of bank notifications of transfer payments (Resend Inbound).
  • Zoho (Zoho Corporation B.V., the Netherlands) — mailboxes for the syllonaut.com domain: contact-form enquiries, emails you send us (e.g. questions, GDPR requests, withdrawals or complaints) and replies to our emails; data is stored in Zoho’s EU data centre.
  • AI model providers — through Vercel AI Gateway with zero data retention: OpenAI (OpenAI Ireland Limited) for creating and editing lessons, suggested evaluations of student responses and Syllonaut Help; Microsoft Azure or Amazon Web Services (Bedrock) only for creating a lesson from uploaded source materials. Always only to the extent needed for the specific AI operation.
  • Google — Google Analytics 4, only after analytics consent and never on student pages; also a Gmail mailbox and Google Apps Script, through which the bank’s notifications of transfer payments for school licences pass before we hand them to Resend for matching.

Where a provider transfers personal data outside the European Economic Area, appropriate GDPR transfer safeguards must be used.

The current list of sub-processors relevant to organisations and teachers, their purposes, data scope and change procedure is included in the Data Processing Agreement (DPA).

9. Retention periods

  • Account data and saved lessons are retained while the account is active or until deletion, unless a legal obligation requires longer retention. When an account is deleted, we delete the account data, the lessons and all live sessions including the students’ data; copies of shared lessons saved by other teachers stay with them.
  • Ended live sessions are scheduled for automatic deletion after 12 months.
  • Abandoned sessions left in lobby/live state are scheduled for automatic deletion after 30 days.
  • Anonymous messages to the teacher and the answers to them are deleted automatically 30 days after the lesson ends, or earlier together with the whole lesson.
  • Team chat messages are deleted automatically within one hour after the lesson ends at the latest, or earlier together with the whole lesson.
  • The real-time live-lesson copy (Cloudflare, EU jurisdiction) is deleted automatically one hour after the lesson ends, and at the latest 7 days after the lesson’s last activity.
  • Database history used to recover from an error or a security incident (Neon, EU) is kept for 7 days; data we delete disappears from it within 7 days at the latest.
  • Syllonaut Help usage records (without the conversation text) are retained while the account exists, because the monthly message limit and budget are calculated from them; they are deleted together with the account.
  • Referral program data (the link between the accounts, the device hash and the referral status) is kept while both accounts exist, at most 12 months after the referral closed (rejected, expired or capped); for a rewarded referral at most 12 months after the reward expired. The link is then deleted automatically; for a reward only a record that it was credited remains, without a link to the invited account, so that the reward limit can be applied. When either account is deleted, the link is deleted earlier; the referrer’s bonus lessons remain. The referral code is kept while the account exists.
  • Organisation invitations are deleted 30 days after they are accepted, revoked or expire, and immediately when the organisation or the invited person’s account is deleted.
  • Organisation billing data, orders and issued invoices are kept while the licence lasts and then for the period required for accounting and tax documents by accounting and tax law. When the organisation owner’s account is deleted, we remove their contact email from the organisation; issued invoices remain.
  • Bank notifications of transfer payments are kept in the mailbox and in Resend only as long as needed to match and check payments and for bookkeeping; the database keeps only the record of the matched payment (payment reference, amount, currency, transaction reference and time) as part of the order.
  • Sign-in session records (including the IP address and user agent) are managed by Neon Auth; they are deleted on sign-out, at the latest one hour after the session expires (a session expires after 7 days without use), and with the account.
  • Short-lived editing locks are cleared after 24 hours.
  • Cookie choices are retained for no more than 180 days.
  • A Terms acceptance audit record (account ID, version / acceptance key and server timestamp) is kept for 3 years after account deletion (the general limitation period) to evidence the contractual relationship and to establish, exercise or defend legal claims; it is then deleted automatically.
  • A record of acknowledging the Free single live use notice (account ID, lesson, notice version and text, language, how it was closed and server timestamp) is kept for 3 years after account deletion to handle complaints and to establish, exercise or defend legal claims; it is then deleted automatically.
  • Records of attempts to start an already used lesson on the Free plan are kept while the account exists; they are deleted together with the account or with the lesson concerned.
  • An organisation DPA acceptance record (version / acceptance key, server timestamp and accepting account ID) may be retained for as long as reasonably necessary to evidence the binding processing agreement and to establish, exercise or defend legal claims; it is then deleted or anonymised unless further retention is legally required.
  • An immutable paid individual contract snapshot (account ID, plan, price, billing period, accepted Terms version, immediate-start request, contract HTML document, model withdrawal form, integrity hash and technical checkout link) is kept for 3 years after account deletion to evidence the contract content, comply with legal obligations and establish, exercise or defend legal claims; it is then deleted automatically. The same applies to records of buying and using AI grading suggestion packs and to terminations because of a service change. Accounting records (invoices, payments, refunds) are kept by Stripe and in our accounts for the period required by accounting and tax law.
  • The immutable withdrawal record and related settlement (including the name and contact from the online form) are retained while the account exists and for 3 years after its deletion to evidence receipt and content of the submission, comply with consumer obligations and establish, exercise or defend legal claims; they are then deleted automatically.
  • For a complaint (name, contact email, account ID, complaint content, requested remedy, current plan, submission time and resolution record) we process data to fulfil the legal obligation to handle the complaint and confirm its receipt and resolution. The immutable record is retained while the account exists and for 3 years after its deletion to evidence the resolution and to establish, exercise or defend legal claims; it is then deleted automatically.
  • A record of handling an account deletion request (account ID, request and deletion dates, who carried it out and which follow-up steps were done; no email) is kept for 3 years to evidence that the request was fulfilled; it is then deleted automatically.
  • After withdrawal, a limited record of marketing consent may be retained where necessary to demonstrate that your choice and legal obligations were respected.
  • Contact-form messages are retained for the time needed to respond and handle related follow-up; if no contractual relationship or other reason for longer retention arises, we generally do not need the message for more than 12 months. Pseudonymised rate-limit records are continuously deleted after 30 days.

10. Your rights

Depending on the circumstances, you have rights of access, rectification, erasure, restriction, data portability and objection. You can withdraw consent to analytics or marketing emails at any time; withdrawal does not retrospectively affect the lawfulness of prior processing.

You also have the right to lodge a complaint with the Czech Office for Personal Data Protection. Current contact details are available on the authority website.

11. Changes to this notice

This page will be updated if processing practices, service providers or legal requirements change. If a material change requires new consent, consent will be requested again.