Prezuva
Product Pricing Resources
School login Sign in Get started →
Legal

Privacy Policy

How Prezuva collects, uses, shares, and protects personal data across the website, app, classroom tools, and related services.

Last updated: October 21, 2026

On this page

Who We Are Our Role in Your Data Data We Collect How We Use Data AI Processing Creator and Payout Data Billing and Payments Visiting Without an Account Legal Bases Sharing Integrations Zoom Age Verification International Transfers Classroom Access Shared Lesson Links Security Retention Your Rights Children and School Use Cookies Changes Contact

Who We Are

Prezuva Ltd, a company registered in the United Kingdom whose address is Unit A, 82 James Carter Road, Mildenhall IP28 7DE, provides education software for teachers, students, schools, and institutions. This policy explains how we collect, use, and protect personal data when you use prezuva.com, app.prezuva.com, and related services.

It covers the website, the app, the editor and studios, live teaching tools, courses and classrooms, the content library and Creator Studio, and the contributor revenue sharing programme.

Our Role in Your Data

For accounts that individuals create themselves, and for our own operation, security, and improvement of the platform, Prezuva Ltd acts as the controller of the personal data described in this policy.

Where a school, district, university, or other institution administers accounts, classes, courses, or student records, that institution is generally the controller of the educational data it and its users place into the platform, and Prezuva acts as a processor on its instructions under our agreement with it. In those cases, please direct requests about educational records to the institution first.

Data We Collect

  • Account data: name, email address, encrypted password, account type, onboarding preferences, purpose of use, and login sessions.
  • Teaching profile and preferences: the subjects you teach, your country, the education systems, curricula, and grade levels you select, and similar preferences you set during onboarding or in your settings.
  • Authentication and security data: email verification status, verification tokens, password reset tokens, Google sign-in identifiers where used, and security-related logs.
  • Facebook sign-in data: if you choose to continue with Facebook, we receive your Facebook user ID, name, and primary email address from Meta. We use them only to create or sign you in to your Prezuva account and to show your name in the app. We do not receive your password, friends list, posts, or any other Facebook data, and we never post to Facebook on your behalf. You can remove Prezuva from your Facebook settings at any time; this does not delete your Prezuva account, which you can delete separately.
  • Role and organisation data: account role and permissions, institution or school membership, group and class membership, administrator or contributor status, and access approvals.
  • Learning and workspace data: lessons, presentations, folders, courses, assignments, quizzes, submissions, grades, remarks, and related classroom configuration data.
  • Shared lesson links: when you share a lesson by link, a record of the link, the lesson it points to, when it was created, and whether you have revoked it. We store only a one-way hashed form of the link's secret token, not the token itself.
  • Live classroom data: class codes, attendee display names, teaching session state, poll/Q&A/draw/upload activity responses, and similar real-time session data.
  • User media and files: uploaded images, videos, PDFs, presentation files, embedded media references, thumbnails, file metadata, and storage usage.
  • AI feature data: the prompts, selected text, images, and lesson context you submit to AI features, the generated output, and records of AI generation requests, including their status and whether content was marked as AI-generated.
  • Creator Studio data: content you build and submit, its titles, descriptions, tags, subject and level metadata, submission and review status, reviewer decisions and notes, publication records, content removal requests, and usage and impact statistics for your published content.
  • Contributor application data: if you apply to become a contributor, the application you submit (email address, display name, biography, teaching experience, motivation, subjects, grade levels, languages, portfolio links, and sample materials), together with its review status, reviewer notes, the decision, and a history of each change of status.
  • Payout data: account holder name, country, currency, payout method, payment identifier such as a mobile banking or account reference, phone number, bank and branch details, routing references, verification status, earnings records, payout amounts, and payout batch history.
  • Subscription and usage data: plan, billing interval, subscription status and renewal dates, beta access and free trial status with their start and end dates, entitlements, feature allowances and remaining quota, metered usage events such as AI generations and translations, and storage consumption.
  • Payment and billing data: when you buy a paid plan, your name, email address, billing address, and, if you provide one, your business name and tax ID; payment and invoice records such as amounts, currency, tax charged, dates, and refunds; and limited card details passed back to us by Stripe, namely the card brand, last four digits, and expiry date. Your full card number and security code are collected directly by Stripe and never reach Prezuva.
  • Notification data: in-product notifications, their read state, and related delivery records.
  • Integration data: where you connect a video conferencing account or use another integration, the identifiers, tokens, and meeting or session details needed to operate it.
  • Zoom age-verification data: before an independent teacher connects Zoom for the first time, we process the date of birth and country or region they submit to determine age eligibility. We do not retain the date of birth after making that determination. We retain the eligibility result, country or region, verification method, applicable policy version, and verification time.
  • Technical data: device/browser details, IP address, approximate usage diagnostics, and events needed for security, abuse prevention, reliability, and troubleshooting.
  • Library search data: searches you run in the editor and content library, including the search terms, filters such as subject, category, and curriculum, the number of results returned, and the time of the search. Searches are linked to your account for 12 months, after which the link to you is removed, and they are deleted after 24 months.
  • Campaign link data: when anyone opens one of our campaign links, the campaign, the time, the referring page, the browser's user-agent string, and a salted one-way hash derived from the visitor's IP address and user agent, used to count unique visitors. The IP address itself is not stored with these records. See Visiting Without an Account.
  • Analytics data: page views, navigation events, device and browser type, approximate location derived from IP address, and similar measurements collected by Google Analytics on our website and in the app, only if you have agreed to analytics cookies, and never for school-managed accounts. See Cookies.
  • Cookie and local storage data: your sign-in session, your cookie choices, security cookies, product settings, and work in progress kept in your browser, such as editor recovery drafts and, for visitors without an account, work created in the editor.
  • Support and correspondence: messages you send us, including rights complaints and removal requests, and our replies.

