Privacy Policy.
Last updated: 4 November 2026
This policy explains how Diaposi handles personal data when you visit the website, create or use an account, host or join a session, study from a document, open a report, contact support or use an AI-assisted feature. It is written for account holders, hosts, participants, report recipients and educational institutions.
Diaposi does not require a participant account for a live session. A session identifier is pseudonymous, not necessarily anonymous: the timing, wording or classroom context of a contribution may still identify its author.
1. Controller and contact
For website operation, accounts, direct subscriptions, security, support and Diaposi's own product administration, the controller is Diaposi, a société par actions simplifiée à associé unique (SASU) with its registered office at 9 Rue du Renard, 76000 Rouen, France, represented by its president, Alae Belaich; its registration with the Trade and Companies Register of Rouen is in progress. Diaposi has not appointed a data protection officer, which the GDPR does not require of it; its president answers privacy requests. When an institution uses Diaposi to process classroom or learner data under its instructions, the institution is normally the controller and Diaposi is its processor for that processing.
Privacy requests may be sent to legal@diaposi.com. Do not send passwords, session credentials, recovery codes or unnecessary identity documents by email.
The publisher's registration details are on the Legal notice.
2. Roles in education
A school, university, training organisation or employer that decides why and how Diaposi is used for its learners remains responsible for its lawful basis, notices, access rules, retention choices and handling of rights. Diaposi processes instructed classroom content under the customer agreement and a GDPR Article 28 data-processing agreement where required. Diaposi remains an independent controller for limited account, billing, legal-compliance and service-security processing it determines itself.
A teacher or administrator must not treat acceptance of Diaposi's Terms as the learner's consent to the institution's processing. In public education, consent may not be freely given; the institution must select the lawful basis that actually applies, such as a public task or another basis under applicable education law.
3. Where data comes from
- You, when you register, upload material, configure or join a session, answer, take notes, study, request AI output, subscribe or contact support.
- A host or institution, when it creates a session, invites you, shares material, adds members or supplies account information.
- Your browser and device, through ordinary requests, security logs, cookies and first-party product events.
- Google or Microsoft, only when you choose that sign-in method, through the identity fields needed to link or authenticate the account.
- Other participants, where they create content that refers to you or is shown in a shared session or report.
4. How and why we process data
Public website and technical delivery
- Data:
- IP address, country derived locally from that address when regional access control is enabled, date and time, requested path, response status, referrer and user-agent; query strings are excluded from the reviewed access log.
- Purpose:
- Deliver pages, apply the configured regional availability policy, diagnose faults, prevent abuse and secure the service.
- Legal basis:
- Legitimate interests in operating and protecting the service; legal obligation where applicable.
- Retention:
- The country lookup is transient; the reviewed code retains the ordinary access log, including the IP address but not a separate country profile, for 30 days by default.
Account and authentication
- Data:
- Email, verification status, optional first and last name, telephone, organisation, department, role and postal address, display preferences, password hash, linked Google or Microsoft identifier, account dates, last sign-in, the counters of the free plan (learning spaces, practice exams and quizzes used) and the folders and stars you arrange your sessions with.
- Purpose:
- Create, authenticate, recover and administer an account.
- Legal basis:
- Steps requested before a contract and performance of the Terms; legitimate interests in account security.
- Retention:
- No automatic expiry: the account lasts until you close it. You can close it yourself from its settings, typing your email address to confirm; a live session or exam must be ended first. Closing it removes, in one operation, the account, its sign-in sessions, the sessions it hosted with their participants' records, its reports with their members and invitations, its learning journeys and documents, its boards, its study plans and logs, its credit receipts, its feedback, its consent records and its subscription. Authentication sessions expire after 90 days. One-time codes are valid for 10 minutes and their challenge records are removed after approximately one hour.
Terms acceptance and communication choices
- Data:
- Account identifier, action, source, wording version and timestamp.
- Purpose:
- Prove the applicable agreement and honour marketing choices and withdrawals.
- Legal basis:
- Performance of the agreement, consent for electronic marketing, and establishment or defence of legal claims.
- Retention:
- An append-only history with no automatic expiry, removed when the account is closed.
Live-session host and presentation
- Data:
- Host account where used, session settings and code, presentation file and extracted/rendered content, host actions, timing and session results.
- Purpose:
- Prepare, run and report an interactive session.
- Legal basis:
- Performance of the Terms for a direct host; the institution's documented instructions and lawful basis for customer-controlled use.
- Retention:
- Original uploaded file: up to 24 hours. Rendered material and session data: ordinarily up to 12 months from the session, except where an account holder deliberately retains material in an ongoing learning journey.
Per-account upload conversion cache
- Data:
- Account identifier, SHA-256 fingerprint of the uploaded file, internal rendered-material identifier, format, page count and first/last-use dates. The fingerprint is scoped to one account and is not the readable file.
- Purpose:
- Avoid converting the same file repeatedly for the same account.
- Legal basis:
- Performance of the requested upload and legitimate interests in service efficiency.
- Retention:
- No automatic expiry; removed when the account is closed. The record can remain after the rendered file has been removed.
Live-session participant
- Data:
- Random per-session identifier, the name you give when a room asks for one (shown to the host and to the other participants), account identifier only if you choose to sign in and attach the seat, join and activity times, reactions, poll or quiz answers, comments, questions and replies, free-text answers, private drawing strokes, progress and technical connection events. An account or email is not required to join the live room.
- Purpose:
- Provide participation, show authorised live results, prevent duplicate actions and create the session report.
- Legal basis:
- The host institution's lawful basis and instructions; performance of the requested service for direct individual use; legitimate interests for proportionate security.
- Retention:
- Up to 12 months from the session. Thirty seconds after a room ends, the names are copied into the session's attendance list, which is tied to nothing else, and removed from every participant row; each participant's device token is replaced by a one-way hash with a salt that is then discarded, so that nothing kept afterwards can be matched back to a device or to a name.
Participant experience feedback
- Data:
- Session identifier, pseudonymous participant token, rating from 1 to 5, optional message of up to 500 characters, vote time, time spent in the session, audience-size indicators and reaction counts.
- Purpose:
- Understand the participant's experience and relate voluntary feedback to limited session context.
- Legal basis:
- Legitimate interests in product research, taking account of the voluntary submission and pseudonymous context.
- Retention:
- Up to 12 months from creation in the reviewed application.
Live exam rooms
- Data:
- Exam room code, a random participant token held in a cookie, the name you give, seat number, readiness, answers, flags, marks, extra time granted, start and finish times, and your account identifier if you were signed in.
- Purpose:
- Run a mock exam or quiz with a room, mark the answers and show the results to the host and to you.
- Legal basis:
- The host institution's lawful basis and instructions; performance of the requested service for a direct host; legitimate interests in preventing duplicate seats.
- Retention:
- 12 months from joining.
Whiteboards and learning spaces
- Data:
- The boards you create or join: their elements (text, shapes, drawings, stickers, links, the pages of documents you import, the videos you link), the files you upload to them, their settings, a log of what was added, changed or removed, the names of the participants of a shared board, and the AI material made from a document on request.
- Purpose:
- Provide your whiteboards and learning spaces, keep them in step between devices and participants, and let you put a deleted board back.
- Legal basis:
- Performance of the Terms; the host institution's instructions for a board used in its session.
- Retention:
- Until you delete the board. A deleted board or session waits 30 days in the Trash, where you can put it back, then is removed for good. A board that belongs to a live session follows the session's 12 months. Files and elements are capped per board under the free plan.
Reports and invitations
- Data:
- Aggregated and individual session results, report title and dates, invited email, membership, access and audit events.
- Purpose:
- Generate, save, share, authorise and audit access to a session report.
- Legal basis:
- Performance of the Terms or customer instructions; legitimate interests in access security.
- Retention:
- A saved report expires no later than 12 months from the underlying session. Invitation, membership and access-audit records are configured for up to 12 months from their own creation and can therefore outlive the inaccessible report. An unclaimed report is removed after approximately one hour.
Personal learning journey
- Data:
- Documents and rendered pages, title and file name, study status, reading position, reactions, encrypted notes, drawing references, quiz attempts, answers, scores, time spent, calendar, study plan and review history.
- Purpose:
- Provide the signed-in learner's library, progress, notes, revision and planning tools.
- Legal basis:
- Performance of the Terms; customer instructions where an institution provides the journey.
- Retention:
- Until you delete the journey or close the account, which removes the journey, its documents and what was made from them. Learning events expire after 12 months, study-session logs after 13 months and temporary study-plan designs after 30 days; the calendar, folders, flashcards and their review history last as long as the account.
AI-assisted features
- Data:
- The visible text or learning context needed for the request, the user's question or answer, instructions supplied by the application, generated output, model/usage metadata and related resource identifier. Passwords and authentication credentials are not intended as AI inputs.
- Purpose:
- Generate summaries, topics, explanations, flashcards, quizzes, study plans or feedback, including evaluation of a free-text answer when requested.
- Legal basis:
- Performance of the requested feature or the institution's instructions; legitimate interests for limited operational usage records.
- Retention:
- Outputs saved directly in a session or learning record follow that record where technically linked. A separate reusable generated-content package, keyed to a content fingerprint and model version, and AI usage metadata currently have no automatic expiry; the package can remain after the source deck is removed. Provider-side retention cannot be stated until the production AI contract and settings are confirmed.
First-party product events
- Data:
- Feature or interface event, time, role, session or resource identifier, application build and limited event properties. For a signed-in account, also: each sign-in and sign-out (time, method, country looked up from the IP address on our own server, the IP address itself is not kept, browser and device type, browser time zone), the pages of the application opened with the time each stayed visible, and the name of the buttons pressed. Nothing typed into a field is recorded, and no cross-site advertising identifier is created.
- Purpose:
- Understand reliability and how each part of the service is used, improve it, support account holders and investigate errors.
- Legal basis:
- Legitimate interests in running and improving the service, balanced against the limited nature of the events, which stay with Diaposi and are never used for advertising; customer instructions where appropriate.
- Retention:
- Up to 12 months for each event. The account keeps only running totals (number of sign-ins and sign-outs, last seen, last country and time zone) until it is closed; closing the account removes them and the events.
Account-holder product feedback
- Data:
- Account identifier, rating from 1 to 5, optional free-text comment and submission time.
- Purpose:
- Understand an account holder's opinion and improve Diaposi.
- Legal basis:
- Legitimate interests in product research, taking account of the voluntary and limited submission; performance of the Beta Terms where feedback is part of an invited beta.
- Retention:
- One response per account, kept until the account is closed; Diaposi asks for a rating once per person and never again.
Credits and plan usage
- Data:
- Account identifier, month, the share of the monthly allowance used for sessions and for AI-assisted work, one receipt per session started (its code, its date and the amounts counted), and the free plan's counters.
- Purpose:
- Apply the free plan's allowances and limits, tell you what is left, and refuse a start when the allowance is used up.
- Legal basis:
- Performance of the Terms.
- Retention:
- The monthly ledger stays with the account and keeps only its identifier; a session receipt is removed 100 days after the session.
Upgrade waiting list
- Data:
- Account identifier, email, the date you joined and the buttons from which you asked, the last thirty.
- Purpose:
- Record who is interested in features beyond the free plan and write to them when an offer exists.
- Legal basis:
- Steps requested by the person before a possible contract.
- Retention:
- Until you ask to be taken off the list or the account is closed.
Support and error reports
- Data:
- Message, optional email, role, page, browser information, account or session reference, diagnostic context and optional screenshot, and the messages of a Help chat with their pictures.
- Purpose:
- Answer the request, reproduce a fault, secure the service and improve reliability.
- Legal basis:
- Performance of the service, legitimate interests, or steps requested by the user.
- Retention:
- Application error reports expire after 30 days. An optional screenshot is delivered to the support mailbox rather than stored in the error-report database. Help chats and their pictures last until the account is closed.
Contact, demo, sales and question forms
- Data:
- Name, role or type of enquiry, institution, email, optional phone number, message, the acceptance and the optional product-news choice, and the visit the form was sent from: page, referring site (without its query), country derived locally from the IP address, device type, operating system, browser, screen size, browser language, time zone and time taken. The IP address and the full user-agent are not stored with the message.
- Purpose:
- Answer the message, arrange a demonstration, answer a sales enquiry, keep a record of the exchange and keep automated spam out.
- Legal basis:
- Steps requested by the person before a possible contract; legitimate interests in answering enquiries and preventing abuse.
- Retention:
- Three years from the message, then deleted automatically. Messages classified as spam are deleted after 30 days.
Waiting list and electronic updates
- Data:
- Email, subscription status and source, timestamps, unsubscribe token, limited IP/user-agent/referrer and capped signup history.
- Purpose:
- Manage a requested waiting-list or marketing subscription, prevent abuse and prove the choice.
- Legal basis:
- Consent for electronic marketing; legitimate interests for proportionate anti-abuse records and suppression of messages after withdrawal.
- Retention:
- Until withdrawal for delivery; a minimal suppression record may be retained afterwards. The current model contains no automatic expiry for the associated technical history.
Emails about Diaposi to account holders
- Data:
- Account email, subscription status and source, timestamps and unsubscribe token.
- Purpose:
- Send the holder of a confirmed account occasional emails about Diaposi: what the service does, what is new and how to use it. Every such email carries an unsubscribe link, and an address that has unsubscribed is not added back when its holder signs in again.
- Legal basis:
- Legitimate interests in informing account holders about the service they use. Each person may object at any time, free of charge, through the unsubscribe link in every email or by writing to us.
- Retention:
- Until the person unsubscribes or the account is deleted. After an unsubscribe, a minimal suppression record is kept so that no further email is sent. When the account is deleted, an address that was on the list only because of the account is removed.
Emails to education professionals
- Data:
- Name, professional email address, organisation and role as published on the organisation's public website, the date an email was sent, any reply, whether a link in the email was opened, with the date and the type of browser, and, if a Diaposi account is later opened with the same address, whether it has uploaded a document or run a session.
- Purpose:
- Write to teachers and education staff about Diaposi when it concerns their professional role, and know which emails led someone to visit Diaposi, so that we only follow up where there is interest.
- Legal basis:
- Legitimate interests in presenting a teaching tool to professionals whose work it concerns. Each person may object at any time, free of charge, by replying stop to the email or by writing to us; they are then never written to again.
- Retention:
- Up to 12 months after the last email sent, unless the person becomes a customer or asks us to delete it sooner. After an objection, a minimal suppression record is kept so that no further email is sent.
Security and legal compliance
- Data:
- Authentication, access and abuse signals, IP address, security events, moderation records and information required for a legal request or claim.
- Purpose:
- Prevent, detect and investigate misuse; enforce the Terms; protect people and systems; comply with valid law.
- Legal basis:
- Legitimate interests and legal obligations; establishment, exercise or defence of legal claims.
- Retention:
- Normally 30 days for technical logs; longer only where an identified incident, dispute or legal preservation duty requires a restricted copy.
Audience measurement on the public website
- Data:
- Pages viewed, buttons and links used, whether a form was sent (never its contents), the page or site that led to the visit, device and browser type, an approximate location derived from the IP address, and an identifier kept in a cookie. No account, session or classroom data.
- Purpose:
- Count visits and see which pages are read, in order to improve the website.
- Legal basis:
- Consent, given in the cookie notice and withdrawable at any time with the Cookies link at the foot of the website.
- Retention:
- The cookies last 13 months at most. Google keeps visit-level data for the period set in the Analytics property, 14 months at most; aggregated statistics, which identify no one, are kept longer.
Deleted automatically today, by the database itself rather than by anyone remembering: sessions and everything produced inside them, which is the room, its polls, quizzes, questions, reactions, attendance list and participant records, twelve months after the session; exam rooms and their participants' answers, twelve months; saved reports and their invitations, members and access log, twelve months after the session they describe; uploaded documents and the slide images rendered from them, twelve months, with the original file kept one day; a session set up but never started, six hours; a session draft, thirty days; whatever you put in the Trash, thirty days; the receipt of a session's credits, one hundred days; study-session logs, thirteen months; error logs and access logs, thirty days; messages sent through the contact forms, three years, or thirty days when classified as spam; the records of emails to education professionals, twelve months after the last one; beta applications, six months after a refusal and eighteen months at most otherwise; sign-in state, the length of the sign-in; and the short-lived rows behind an email verification or a provider redirect, minutes. Not deleted automatically, and therefore kept until the account is closed or until you ask: the account itself, consent and acceptance records, subscription records, the credits ledger, the Upgrade waiting list, AI usage records and AI-generated packages, whiteboards and learning spaces, study calendars, folders, flashcards and the review history behind them, and product feedback.
Content produced from a document by the AI features, meaning summaries, explanations, quizzes, flashcards and the study material built from it, is deleted together with the document it came from. That is not a separate rule anyone has to remember: removing a document removes everything derived from it in the same operation, so derived content can never outlive its source.
5. What other people can see
- A host can see the session state, participation and contributions made visible by the selected activity. Other participants may see content displayed in the shared room.
- A session report can contain individual pseudonymous activity and aggregates. Authorised report members can see the report within the permissions granted to them.
- A live participant's private notes remain on that participant's device. Drawing strokes may also be synchronised to the server for session recovery and retained with the participant's session record; they are returned only through that participant's access credential and are not readable by the host. The host may receive limited aggregate activity counts.
- A signed-in learner's notes may be synchronised as encrypted text for that learner's own journey. The account holder controls access through the device key and recovery method.
- Exports are downloaded to the requesting user's device. After export, the recipient is responsible for securing, sharing and deleting that copy.
Do not submit confidential, health, disability, disciplinary, biometric or other special-category information. If an institution proposes an exceptional use involving such data, it must first identify both an Article 6 GDPR legal basis and an Article 9 condition, establish necessity and proportionality, complete any required impact assessment, and agree specific safeguards with Diaposi. Diaposi does not need biometric data or emotion recognition to provide the reviewed service.
6. AI transparency and human review
AI output can be incomplete, inaccurate or biased. Diaposi uses it as an assistance feature, not as the final decision-maker. Diaposi does not use AI to take a decision that produces legal or similarly significant effects about a learner. A teacher or institution must not use an AI-generated score, explanation, classification or recommendation as the sole basis for admission, assessment, discipline, access to education or another significant decision.
Users should be told when content or feedback is AI-generated, be able to review relevant inputs and outputs, and have an appropriate human contact for contesting educational use. Diaposi does not perform biometric categorisation, remote exam proctoring or emotion recognition in the reviewed code.
7. Recipients and processors
Personal data is disclosed only as needed to: authorised Diaposi personnel and contractors; the institution, host, participants or invited report members according to the feature; hosting, database, storage, email and operational providers; Google or Microsoft when their sign-in is chosen; the configured AI provider when an AI feature is requested; professional advisers; and public authorities where disclosure is legally required.
Diaposi does not sell personal data and does not use classroom data for behavioural advertising. Where a provider acts as Diaposi's processor, the executed contract must restrict it to documented instructions and applicable legal duties. Any provider acting as an independent controller must be identified with its own purpose and legal basis. These restrictions cannot be asserted for the production AI service until its contract and settings are verified.
Production subprocessors
Every provider that processes personal data to run Diaposi, what it does and where it does it. Every server that holds Diaposi's data is inside the European Economic Area. Two of these providers are American companies: their contracts carry the European Commission's standard contractual clauses for any access from outside the EEA, and the backups are encrypted before they leave Diaposi. Changes to this register are published here before a new provider begins processing. Audience measurement on the public website, and the services you can call from inside the application, are listed after this register.
Contabo GmbH
- Service:
- Application hosting: the server that runs Diaposi, its reverse proxy and its private file storage.
- Data:
- Accounts, uploaded documents and the slide images rendered from them, and session data while a session runs.
- Entity:
- Contabo GmbH, Welfenstrasse 22, 81541 Munich, Germany (HRB 180722).
- Location:
- Germany. Within the EEA, so no transfer safeguard is required.
MongoDB, Inc. (Atlas, on Amazon Web Services)
- Service:
- The managed database, as a three-node replica set.
- Data:
- Accounts, sessions, questions, answers, notes, reports and learning journeys.
- Location:
- Paris, France (AWS eu-west-3). Within the EEA, so no transfer safeguard is required.
Backblaze
- Service:
- Off-site storage for backups.
- Data:
- Database archives and copies of uploaded documents. Archives are encrypted by Diaposi before they are uploaded, so the storage provider never holds readable content.
- Entity:
- Backblaze, Inc., San Mateo, California, United States.
- Location:
- EU Central region, Amsterdam, Netherlands. The archives stay there and are unreadable to the provider; for any access by its staff from the United States, the standard contractual clauses in its data-processing agreement apply.
HostGator.com LLC / Newfold Digital
- Service:
- Email delivery and the mailboxes published on this site.
- Data:
- Addresses and the contents of messages Diaposi sends or receives.
- Entity:
- HostGator.com LLC, a Newfold Digital company, United States.
- Location:
- Frankfurt, Germany, for the mail server. For any access by the provider's staff from the United States, the standard contractual clauses in its data-processing agreement apply.
Mistral AI
- Service:
- The language model behind the AI features, used only when one of them is requested.
- Data:
- The text of the material the feature is asked about, and the request itself.
- Entity:
- Mistral AI, Paris, France.
- Location:
- European Union.
Services you choose to use from inside Diaposi
Some features of the application reach another company's service, and only when you use them. Each of these companies acts under its own privacy policy for what it receives, which is at least your IP address and the request itself; Diaposi sends it nothing from your account.
YouTube (Google Ireland Limited)
- When:
- You add a video to a board or a study session by its YouTube address.
- What:
- The player is embedded from youtube-nocookie.com and loads when you press play. The video's details and captions are fetched by Diaposi's server with Diaposi's own key, so that your browser does not have to call Google for them.
Google Drive and Dropbox
- When:
- You import a document from your Google Drive or Dropbox instead of your device.
- What:
- Their file picker opens in your browser under your own Google or Dropbox session; the file you choose is then uploaded to Diaposi like any other.
SoundCloud (SoundCloud Global Limited & Co. KG, Berlin)
- When:
- You play music with the study timer.
- What:
- SoundCloud's player is embedded and may set its own cookies when it loads.
GIPHY (Giphy, Inc., United States)
- When:
- You search for an animated picture to put on a board, where that search is offered.
- What:
- Your search words and your IP address go to GIPHY from your browser, and the pictures are loaded from its servers.
Google and Microsoft sign-in
- When:
- You choose to sign in with a Google or Microsoft account.
- What:
- The provider authenticates you and gives Diaposi your email address, your name and a stable identifier; the provider learns that you signed in to Diaposi. Google Ireland Limited and Microsoft Ireland Operations Limited act as independent controllers for that step.
Audience measurement on the public website
Google Ireland Limited
- Service:
- Google Analytics 4, on the public website only, and only for visitors who accept it in the cookie notice.
- Data:
- Pages viewed, buttons and links used, the page or site that led to the visit, device and browser type, approximate location and a cookie identifier. Nothing from accounts, sessions or uploaded documents.
- Entity:
- Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
- Location:
- Google's infrastructure, which includes the United States. Google LLC is certified under the EU-U.S. Data Privacy Framework.
8. International transfers
Diaposi will prefer processing in the European Economic Area where reasonably available. If a recipient accesses personal data from a country outside the EEA without an adequacy decision, the relevant controller must use an available transfer mechanism, such as the European Commission's Standard Contractual Clauses, assess local risks and add supplementary measures where needed. A contractual headquarters address alone does not establish where access occurs.
Transfers outside the EEA happen in three cases only: Google Analytics on the public website, for visitors who accept it; the services you choose to use from inside Diaposi (YouTube, Google Drive, Dropbox, SoundCloud, GIPHY) and sign-in with Google or Microsoft, for what those companies receive; and any access by Backblaze or HostGator staff from the United States to servers that are themselves in the EEA. Where the company is certified under the EU-U.S. Data Privacy Framework, as Google LLC is, the transfer rests on the European Commission's adequacy decision of 10 July 2023 for that framework; otherwise it rests on the standard contractual clauses in the provider's contract. No account, session or classroom data is sent to Google Analytics.
9. Security
Diaposi uses proportionate technical and organisational measures including scoped credentials, password hashing, production HTTPS design, secure cookie attributes, request validation, rate limits, restricted upload processing, browser-side encryption for synchronised notes, limited logging and retention controls. Security measures evolve with the risks and do not eliminate every possibility of loss or unlawful access.
A public overview is available on the Security page.
10. Cookies and device storage
The reviewed application uses strictly necessary first-party cookies for authentication and protected session or report access. It also stores user-requested notes, drawings, recovery state and preferences in the browser. The public website also uses Google Analytics for audience measurement, only for visitors who accept it in the cookie notice. No advertising tracker is used.
Names, purposes, durations and controls are listed in the Cookie and device-storage notice.
11. Children and students
Educational institutions must apply the protections required for their learners, including age-appropriate information, data minimisation, access controls and any required parent or guardian involvement. In France, the special rule allowing a child aged 15 or over to consent alone applies only where consent is the selected lawful basis for a direct information-society service; it does not make consent the correct basis for every school use.
A live participant joins with a name, without giving Diaposi an email or an account. An institution must not ask learners to enter identifying or sensitive information into free-text activities unless it has a documented need and lawful basis. Direct self-service accounts for younger users must not be opened until age rules, guardian handling and an age-appropriate design have been approved.
Independent accounts are for people aged 15 or over, the age at which French law lets a child consent alone to an information-society service. Beta participation is 18 or over, confirmed on the application form. Learners under 15 use Diaposi only through their institution, which remains responsible for its own lawful basis and for any parental authority its national law requires; Diaposi opens no self-service account for them. A live participant of any age can join a session with a name only, without an account or an email.
12. Your rights
Subject to the conditions and exceptions in data-protection law, you may request access, a copy, rectification, erasure, restriction, portability and information about recipients. You may object to processing based on legitimate interests, withdraw consent at any time for future processing, and request human intervention where Article 22 GDPR applies. Withdrawal does not make earlier consent-based processing unlawful.
Send a precise request to the privacy contact. Diaposi may ask for proportionate information to verify identity, but will not require an identity document by default. A response is normally due within one month; the period may be extended by two further months for a complex or numerous request, with notice during the first month.
Two things you can do yourself, without writing to anyone: close your account from its settings, which removes it and everything it owns at once, and download your learning data as a file from your learning journey page.
For institution-controlled classroom data, contact the institution first. When Diaposi receives such a request as processor, it will direct or transmit it to the responsible institution and provide reasonable assistance. Certain information may need to be retained temporarily to comply with law, protect others or establish legal claims.
You may lodge a complaint with the French Data Protection Authority (CNIL) or the authority for your habitual residence, place of work or the alleged infringement. French law also permits instructions concerning personal data after death.
13. Deletion, backups and legal preservation
Deletion removes data from active systems according to the feature and applicable retention process. Encrypted backups retain a protected copy until their scheduled rotation; that copy is isolated from ordinary use and restored only for service recovery. Data subject to a documented dispute, security investigation or legal preservation duty may be restricted and retained for that purpose, then deleted when that duty ends.
14. Beta programme
The beta application and participation process has a supplemental notice. An application sent from the beta page is saved in Diaposi's own database with the visit it was sent from, and a receipt is emailed to the applicant; an application classified as spam is kept thirty days, never answered, then deleted.
Read the Beta Privacy Notice.
15. Changes to this policy
The date at the top identifies the current version. Diaposi will provide proportionate notice of a material change before it takes effect where the change affects an account holder's rights or the agreed service. A new purpose that requires consent will not be applied on the basis of old consent.