Last updated: 19 September 2026
Privacy Policy
This Privacy Policy explains how Plenora AS ("Plenora", "we", "us") collects, uses, and protects personal data when you use our service at plenora.io.
1. Data controller
Plenora AS (org. no. 837 322 502, Sofienberggata 29C, 0558 Oslo, Norway) is the data controller for processing carried out through the Plenora platform. For personal data processed on behalf of an organisation that uses Plenora to run sessions, that organisation is the data controller and Plenora acts as data processor (see our Data Processing Agreement).
2. Data we collect
Account data
When you create an account we collect your name, email address, and authentication credentials. If you sign in with Google OAuth we receive your name, email, and profile picture from Google.
Session data
When you participate in or create a session we process the responses, votes, and other contributions you submit. Session creators can see aggregated and, where the session design allows, individual responses.
Usage data
We collect technical data required to operate the service: IP address (used for rate limiting and abuse prevention), browser type, request paths, and timestamps. We do not use advertising trackers or third-party marketing analytics. Visits to public pages and selected product events are measured by Plenora without an analytics cookie or persistent browser identifier. The analytics service uses the IP address and User-Agent to create an identifier with a random daily salt. It does not store the raw IP address or User-Agent in the analytics database. Core Web Vitals are sent to a Plenora-operated endpoint. Each public-page event records the page path, the referring site, the country derived from the IP address, device type, browser, operating system, browser language, and any campaign parameters in the link.
When Sentry is configured for the deployment, browser errors and diagnostic breadcrumbs, server errors, and sampled server performance data are sent to Sentry. In the browser, session replay, profiling, tracing, and release-session tracking are disabled. On our servers, sampled request tracing and profiling (10% of requests by default) and release-session tracking are enabled so we can monitor performance. See the Subprocessor List for the data fields involved.
Optional AI features
When you invoke an AI authoring feature (for example, "Generate exercises"), the relevant slide content is transmitted to OpenAI to produce the requested output. This content may include titles, body text, and speaker notes for slides in the request. AI authoring features are not invoked unless you take an action that requires them. Where Plenora is operated for an organisation, the organisation may disable AI authoring features for its tenant.
Payment data
Payments are processed by Stripe. We do not store credit card numbers. Stripe acts as an independent data controller for payment data. See Stripe's Privacy Policy.
3. Purposes and legal basis
We process personal data for the following purposes:
| Purpose | Legal basis (GDPR Art. 6) |
|---|---|
| Providing the Plenora service | Performance of contract (Art. 6(1)(b)) |
| Account creation and authentication | Performance of contract (Art. 6(1)(b)) |
| Processing payments | Performance of contract (Art. 6(1)(b)) |
| Rate limiting and abuse prevention | Legitimate interest (Art. 6(1)(f)) |
| Service diagnostics and error investigation | Legitimate interest (Art. 6(1)(f)) |
| Measuring service use and public-page performance | Legitimate interest (Art. 6(1)(f)) |
| Legal obligations (e.g. accounting) | Legal obligation (Art. 6(1)(c)) |
4. Subprocessors
We use a limited number of subprocessors to operate the service. See our Subprocessor List for the current list.
5. International transfers
Primary application data is hosted in the EU, currently in France (Scaleway). Some subprocessors process data outside the EU/EEA. See the Subprocessor List for the location of each. Where personal data is transferred outside the EU/EEA, we rely on Standard Contractual Clauses (SCCs) or other safeguards permitted under GDPR Chapter V. We do not transfer personal data outside the EU/EEA without an applicable safeguard.
6. Data retention
Account data is retained for as long as your account is active. When you delete your account, we delete your account data and content from our systems. This normally completes within one month. Backup copies may persist for up to six months and are used only to restore service after a failure. Records we are required to keep by law, such as invoices and payment records held by Stripe, are kept for the statutory period, which is five years under the Norwegian Bookkeeping Act.
Session data containing participant contributions is retained while the related presentation remains stored, unless the relevant data controller requests deletion. Empty, abandoned, and response-free sessions may be removed earlier by automated cleanup. Deleted presentations are kept in a trash for 30 days and then purged.
Server logs containing IP addresses are retained for operational security and deleted according to the configured retention schedules of Plenora and its infrastructure providers.
Plenora analytics events are retained for 90 days. Raw IP addresses and raw User-Agent strings are not stored in the analytics database.
Sentry diagnostic datais retained according to the retention settings of Plenora's Sentry project and service agreement.
7. Your rights
Under the GDPR you have the right to:
- Access the personal data we hold about you
- Rectify inaccurate personal data
- Erase your personal data ("right to be forgotten")
- Restrict or object to processing
- Data portability
- Lodge a complaint with the Norwegian Data Protection Authority (Datatilsynet)
To exercise these rights, contact us at [email protected].
8. Cookies and browser storage
Plenora uses cookies for authentication, session management, participant continuity, language preferences, and editor layout preferences. We do not use advertising cookies or a cross-visit attribution cookie. Public-page measurement does not set a browser identifier. Account session cookies can last up to 30 days, live-session participant cookies last 24 hours, anonymous survey continuity cookies last up to 30 days, preference cookies last up to one year, and authentication security cookies are limited to the relevant sign-in flow.
Audience and presenter state needed to survive a reload is stored in tab-scoped session storage and is intended to last only for that tab. Some editor preferences and the editor clipboard use local storage and remain until they are overwritten or you clear site data.
The semantic word-cloud feature downloads model files and allows the browser library to cache them in IndexedDB only after that feature is invoked. The model cache does not contain participant responses and is not preloaded for every signed-in user.
9. Security
We implement appropriate technical and organisational measures to protect your data, including encryption in transit (TLS), encryption at rest for database storage, and access controls. See our DPA for details on security measures.
10. Changes to this policy
We may update this Privacy Policy from time to time. We will inform registered users of material changes before they take effect. The "last updated" date at the top of this page indicates when the policy was last revised.
11. Contact
Plenora AS, org. no. 837 322 502
Sofienberggata 29C, 0558 Oslo, Norway
Email: [email protected]
Privacy requests: [email protected]