How We Use Data

  • To provide authentication, dashboard, editor, classroom, course, assignment, quiz, and collaboration features.
  • To operate the studios and content library, including submission, review, categorisation, publication, versioning, and removal of contributed content.
  • To provide AI-assisted features such as text, question, diagram, image, and 3D generation, translation, and background removal.
  • To determine and enforce plan entitlements, feature allowances, storage quotas, and usage limits, and to show you your own usage history.
  • To calculate contributor impact and revenue sharing, to prepare and verify payout profiles, and to process and reconcile payouts.
  • To detect and investigate fraud, manipulation of usage or earnings, abuse, and other violations of our Terms.
  • To send transactional emails such as account verification, password reset, and account security messages.
  • To send service notifications about classes, courses, submissions, reviews, earnings, and billing.
  • To maintain platform security, prevent abuse, enforce access controls, and troubleshoot issues.
  • To store and deliver user-uploaded content and presentation assets.
  • To confirm that an independent teacher satisfies the minimum age requirement before allowing that account to authorize the Zoom integration, and to prevent student and underage accounts from accessing Zoom authorization.
  • To tailor library results, suggestions, and content to the subjects, curricula, and grade levels you teach.
  • To find library searches that return poor or no results, so we can improve search and decide which content to add.
  • To review contributor applications and decide whether, and for which subjects, to grant contributor access.
  • To count how often our campaign links are opened and by how many unique visitors, so we can tell which campaigns are worth running.
  • To measure how our website and app are used through Google Analytics, where you have consented.
  • To measure and improve our adverts on Facebook and Instagram through the Meta Pixel, where you have consented to marketing cookies.
  • To improve product quality, reliability, and user experience.
  • To comply with legal obligations and respond to lawful requests.

AI Processing

When you use an AI feature, the prompt and the content you select are sent to Prezuva and, where applicable, to third-party AI and media processing providers acting on our behalf under contract, so that the requested output can be generated and returned to you. We keep records of AI generation requests and their outcomes to deliver the feature, enforce allowances, support review of AI-generated content submitted to the library, prevent abuse, and troubleshoot failures.

