Privacy Policy
Last updated: 15 July 2026
This Privacy Policy explains how Vergil AI Hungary Kft. ("Vergil", "we", "us" or "our") collects, uses, discloses and protects personal data in connection with:
- our public website at https://vergilai.com (the Site);
- our learning platform at https://www.vergillearn.com (the Platform); and
- related accounts, subscriptions, payments, customer relationships, support and security operations.
The Site and Platform are referred to together as the Services.
This Privacy Policy is a transparency notice. It is not a request for consent to all processing. We rely on the legal basis appropriate to each activity, as described below. When you create an account, you must confirm that you are at least 18 years old and agree to our Terms of Service.
Table of Contents
- Who We Are
- When Vergil Is a Controller and When It Is a Processor
- Personal Data We Process
- Purposes and Legal Bases
- Authentication and Access Control
- AI-Enabled Functions and Learning Analytics
- Cookies and Similar Technologies
- How We Share Personal Data
- International Data Transfers
- Data Retention
- Security
- Your Data-Protection Rights
- Age Restriction
- Information You Must Provide
- Third-Party Websites and Services
- Changes to This Privacy Policy
- Contact and Complaints
1. Who We Are
Vergil AI Hungary Kft.
Registered office: 1037 Budapest, Erdőalja köz 6., Hungary
Company registration number: 01-09-436058
VAT number: HU32662083
Email: info@vergilai.com
Telephone: +36 20 997 7655
For the processing activities in which Vergil determines why and how personal data is used, Vergil is the controller.
2. When Vergil Is a Controller and When It Is a Processor
Vergil may have different data-protection roles for different activities. The role depends on who determines the purposes and essential means of the relevant processing.
2.1 When Vergil acts as controller
Vergil generally acts as controller when it processes personal data for its own purposes, including when it:
- operates and secures the Site and Platform;
- provides an account or subscription directly to an individual user;
- manages customer, supplier and business-contact relationships;
- administers subscriptions, payments, invoices and accounting records;
- responds to support, privacy and other requests;
- prevents misuse, investigates incidents and maintains security audit trails;
- complies with legal obligations or establishes, exercises or defends legal claims; or
- manages its own corporate transactions and operations.
Where an individual purchases and uses the Platform directly, Vergil is generally the controller of that individual's account, learning activity, assessment results and Platform Content.
2.2 When Vergil acts as processor
Where a company, school, training provider or other organisation (an Organisation) provides the Platform to its personnel or other authorised users, the Organisation generally determines why those users' personal data is processed and acts as controller. Vergil then processes that personal data on the Organisation's behalf, under a data processing agreement and the Organisation's documented instructions.
In this situation:
- the Organisation is responsible for choosing a lawful basis and giving its users the information required by data-protection law;
- Vergil does not use Organisation-controlled personal data for its own unrelated purposes;
- Vergil assists the Organisation with data-subject requests and other applicable GDPR obligations; and
- users should normally direct requests relating to Organisation-controlled data to the Organisation. If Vergil receives such a request, we may forward it to the Organisation and assist it in responding.
Vergil remains a controller for its own business-contact, billing, account-security and legal-compliance activities, even where it otherwise acts as processor for Platform data.
2.3 Organisation administrators
Organisation administrators may create or invite users, assign roles and courses, manage permissions, and view information made available to their role. Depending on the Platform configuration, this can include course progress, completion information, certificates, assessment results, competency measurements and learning analytics.
Organisation administrators decide how information available to them is used within their Organisation. Vergil does not control independent decisions that an Organisation makes on the basis of Platform information.
3. Personal Data We Process
The categories below describe the personal data that may be processed depending on how you interact with the Services.
3.1 Account, identity and profile data
This may include:
- name and display name;
- email address;
- Organisation or workspace membership;
- role, permissions and administrative status;
- internal user, account and Organisation identifiers;
- account settings and language preference;
- account-creation, activation, suspension and closure information; and
- authentication and account-security information required for email-and-password sign-in, Google Sign-In or enterprise single sign-on.
3.2 Enterprise identity and access data
Where an Organisation uses Microsoft Entra ID, Vergil may receive identity claims and access-control information from the Organisation's Entra tenant, such as:
- name and work email address;
- tenant, subject or user identifiers;
- Organisation, domain, group or application-role information where configured for role mapping;
- signed authentication assertions and related validation information;
- session, token and revocation information; and
- provisioning and account-status information.
Vergil does not receive or store enterprise users' Microsoft passwords. Password policies, multifactor authentication, passwordless sign-in, Conditional Access, device-compliance rules and account-lifecycle policies remain controlled by the Organisation through Microsoft Entra ID.
3.3 Google Sign-In data
When you choose Google Sign-In, Google authenticates you. Vergil receives the identity information needed to create or access your Vergil account, such as your name, email address and a unique Google account identifier, according to the sign-in permissions configured for the Platform. Vergil does not receive your Google password.
3.4 Platform Content
Platform Content may include:
- source documents and other materials uploaded to the Platform;
- course-generation instructions and settings;
- generated courses, lessons and assessments;
- generated narration scripts and audio;
- messages submitted to the Ziggy AI assistant and Ziggy's responses;
- course configuration and assignment information; and
- other text, files or materials created, uploaded or saved through the Platform.
Platform Content is stored in Vergil's file-storage and Platform systems and is associated with the relevant Organisation or workspace. It is not necessarily associated only with the individual account that uploaded or generated it. Access is controlled by Organisation membership, roles and permissions.
Platform Content can contain personal data if a user includes it. Users and Organisations should not include personal data unless it is necessary, lawful and appropriate for the intended purpose.
3.5 Learning, assessment and usage data
This may include:
- course enrolment and access information;
- progress, completion and certificate information;
- responses to assessments and exercises;
- assessment, competency-measurement and gap-analysis results;
- learning recommendations and forward-looking learning analytics;
- feature activation and Platform-use information;
- a pseudonymous learner identifier; and
- the content and context of learner interactions with Platform features.
Vergil separates direct identifying information from relevant learning and assessment data and uses a pseudonymous learner identifier for statistical learning calculations. Pseudonymised data remains personal data and continues to receive GDPR protection.
3.6 Payment, subscription and billing data
Vergil uses Stripe-hosted Checkout and the Stripe Billing Portal for card payments and subscription management.
Stripe collects payment-card information directly on Stripe-hosted pages. Vergil does not collect or store payment-card details, such as the full card number, expiry date or security code.
Vergil may receive and retain information needed to administer the transaction and subscription, such as:
- purchaser and billing contact details;
- Organisation or company name and tax or VAT information where applicable;
- subscription plan and billing cycle;
- amount, currency, payment status and transaction date;
- invoice, refund, dispute and cancellation information; and
- Stripe customer, subscription, payment or transaction reference identifiers.
Stripe may separately process payment, device, fraud-prevention and regulatory information under its own privacy documentation.
3.7 Technical, device and security data
When you access the Site or Platform, our systems may process technical and security information such as:
- IP address;
- browser type and version;
- operating system and device information;
- requested pages, endpoints and files;
- request, response and error information;
- date, time and duration of activity;
- request identifiers and operational context;
- successful and failed sign-ins;
- session creation, sign-out and revocation;
- token issuance, expiry, rejection and re-authentication events;
- role and permission changes;
- identity-provider configuration changes;
- secret creation, rotation and access attempts;
- automated-abuse, spam and fraud-prevention signals and resulting risk scores; and
- denied authorisation attempts and other security-relevant events.
We use this information to operate the Services, enforce permissions, diagnose faults, detect misuse and investigate security events.
When you use the contact or waitlist form, Google Cloud reCAPTCHA analyses technical, device and interaction signals and returns a verification token and risk score so that Vergil can distinguish likely legitimate submissions from automated abuse. Vergil's server-side verification request contains the reCAPTCHA token and does not include the name, email address, category or message entered in the form.
If you consent to optional analytics on the Site, Google Analytics processes information about the page viewed, referring page, date and time, browser and device characteristics, approximate geographic area, language selection and selected Site interactions. The interactions we record include clicks on principal calls to action and whether a contact or waitlist submission succeeded. We do not send the name, email address, message, reCAPTCHA token or other form-field contents to Google Analytics. Google may process an IP address transiently to derive technical and approximate-location information, but Google Analytics does not make the individual IP address available to Vergil.
3.8 Communications and support data
If you contact us, we may process your name, contact details, Organisation, the content of your message, attachments, support history and any information needed to investigate and respond.
If you voluntarily join our temporary pre-launch waitlist, we process your name, email address, any optional message you provide, and a record of your consent. We use this information only to contact you manually with updates about Vergil's launch and availability. You may withdraw your consent at any time by emailing info@vergilai.com.
We do not otherwise send marketing newsletters. We may send account, billing, support, security and other service-related communications that are necessary to administer the Services.
3.9 Sources of personal data
We obtain personal data:
- directly from you;
- from an Organisation or its administrator when it creates, invites, provisions or manages your account;
- from Google when you use Google Sign-In;
- from Microsoft Entra ID when your Organisation uses enterprise single sign-on;
- from Stripe in connection with payments and subscriptions;
- from Google Cloud reCAPTCHA when it returns a form-submission verification result;
- from Google Analytics, if you consent to optional Site analytics;
- automatically through your use of the Site or Platform; and
- from another business contact where that person provides your details for a legitimate business purpose.
4. Purposes and Legal Bases
The table below describes the principal purposes and legal bases used when Vergil acts as controller. Where Vergil acts as processor, the relevant Organisation determines the legal basis for its processing and Vergil acts on the Organisation's instructions.
| Processing activity | Purpose | Legal basis when Vergil acts as controller |
|---|---|---|
| Visiting and using the Site | Deliver pages, maintain availability, troubleshoot errors and protect the Site | Our legitimate interests in operating a reliable and secure public website |
| Creating and administering a direct user account | Register you, authenticate you, provide the Platform and administer the account | Performance of a contract or steps taken at your request before entering a contract |
| Managing Organisation representatives and administrators | Administer the commercial and operational relationship, permissions and communications | Performance of a contract where the individual is a contracting party; otherwise our legitimate interests in managing the relationship with the Organisation |
| Email-and-password, Google or enterprise authentication | Verify identity, establish sessions, enforce access and prevent account misuse | Performance of a contract and our legitimate interests in protecting accounts and systems |
| Providing course generation, Ziggy, narration and other Platform functions | Deliver requested Platform features and store the resulting Platform Content | Performance of a contract; where Organisation-controlled, processing on the Organisation's instructions |
| Tracking learning and producing assessment or competency analytics | Provide progress tracking, certificates, assessments and learning analytics | Performance of a contract for direct users; where Organisation-controlled, processing on the Organisation's instructions |
| Payments, subscriptions, refunds and billing | Process purchases, manage subscriptions and keep financial records | Performance of a contract and compliance with tax, accounting and other legal obligations |
| Support and service communications | Respond to requests, resolve problems and provide operational, billing and security information | Performance of a contract and our legitimate interests in supporting users and Organisations |
| Temporary pre-launch waitlist | Record your interest and contact you manually with updates about Vergil's launch and availability | Your consent, which you may withdraw at any time |
| Contact and waitlist form protection | Detect and prevent automated submissions, spam, fraud and abuse using Google Cloud reCAPTCHA | Our legitimate interests in protecting Vergil, form users and the availability and integrity of the Site |
| Optional public-Site analytics | Understand aggregate Site use, page visits, language choices and the effectiveness of principal calls to action | Your consent, which you may withdraw at any time through Cookie settings in the Site footer |
| Security monitoring and audit logging | Prevent abuse, enforce least-privilege access, detect incidents, investigate events and maintain system integrity | Our legitimate interests in protecting users, Vergil and the Services; compliance with legal obligations where applicable |
| Legal and corporate administration | Comply with law, respond to authorities, manage disputes, and establish, exercise or defend legal claims | Compliance with legal obligations and our legitimate interests in protecting our legal rights |
| Remembering and serving the Platform language | Provide the correct server-rendered language and a consistent interface | Consent where required by rules governing storage on a user's device; otherwise our legitimate interests in providing the requested Platform interface |
Where we rely on legitimate interests, those interests include operating and securing the Services, preventing fraud and misuse, maintaining appropriate auditability, managing business relationships, protecting legal rights and improving service reliability. We consider the necessity and impact of the processing and do not rely on legitimate interests where the individual's rights and freedoms override our interests.
Where we rely on consent for a specific optional activity, you may withdraw that consent at any time without affecting processing that took place before withdrawal.
5. Authentication and Access Control
5.1 Email and password
Individual users may authenticate using an email address and password. Vergil processes the account and credential information needed to verify the sign-in, maintain the account, secure the authentication flow and support account recovery.
5.2 Google Sign-In
Users may choose Google Sign-In. The user is redirected to Google's authentication service, and Google verifies the user's credentials. After successful authentication, Vergil validates the identity response and creates or accesses the relevant Vergil account. Google's own processing is governed by Google's privacy documentation.
5.3 Microsoft Entra ID enterprise single sign-on
Vergil supports enterprise single sign-on using Microsoft Entra ID through standard federation protocols such as OpenID Connect and SAML 2.0.
When an enterprise user signs in:
- the user is redirected to the Organisation's Microsoft Entra ID tenant;
- Microsoft authenticates the user under the Organisation's security policies;
- Microsoft sends Vergil a signed identity response;
- Vergil validates the response, including its tenant, intended audience, validity and replay protections; and
- only after validation does Vergil establish a Platform session.
Authentication proves who the user is. It does not by itself grant broad Platform access. Vergil separately enforces Organisation membership, application roles, course access, school or workspace access, administrative privileges and data permissions.
Users may be pre-provisioned or created through controlled just-in-time provisioning. A newly provisioned user receives only the roles and scopes configured for the relevant Organisation, domain, Entra group or application assignment. If a user is disabled or removed in Entra ID, future authentication is blocked by the Organisation's identity system. Vergil can also revoke Platform sessions where immediate removal is required.
5.4 Sessions and permissions
Vergil uses short-lived access tokens and server-side session controls. Tokens and sessions are scoped to the user, Organisation, environment and permitted actions. Sessions can be revoked, sign-out invalidates the active session, and permission changes can cause stale tokens to be rejected.
6. AI-Enabled Functions and Learning Analytics
The Platform uses third-party AI services for specified functions. It does not send all Platform data to those services.
6.1 Course generation and narration scripts — Anthropic
For course generation, Vergil sends the source document and the instructions or context needed to generate the requested course to Anthropic. Relevant generated course content may also be sent to generate a narration script.
Vergil does not intend users to include personal data in source documents submitted for AI processing. If a source document contains personal data, that data may be processed by Anthropic to generate the requested output. Users and Organisations are responsible for ensuring that uploaded content is lawful, necessary and appropriately minimised.
6.2 Ziggy AI assistant — OpenAI
To generate a Ziggy response, Vergil sends OpenAI:
- the user's Ziggy message; and
- the relevant generated lesson content.
The payload does not contain the user's name, email address, Vergil account identifier, Microsoft or Google sign-in identifier, or pseudonymous learner identifier. OpenAI does not receive the Organisation's source documents through the Ziggy flow.
A user can nevertheless enter personal data directly into a free-text message. Users should not include personal data, confidential personal information or sensitive information in Ziggy messages unless it is strictly necessary and lawful.
6.3 Voice synthesis — Cartesia
For narrated presentations, Cartesia receives only the generated narration script needed to produce the audio.
6.4 No model training and zero-day provider retention
Under Vergil's production arrangements with Anthropic, OpenAI and Cartesia:
- submitted content is not used to train, develop or fine-tune their AI models; and
- the providers process submitted content using a zero-day retention configuration and do not retain it after completing the requested processing.
Vergil does not keep separate copies of prompts, responses, documents or provider payloads solely for AI-provider request logging. This does not mean that content is absent from the Platform: uploaded documents, generated courses, scripts, audio and other content that forms part of an Organisation or workspace may be stored by Vergil as Platform Content so that the requested feature and saved workspace remain available.
6.5 Learning analytics and pseudonymisation
Competency measurement, gap analysis, assessment calculations and forward-looking learning analytics are performed by Vergil's own statistical systems in Vergil's hosted environment. Learning and assessment data is not sent to Anthropic, OpenAI or Cartesia for those calculations.
Relevant calculations use a pseudonymous learner identifier rather than direct identifying details. Direct identifiers are stored separately from the learning and assessment records used by the statistical engine.
These analytics may constitute profiling because they evaluate aspects of learning activity and competency. The general logic is to use course interactions, responses, progress and assessment data to estimate competency, identify gaps and produce learning-related results or recommendations.
6.6 No solely automated significant decisions
Vergil does not use learning analytics to make decisions based solely on automated processing that produce legal effects or similarly significant effects for the user.
Organisation administrators may view results and decide how to use them within their Organisation. Any separate employment, education, access or performance decision made by an Organisation is the Organisation's responsibility as controller.
6.7 Sensitive and criminal-offence data
The Services are not designed for the processing of special-category personal data under Article 9 GDPR or criminal-conviction and offence data under Article 10 GDPR. Do not upload or enter data concerning health, biometrics used for identification, racial or ethnic origin, political opinions, religious or philosophical beliefs, trade-union membership, sex life, sexual orientation, or criminal allegations or convictions unless Vergil and the relevant controller have expressly agreed appropriate safeguards and there is a valid legal basis.
7. Cookies and Similar Technologies
7.1 Public Site security cookie
The contact and waitlist forms on the public Site use Google Cloud reCAPTCHA to detect and prevent automated abuse. When reCAPTCHA runs, it may set the following necessary security cookie on the reCAPTCHA provider's domain:
| Cookie | Provider and scope | Purpose | Value | Lifetime | Category |
|---|---|---|---|---|---|
_GRECAPTCHA | Google Cloud reCAPTCHA; third-party cookie on the reCAPTCHA service domain | Performs risk analysis and helps distinguish legitimate form submissions from automated abuse | Technical security identifier | Controlled by Google Cloud reCAPTCHA | Necessary security / fraud prevention |
Vergil does not use this cookie for advertising, remarketing or behavioural analytics. Blocking reCAPTCHA or its necessary cookie may prevent the contact or waitlist form from being submitted; you may instead contact Vergil directly at info@vergilai.com.
reCAPTCHA is used only for security, fraud prevention and abuse prevention.
7.2 Platform cookie
The Platform at www.vergillearn.com currently uses one first-party cookie:
| Cookie | Provider and scope | Purpose | Value | Lifetime | Category |
|---|---|---|---|---|---|
locale | Vergil; host-only on www.vergillearn.com; Path=/; SameSite=Lax | Selects the Platform language and ensures that server-rendered pages use the correct locale | en or hu | 1 year | Language preference / functionality |
The locale cookie is currently set automatically to en when the Platform is first used and may be updated if the user selects another supported language. It is client-readable and is not used for analytics, behavioural advertising, remarketing or cross-site tracking. It does not contain your name or email address.
If you delete or block the cookie, the Platform may revert to its default language and may not remember your language selection.
7.3 Optional analytics on the public Site
The Site at vergilai.com uses Google Analytics 4 only after you actively select Allow analytics. Before that choice, the Google Analytics script is not requested and Google Analytics cookies are not set by the Site. Declining analytics does not limit access to the Site or the contact and waitlist forms.
If you allow analytics, Google Analytics may set the following first-party cookies:
| Cookie | Provider and scope | Purpose | Value | Lifetime | Category |
|---|---|---|---|---|---|
_ga | Google Analytics; first-party on vergilai.com | Distinguishes browsers for Site usage measurement | Random client identifier | Up to 2 years | Optional analytics |
_ga_<container-id> | Google Analytics; first-party on vergilai.com | Maintains session and campaign state for this Google Analytics property | Random analytics and session identifiers | Up to 2 years | Optional analytics |
The Site stores your analytics choice in browser local storage under vergil.analytics-consent.v1. This necessary preference contains only granted or denied, is not sent to Google Analytics and remains until you change the choice or clear the Site's storage.
You can change or withdraw your choice at any time through Cookie settings in the Site footer. When you disable analytics, the Site instructs Google Analytics to stop collection and attempts to delete its first-party analytics cookies. You may also remove cookies through your browser settings. Withdrawal does not affect processing that took place before withdrawal.
Google Signals, advertising storage, advertising personalisation and remarketing are disabled in our implementation. We use Google Analytics only on the public Site, not on the Platform at www.vergillearn.com. We do not send form-field contents to Google Analytics.
When you choose Google Sign-In, Stripe Checkout or the Stripe Billing Portal, you may be redirected to a page operated by that provider. Those providers may use cookies or similar technologies on their own domains under their own privacy and cookie information. Except for the embedded reCAPTCHA service described above, those provider-domain technologies are not cookies set through the Site or Platform.
8. How We Share Personal Data
We disclose personal data only where necessary for the purposes described in this Privacy Policy, where instructed by an Organisation, or where required or permitted by law.
8.1 Organisations, administrators and authorised users
Where your account belongs to an Organisation, authorised Organisation administrators and users may access personal data and Platform Content according to their roles and permissions. This may include account details, course assignments, progress, completion, certificates, assessment results and learning analytics.
Platform Content is not public by default. Its visibility is determined by the relevant Organisation or workspace configuration and Vergil's role-based access controls.
8.2 Hosting and service sub-processors
Vergil uses carefully selected providers to host and operate the Platform and specified AI functions. These currently include:
- Hetzner Online GmbH for Platform hosting, infrastructure and object storage in Germany;
- Google Cloud for reCAPTCHA security, fraud prevention and automated-abuse detection on the Site's contact and waitlist forms;
- Google Analytics for optional public-Site usage measurement after the visitor's consent;
- Anthropic PBC for course generation and narration-script generation;
- OpenAI for Ziggy responses; and
- Cartesia, Inc. for voice synthesis.
Where these providers process personal data on Vergil's behalf, they are bound by appropriate data-processing terms. A current list, including processing locations and transfer safeguards, is maintained on our published Sub-processors page.
8.3 Identity providers
Where you select or are assigned an external identity provider:
- Google authenticates users who choose Google Sign-In; and
- Microsoft Entra ID authenticates enterprise users through the Organisation's tenant.
The identity provider processes information under its own terms and privacy documentation. In the enterprise Entra context, Microsoft is generally selected and controlled by the Organisation for its identity-management service rather than engaged by Vergil as a sub-processor for the Organisation's authentication directory.
8.4 Stripe
Stripe processes payment information through Stripe-hosted Checkout and the Stripe Billing Portal. Stripe provides Vergil with the transaction and subscription information needed to administer the purchase. Stripe may also process information for its own fraud-prevention, security, regulatory and financial-services purposes as explained in Stripe's privacy documentation.
8.5 Professional advisers and authorities
We may disclose personal data to lawyers, accountants, auditors, insurers and other professional advisers where necessary for professional services, legal compliance or the protection of rights.
We may disclose personal data to courts, regulators, supervisory authorities, law-enforcement bodies or other public authorities where required by law or necessary to establish, exercise or defend legal claims.
8.6 Corporate transactions
If Vergil is involved in a merger, financing, reorganisation, acquisition, sale of assets or similar corporate transaction, personal data may be disclosed to relevant advisers, counterparties and successors subject to appropriate confidentiality and data-protection safeguards.
8.7 No sale or behavioural advertising
Vergil does not sell personal data and does not share personal data for targeted or behavioural advertising. We do not use Platform data to send marketing newsletters. Temporary waitlist updates use only the contact information that a person submits directly through the waitlist form with consent.
9. International Data Transfers
Vergil's core Platform hosting and object storage are located in Germany within the European Economic Area (EEA).
Some providers are established in, or may process data from, countries outside the EEA, including the United States. This can include the AI providers described above and, depending on the service and user choice, payment or identity providers such as Stripe and Google.
For the AI functions:
- Vergil minimises the submitted data and excludes direct user identifiers from the Ziggy payload;
- learning and assessment data is not sent to the third-party AI providers;
- the providers use zero-day retention;
- the submitted content is not used for model training; and
- where personal data is transferred, Vergil uses data-processing agreements incorporating the European Commission's Standard Contractual Clauses and appropriate supplementary measures.
For other non-EEA transfers, Vergil uses a transfer mechanism recognised under Chapter V GDPR, such as an adequacy decision or the European Commission's Standard Contractual Clauses, together with supplementary measures where appropriate.
Google Cloud reCAPTCHA may process technical and security data through Google Cloud infrastructure outside the EEA. Google processes reCAPTCHA customer data on Vergil's documented instructions under the Google Cloud Data Processing Addendum, with the European Commission's Standard Contractual Clauses used where applicable.
If you consent to Google Analytics, analytics data may be processed through Google's infrastructure outside the EEA. Vergil uses Google's applicable data-processing terms and recognised transfer safeguards, including the European Commission's Standard Contractual Clauses where required. Optional analytics remains disabled unless and until you consent.
You may contact us for further information about the safeguards used for a particular transfer and, where applicable, to request a copy of the relevant safeguards. We may redact confidential or commercially sensitive information where permitted by law.
10. Data Retention
We retain personal data only for as long as necessary for the purpose for which it was collected, to follow an Organisation's lawful instructions, and to meet legal, accounting, security and dispute-resolution requirements.
The following rules currently apply:
| Data category | Retention approach |
|---|---|
_GRECAPTCHA cookie | Retained for the provider-controlled period necessary to perform reCAPTCHA risk analysis, unless deleted earlier through browser settings |
locale cookie | 1 year from the time it is set or refreshed, unless deleted earlier through browser settings |
| Google Analytics cookies | Up to 2 years unless analytics consent is withdrawn or the cookies are deleted earlier |
| Google Analytics event-level data | Configured for 14 months; aggregated reporting that no longer identifies a browser may be retained for longer |
| Analytics consent preference | Until you change the choice or clear the Site's local storage |
| Direct individual account data | While the account is active and then deleted or irreversibly de-identified within 30 days after account closure, except where law requires or permits longer retention |
| Organisation-managed user data | For the duration instructed by the Organisation and the applicable service relationship; generally deleted or returned within 30 days after the Organisation's service ends or after any requested return of data, unless law requires longer retention |
| Platform Content associated with an Organisation or workspace | While the Organisation or workspace remains active and then deleted within 30 days after closure or termination, subject to any lawful return process and legal-retention exception |
| AI-provider copies | Zero-day retention under the production configurations used for Anthropic, OpenAI and Cartesia |
| Payment, invoice and accounting information | For the period required by applicable tax, accounting and financial-record laws |
| Temporary waitlist data | Until the final launch or availability update is sent or consent is withdrawn, then removed from the active waitlist within 30 days; a minimal record of consent or withdrawal may be retained where necessary to demonstrate compliance or handle claims |
| Support and business correspondence | For as long as needed to resolve the matter, maintain an appropriate business record, comply with law and handle possible claims |
| Authentication, security and audit records | For as long as reasonably necessary to secure the Services, investigate events, demonstrate access-control changes, comply with law and establish or defend claims |
| Backups | Protected and removed or rendered unavailable through Vergil's ordinary backup-expiry and deletion processes, subject to security, disaster-recovery and legal requirements |
Closing or deactivating one user's Organisation-managed account does not automatically delete Platform Content owned by or associated with the Organisation. The Organisation may need to retain course content, completion records or other information under its own lawful purposes. Vergil will follow the Organisation's instructions where it acts as processor.
Where retention is required only for legal compliance or claims, access is restricted and the data is not used for unrelated purposes.
We may retain information that has been irreversibly anonymised so that it can no longer identify, relate to or single out an individual. Pseudonymised data is not anonymous and remains subject to the retention rules above.
11. Security
Vergil uses technical and organisational measures designed to protect personal data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access. Depending on the relevant system and risk, these measures include:
- TLS/HTTPS encryption in transit;
- encryption of uploaded files at rest using managed encryption keys;
- separation of direct identifiers from pseudonymous learning and assessment data;
- tenant-level database and workspace separation;
- role-based access control and least-privilege permissions;
- multifactor authentication for infrastructure-level administrative access;
- short-lived tokens, server-side session controls and session revocation;
- versioned permission changes that allow stale access tokens to be rejected;
- encrypted storage of identity-provider credentials in a dedicated secrets vault;
- separation of plaintext secret access from ordinary application data paths;
- logging and auditability of security-relevant authentication, authorisation, configuration and secret-management events;
- automated backups stored separately from the production environment and periodic restoration testing;
- network and application-security controls;
- monitoring of known software vulnerabilities and regular security updates; and
- staff confidentiality obligations and data-protection awareness measures.
No online service can guarantee absolute security. Users must keep account credentials confidential, use secure devices and promptly notify Vergil or their Organisation of suspected unauthorised access.
12. Your Data-Protection Rights
Subject to the conditions and limits in applicable law, you may have the right to:
- access your personal data and receive information about its processing;
- rectify inaccurate or incomplete personal data;
- erase personal data in applicable circumstances;
- restrict processing in applicable circumstances;
- receive and transmit certain personal data in a structured, commonly used and machine-readable format where the right to data portability applies;
- object to processing based on legitimate interests, including profiling based on those interests;
- object at any time to processing for direct marketing, including temporary waitlist launch updates;
- withdraw consent where processing is based on consent, without affecting earlier lawful processing;
- obtain information about applicable safeguards for international transfers; and
- lodge a complaint with a competent supervisory authority or seek a judicial remedy.
Vergil does not make decisions about users based solely on automated processing that produce legal or similarly significant effects.
12.1 How to exercise your rights
To exercise a right relating to processing for which Vergil is controller, contact info@vergilai.com. We may ask for information reasonably necessary to verify your identity and locate the relevant records.
We generally respond without undue delay and within one month. Where permitted by law, this period may be extended by up to two further months for complex or numerous requests, in which case we will explain the extension.
Rights are not absolute. For example, we may need to retain information to comply with law, protect the rights of others or establish, exercise or defend legal claims.
12.2 Requests concerning Organisation-controlled data
If your account is provided by an Organisation, the Organisation is generally the controller for your Platform learning and assessment data. You should normally submit the request to the Organisation. Vergil will assist the Organisation and, where appropriate, forward requests received directly by Vergil.
13. Age Restriction
The Services are intended only for people who are 18 years of age or older. Persons under 18 are not permitted to register for or use the Services.
When creating an account, a user must confirm that they are at least 18 and agree to the Terms of Service. Vergil does not offer a parental-consent registration route for minors.
If we learn that a person under 18 has created or used an account, we may suspend or close the account and delete the associated personal data within 30 days, except to the extent that retention is required by law, needed to investigate misuse or necessary to protect legal rights. Please contact us if you believe a person under 18 is using the Services.
14. Information You Must Provide
Certain information is necessary to create an account, authenticate you, provide the Services, administer a subscription or comply with law.
- Without the required account and authentication information, we cannot create or secure an account.
- Without required billing information, Stripe and Vergil cannot complete or administer a paid subscription.
- Some Platform functions require source content, instructions or responses. You choose what content to provide, but the requested function may not work without it.
- Where an Organisation provides your account, the Organisation determines which information it requires and is responsible for explaining the consequences of not providing it.
Please provide accurate information and avoid submitting personal data that is not necessary for the relevant purpose.
15. Third-Party Websites and Services
The Services may link or redirect to third-party websites and services, including Google, Microsoft and Stripe. Those third parties control their own websites and may process personal data for their own purposes. Their privacy practices are governed by their own notices, not this Privacy Policy, except to the extent that they process data on Vergil's documented instructions as a processor or sub-processor. Relevant notices include the Google Privacy Policy, the Microsoft Privacy Statement and the Stripe Privacy Policy.
For Google Cloud reCAPTCHA, Google acts as Vergil's processor for the security, fraud-prevention and abuse-prevention purposes described in this Privacy Policy and the applicable Google Cloud data-processing terms govern that processing.
Where you consent to Google Analytics on the Site, Google processes the analytics information described in this Policy under the applicable Google Analytics terms and data-processing terms. The Google Analytics privacy information explains how Google handles data collected through Google Analytics.
16. Changes to This Privacy Policy
We may update this Privacy Policy to reflect changes in the Services, providers, processing activities or applicable law. We will update the date at the top of the Policy.
Where a change is material, we will provide an appropriate notice, such as through the Site, Platform, account interface or email. Where a new activity requires consent, we will request consent rather than treating continued use as consent.
17. Contact and Complaints
Questions, requests and complaints may be sent to:
Vergil AI Hungary Kft.
1037 Budapest, Erdőalja köz 6., Hungary
Email: info@vergilai.com
Telephone: +36 20 997 7655