We do not use your prompts or generated output to sell advertising, and we require our AI providers to process the data only for providing the service to us. Please avoid entering personal data about students or others into AI prompts beyond what the lesson requires. AI features do not make decisions with legal or similarly significant effects about you; grading and academic decisions remain with the teacher and institution.

Creator Studio and Payout Data

If you contribute content, we process your submissions, their metadata and review history, and statistics about how your published content is used across the platform, such as insertions into lessons, use in live classes, and unique students opening it from courses. These usage records are used to show your impact and to calculate your share of the contributor pool.

To pay you, we process the payout profile you submit, including payout method, account holder name, country, currency, payment identifier, phone number, and bank or branch details, together with the earnings, adjustment, and payout batch records associated with your account. Payout details are shared with the payment providers used to send funds, and may be reviewed by authorised Prezuva administrators for verification, fraud prevention, and reconciliation. Financial and tax-related records are retained for the periods required by accounting and tax law.

Published content may be shown to other users with attribution or contributor information where the product displays it. Content removal requests are recorded along with their outcome.

We also keep records of contributor status itself, including when it was granted, changed, suspended, or withdrawn, and the reason, so that access decisions can be applied and reviewed. Prezuva decides who holds contributor access and may grant or remove it at its discretion, as set out in our Terms of Service.

If you apply to become a contributor, we use your application to decide whether to grant contributor access and in which subjects. Applications are reviewed by authorised Prezuva staff, and their notes and each change of status are recorded so that the decision can be explained and reviewed. You can withdraw an application before a decision is made.

The contributor payout process is still under development. Payment processing, verification, and tax documentation arrangements, and the providers involved in them, are not yet finalised. When they are, this policy will be updated to describe the providers used and the data shared with them before those arrangements take effect.

Billing and Payments

We process plan, entitlement, allowance, and usage records to give you the features you are entitled to and to show your remaining allowances.

Payments are processed by Stripe. When you buy or manage a subscription, you enter your payment details on pages hosted by Stripe, and Stripe processes them to take the payment, calculate tax, prevent fraud, and meet its own legal obligations, such as anti-money laundering checks. For payment processing Stripe acts as our service provider; for fraud prevention and its regulatory obligations it acts as an independent controller under the Stripe Privacy Policy. Stripe may use technical data from your device, such as your IP address and browser details, to detect fraudulent payments.

We use payment and billing data to provide your subscription, send receipts and billing emails (such as renewal, failed payment, and plan change notices), handle refunds and disputes, calculate and report tax, and keep the accounting records the law requires. We do not use your payment details for advertising, and we do not sell them.

Visiting Without an Account

Some of our links, such as those we use in advertising and on social media, open the Prezuva editor without asking you to sign in, so that you can try it first.

When you open one of these links, we record the campaign, the time, the page that referred you, your browser's user-agent string, and a salted one-way hash derived from your IP address and user agent. The hash lets us count unique visitors without keeping your IP address against the visit. It is still treated as personal data, because it can recognise a repeat visit from the same browser. We use these records only to measure how well each campaign performs. Individual records are deleted after 13 months, or sooner if the campaign is deleted, after which only each campaign's running totals remain.

Anything you build in the editor without an account stays in your browser. It is not sent to our servers and is not linked to you, and it may be lost if you close the page or clear your browser data. Features that would store data on our servers, such as saving, uploading, or AI tools, ask you to create an account first. If you sign up, the rest of this policy applies to your account from that point.

Google Analytics runs on these pages only if you have agreed to analytics cookies, and the Meta Pixel only if you have agreed to marketing cookies.

Legal Bases (UK GDPR and EU GDPR)

  • Contract: to provide services you request, including account, classroom, library, paid subscription, payment, refund, and payout features, and to review a contributor application you submit.
  • Legitimate interests: platform security, fraud and abuse prevention, integrity of usage and revenue calculations, product improvement, tailoring content to your teaching profile, improving library search, and measuring how our campaign links perform.
  • Consent: optional analytics cookies (Google Analytics) and marketing cookies (Meta Pixel) on our website and in the app, and optional marketing messages. You can withdraw consent at any time.
  • Legal obligation: keeping accounting and tax records for payments, refunds, and payouts, calculating and reporting tax, and responding to lawful requests.

Sharing

We do not sell personal data. We may share data with infrastructure and service providers, such as hosting, storage, content delivery, transactional email, authentication, and analytics services, under contractual safeguards and only for operating Prezuva.

This includes Cloudflare, which carries traffic to our website and app and provides security, caching, and protection against abuse, and so processes visitors' IP addresses and request data; Google, for Google Analytics where you have consented and for Google sign-in if you choose to use it; Meta, for Facebook sign-in if you choose to use it and for the Meta Pixel where you have consented to marketing cookies; transactional email providers, which deliver account emails such as verification and password reset messages; and cloud object storage and content delivery services used to store and deliver uploaded files and media.

It may also include AI and media processing providers used to power generation, translation, and background removal; Stripe, which processes subscription payments, tax, and invoices; payout providers used to send contributor payouts; video conferencing providers where you use that integration; and stock media, icon, and image search providers used to find assets inside the editor.

We may additionally share data with your institution where it administers your account, with professional advisers, and with authorities or other parties where required by law, to enforce our Terms, to investigate fraud or security incidents, or in connection with a merger, acquisition, or transfer of assets, in which case we will notify affected users where required.

Integrations and Embedded Content

Where you connect an external account, such as a video conferencing provider, we process the tokens and identifiers needed to create and join sessions on your behalf. Data you place into that provider's service, including any recordings, is governed by that provider's own terms and privacy policy.

Lessons may embed media hosted elsewhere. When such media is displayed, the hosting site may receive the viewer's IP address and set its own cookies. We also proxy or cache some external images to protect viewers and improve reliability.

Age Verification for the Zoom Integration

Before an independent teacher connects a Zoom account to Prezuva for the first time, we ask for their date of birth and country or region to determine whether they satisfy the minimum age requirement for authorizing the integration. Independent teachers must be at least 18 years old to authorize Zoom through Prezuva.

The submitted date of birth is processed only to calculate age eligibility and is not retained after that calculation. We retain whether the account is eligible, the submitted country or region, the verification method, the applicable age-policy version, and the date and time of verification. We use this information only to enforce access to the Zoom authorization flow and demonstrate compliance with platform and legal requirements. It is not used for advertising, marketing, or profiling.

We do not provide the submitted date of birth or the age-verification record to Zoom. Students do not authorize the Prezuva Zoom integration. Zoom authorization is restricted to authenticated teaching-purpose accounts that have passed this check. If you believe your eligibility information is incorrect, contact privacy@prezuva.com to request correction or deletion, subject to applicable law and any information we need to retain for security or compliance.

International Transfers

Prezuva and our service providers may process data in countries other than your own. Where personal data is transferred out of a region with data transfer restrictions, we rely on appropriate safeguards, such as UK or EU standard contractual clauses, the UK International Data Transfer Agreement or Addendum, or an adequacy decision, together with contractual and technical protections.

School, Course, and Classroom Access

Teachers, schools, and institutions may control access to certain content, courses, classes, assignments, quizzes, and live sessions. Student access requests, approvals, submissions, and grading data may therefore be visible to the relevant teacher or institution administrators as part of operating the service.

In live teaching sessions, the display name you join with and the responses you submit to polls, question and answer, drawing, and upload activities are visible to the host, and may be shown to other attendees where the host chooses to display them.

Shared Lesson Links

You can share a lesson by creating a link. Anyone who has the link can open and view the lesson in a browser without signing in, so treat a share link like the lesson itself: send it only to people you intend to see it, and keep personal information about students out of lessons you share. Signed-in recipients may also be able to save their own copy of a shared lesson to their account.

You can revoke a share link at any time, after which it stops working. Revoking a link does not remove copies that signed-in recipients have already saved to their accounts.

Security

We use technical and organisational measures appropriate to the risk, including encryption in transit, hashed password storage, access controls and role separation, signed or time-limited access to stored media, session management, and logging and monitoring. Access to payout and administrative data is restricted to authorised personnel. No system is completely secure, and you are responsible for keeping your credentials safe. If a breach affecting your personal data occurs, we will notify you and the relevant authorities where required by law.

Retention

We retain data only as long as needed for service delivery, legal compliance, dispute resolution, and security. Retention periods may vary by data type and account status. Some live classroom activity responses may be temporary by design, while account records, stored media, lessons, submissions, and related educational records may remain until deleted by the account holder, institution, or as otherwise required for service operation or legal reasons.

Payout, earnings, and billing records are kept for the periods required by tax and accounting law. Usage records underlying revenue sharing are retained so that periods can be audited and corrected. Security and abuse-prevention logs are kept for a limited period. Backups are cycled on a rolling basis, so deleted data may persist in backups for a short time after removal from the live service. Content you publish to the library is retained and remains available to other users for a minimum period of six months from publication, and cannot be withdrawn during that period except where removal is legally required or where we agree to an earlier removal at our discretion. After that period, an accepted removal request de-lists the content from library search and browsing, but content you published may remain in lessons and courses where other users have already inserted it, even after it is removed from the library.

We also apply these specific periods:

  • Library searches: linked to your account for 12 months, then kept without any link to you, and deleted after 24 months. If you delete your account, your searches are unlinked from you immediately.
  • Campaign link records: deleted after 13 months, or sooner if the campaign is deleted. Only each campaign's running totals are kept.
  • Contributor applications: unsubmitted drafts are deleted 90 days after they were last edited, and declined or withdrawn applications 12 months after the decision or withdrawal. Approved applications are kept while you remain a contributor.
  • Contributor applications when you delete your account: an application that was not approved is deleted within a day. If your application was approved, its personal details are erased within a day, but the record that you accepted the Contributor Terms is kept for up to six years, because content you contributed may remain licensed in the library.
  • Payment and billing records: invoices, payments, refunds, and the billing details on them are kept for six years after the end of the financial year they relate to, as UK tax and company law require, even if you delete your account. Stripe keeps its own records under its privacy policy.
  • Google Analytics data: kept for 14 months.
  • Meta Pixel data: we do not keep a copy. Meta holds it under its own retention terms, and it stops being collected as soon as you withdraw marketing consent.
  • Zoom age eligibility: retained while the associated Prezuva account remains active, or longer where required for security, compliance, dispute resolution, or law. The eligibility record is deleted when the associated account is deleted unless retention is legally required. The date of birth submitted for the check is not retained after eligibility is calculated.

Your Rights

Depending on your location, you may have rights to access, correct, delete, restrict, or export your personal data, and to object to certain processing.

You may also withdraw consent where processing is based on consent, without affecting processing already carried out, and lodge a complaint with a data protection authority. In the United Kingdom this is the Information Commissioner's Office (ico.org.uk); elsewhere it is your local supervisory authority. To exercise a right, contact privacy@prezuva.com. We may need to verify your identity, and some rights are limited where we must keep records for legal, accounting, or fraud-prevention reasons, or where fulfilling a request would affect another user's data. If your account is administered by a school or institution, we may refer your request to that institution.

If you believe a Zoom age-eligibility result is incorrect, you can ask us to review, correct, or delete it by contacting privacy@prezuva.com. We may ask for information needed to verify your identity and the accuracy of the request.

A request to delete your account does not by itself remove content you published to the library. Published content is subject to the minimum availability period and the de-listing process described in our Terms of Service, and copies already incorporated into other users' lessons and courses remain with those users. We will still delete or anonymise your account and profile data where you ask us to and we are not required to keep it.

Children and School Use

Prezuva may be used in educational settings where teachers and institutions manage student participation. Schools and institutions remain responsible for ensuring lawful data use, authorization, and notices in their jurisdiction, including where student accounts or access are managed centrally.

You must be at least 13 years old to use Prezuva, or older if the age of digital consent in your country is higher (for example 16 in some EU countries). Students who meet this age use Prezuva on the same basis as any other user: they make their own cookie and consent choices, and this policy applies to them in full. Users below that age may only use Prezuva through an account provided and managed by their school or institution, which is responsible for obtaining any consent required by law. We do not knowingly collect personal data from children below the minimum age other than as instructed by a school or institution. We never send lesson content, student work, or data from school-managed accounts to advertising partners. If you believe a child's data has been provided to us without the necessary authorisation, contact privacy@prezuva.com and we will investigate and delete it where appropriate.

Google Analytics and the Meta Pixel are never used for accounts provided and managed by a school or institution.

Students do not authorize the Prezuva Zoom integration. Independent teachers must be signed in to an authenticated teaching-purpose account and be at least 18 years old before Prezuva permits Zoom authorization. Student accounts and accounts that do not satisfy the age requirement are blocked from that authorization flow.

Cookies and Similar Technologies

We use a small number of cookies and browser storage, in three groups.

  • Essential, always on: your sign-in session cookie, which keeps you signed in and lets our website recognise that you are already signed in so it can take you straight to the app; security cookies that Cloudflare may set to protect the service from abuse; and a record of your cookie choices. We also use your browser's local storage for product settings and work in progress, such as editor recovery drafts and work created without an account. These are needed for the service to work and do not require consent.
  • Analytics, only with your consent: Google Analytics cookies (named _ga and _ga_ followed by an identifier) that measure visits and usage on our website and in the app. They are set only after you choose to allow analytics, are never used for school-managed accounts, and are not used for advertising.
  • Marketing, only with your consent: the Meta Pixel, provided by Meta Platforms Ireland Limited, which sets cookies (named _fbp and _fbc) and tells Meta when you visit our website or the app and when you take actions such as signing up. We use it to measure our adverts on Facebook and Instagram and to show them to people likely to find Prezuva useful. Meta receives your IP address, browser details, and the pages you visit, and may combine this with information it holds about you under its own privacy policy. We do not send Meta your name, email address, or any lesson or student content. It loads only after you choose to allow marketing cookies and is never used for school-managed accounts.

Your analytics and marketing choices are separate from accepting our Terms: you can use Prezuva fully without agreeing to either. You can change or withdraw your choice at any time through Cookie settings, found in the footer of our website and in your account menu in the app. Your choice applies to both.

Records we keep to operate features, such as entitlement checks, usage allowances, contributor impact, and revenue sharing calculations, are necessary to deliver the service and are not optional analytics, so they are not controlled by the cookie banner.

Changes to This Policy

We may update this policy as the product and applicable law change. The revised date at the top of this page shows when it was last changed, and for significant changes we will provide additional notice through the product or by email.

Contact

The data controller for personal data described in this policy is Prezuva Ltd, Unit A, 82 James Carter Road, Mildenhall IP28 7DE, United Kingdom. For privacy questions or requests, contact: privacy@prezuva.com

For legal notices, including intellectual property complaints, contact legal@prezuva.com. See also our Terms of Service.

Prezuva

Empowering educators with the next generation of presentation and engagement tools.

Product
  • Features
  • How it works
  • Pricing
  • Resources
  • Marketplace
Support
  • Help Center
  • Zoom Integration
  • Privacy Policy
  • Terms
  • Creator Program
Company
  • About
  • Events
  • Careers
  • Partners & Affiliates
  • Press

© 2026 Prezuva Ltd. All rights reserved.

Status Cookies

Cookie settings

We use necessary cookies to run Prezuva. With your consent, we also use analytics cookies to understand how the site is used, and marketing cookies (Meta Pixel) to measure our ads. See our Privacy Policy and Terms.