Legal
Privacy policy
Effective 13 November 2026. This English version is a translation; in the event of any discrepancy, the Polish version prevails.
This Privacy Policy explains what personal data is processed in connection with the Scormbee service (the “Service”), for what purposes and on what legal basis, to whom it is disclosed, how long it is kept and what rights the people it concerns have (Article 13 of Regulation (EU) 2016/679 – the “GDPR”). It applies to Users, to visitors of the Service’s website and to companies the Controller writes to about working together (section 17; in that respect also Article 14 GDPR). Capitalised terms have the meaning given to them in the Terms of Service.
1. Controller
- The controller of personal data is Filip Dębiński, a natural person conducting unregistered business activity, the operator of the Service (the “Controller”).
- For all matters concerning personal data, the Controller can be contacted by e-mail: [email protected].
- The Controller has not appointed a data protection officer, as there is no obligation to do so.
2. Data processed
- Account data: name, e-mail address, password hash, interface language, date of e-mail address confirmation, time of last activity and, if the User turns on two-step verification, its encrypted key and recovery codes.
- Billing data: Stripe customer ID, Plan and subscription status, and the time at which, when ordering, the User accepted the Terms and requested that the service start before the end of the withdrawal period (recorded with the subscription in Stripe). Payment card data and payment documents are kept by Stripe; the Controller has no access to full card details.
- AI credits and use of the AI assistant: the AI credit balance history and records of AI tasks: task type, number of credits, token counts and time.
- Content: projects, files, versions and reviewer comments saved in the Account. They may contain personal data if the User puts it there.
- Organisations: the Organisation’s name and logo, the User’s membership and role, invitations (the invitee’s e-mail address, the role, who invited them and when; the invitation link is stored only as a cryptographic hash), the creator and last editor of the Organisation’s projects, AI credits used from the Organisation’s pool by each member, and the list of activity in the Organisation’s projects (section 15). On the Team Plan: the company name and tax identification number given when ordering.
- Requests from the form for training companies: name, company, work e-mail address, website and phone (if given), the description of the course and the message, the language of the page, the time of the request, a cryptographic hash of the IP address and browser information, as well as the status of the request and the Controller’s notes (section 16).
- Contacts with companies: the company’s name, its general e-mail address (e.g. office@, contact@) and website, the page on which the company published that address, a short description of the company’s offer based on its website, the messages sent and received and the status of the contact, e.g. consent to commercial information or a request not to be contacted (section 17).
- Technical data: IP address and browser information recorded in server logs, and session data.
- Event log: sign-ins (including failed ones – the e-mail address typed is then recorded only partly masked and as a cryptographic hash), sign-outs, changes of the password, e-mail address and two-step verification, deletion of the Account, use of promotional codes, subscription changes and every action of the Controller concerning the Account – with the time of the event, the IP address and browser information.
- Log of sent e-mails: recipient, subject, type of message and time of sending (without the content of the message).
- Correspondence: e-mails sent to the Controller (e.g. questions, complaints, withdrawal statements, notices of unlawful content) together with the sender’s data.
3. Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Concluding and performing the contract: maintaining the Account, the editor and storage of projects, import and export, the AI assistant, Plans and AI credits, handling payments and subscriptions, Account-related e-mails (e.g. e-mail address confirmation, password reset, confirmation of the contract, notice of changes to the Terms) | Article 6(1)(b) GDPR – performance of a contract and steps taken before entering into it |
| Complying with legal obligations, in particular recording and keeping payment documents for tax purposes, recording the request that the service start before the end of the withdrawal period, handling complaints, withdrawal statements and notices of unlawful content | Article 6(1)(c) GDPR in conjunction with tax law, the Polish Act on consumer rights and the Digital Services Act |
| Support and Account administration: resolving problems reported by the User (including viewing the Account and projects at the User’s request), billing matters, granting AI credits and Plans, promotional codes | Article 6(1)(b) GDPR – performance of a contract |
| Security of the Service and abuse prevention (server logs, the event log, the log of sent e-mails, protection against attacks and circumvention of limits, blocking Accounts that breach the Terms) | Article 6(1)(f) GDPR – the Controller’s legitimate interest in keeping the Service secure |
| Establishing, exercising or defending legal claims | Article 6(1)(f) GDPR – the legitimate interest in protecting the Controller’s rights |
| Simple, aggregated statistics of use of the Service (e.g. number of projects, AI credit usage) used to maintain and develop it | Article 6(1)(f) GDPR – the legitimate interest in developing the Service |
| Replying to messages not related to a contract | Article 6(1)(f) GDPR – the legitimate interest in conducting correspondence |
| Organisations: the shared library of projects, invitations, roles, the pool of AI credits and storage, billing of the Team Plan | Article 6(1)(b) GDPR – performance of the contract with the User; for members acting on behalf of a company also Article 6(1)(f) GDPR – the Organisation’s legitimate interest in organising the team’s work |
| The list of activity in the Organisation’s projects shown to its Owner and Admins | Article 6(1)(f) GDPR – the Organisation’s legitimate interest in overseeing its projects, Seats and billing |
| Answering a request sent with the form for training companies and moving a course for free | Article 6(1)(b) GDPR – steps taken at the request of the data subject before entering into a contract; for a person acting on behalf of a company – Article 6(1)(f) GDPR, the legitimate interest in answering a company’s enquiry |
| Statistics of visits to the Service’s website (Google Analytics): which pages are visited, where visitors come from and how they use the site | Article 6(1)(a) GDPR – consent given in the cookie banner (section 10) |
| Measuring the Service’s ads and showing ads to people who visited the site (Google Ads) – when the Controller runs Google ad campaigns | Article 6(1)(a) GDPR – consent to marketing cookies given in the banner (section 10) |
| Contacts with companies: one question whether the company wishes to receive information about the Service, at most one reminder and further correspondence, and – after consent – information about the Service (section 17) | Article 6(1)(f) GDPR – the Controller’s legitimate interest in establishing business contacts with companies; commercial information by e-mail only with the recipient’s consent (Article 10 of the Polish Act on Providing Services by Electronic Means, Article 398 of the Polish Electronic Communications Law) |
The Controller does not send newsletters. To Users it sends only messages related to the Account and the service provided, and it sends commercial information by e-mail only to people and companies that have agreed to it (section 17). Usage statistics of the Service (e.g. the number of projects) are produced from data stored in it. Google’s analytics and advertising tools run on the Service’s website only after consent (section 10); the editor does not use them.
4. Whether providing data is required
Providing data is voluntary but necessary to conclude and perform the contract: without a name, an e-mail address and a password an Account cannot be created, and without payment details a Paid Plan cannot be bought. Technical data is collected automatically when the Service is used.
5. AI assistant
- When a User runs an AI assistant task, the Controller’s server sends the content of the task to OpenAI through the API: the prompt, the selected text and the attached source files. OpenAI processes this data on behalf of the Controller as a processor.
- Requests are sent with storage of responses turned off. Under OpenAI’s policies, data sent through the API is not used to train models by default, and OpenAI may keep it for up to 30 days to detect abuse (OpenAI’s policy).
- The Controller does not keep prompts or source files after a task is completed – only what the User saves in the project remains. Only usage data is recorded: task type, number of credits, token counts and time.
- Personal data of other people should not be sent to the AI assistant unless it is needed, and especially not special categories of data (e.g. health data).
6. Recipients of data
Data may be disclosed to the following recipients:
- Hosting: the Service’s server is currently operated by the Controller. If the Controller uses an external hosting or infrastructure provider, that provider processes data on behalf of the Controller as a processor (Article 28 GDPR).
- E-mail delivery provider – delivers system messages (e.g. e-mail address confirmation, password reset, confirmation of the contract, invitations to Organisations) as well as requests from the form for training companies and their confirmations, and correspondence with companies (section 17); a processor.
- OpenAI (USA) – performs AI assistant tasks; a processor.
- Stripe Payments Europe, Limited (Ireland) – processing of payments, subscriptions and the billing portal. Stripe also processes payment data as an independent controller, in particular to comply with its own legal obligations and to prevent fraud (Stripe’s privacy policy).
- Google Ireland Limited (Ireland) – Google Tag Manager and Google Analytics and, after consent to marketing cookies, Google Ads; only after consent is given in the cookie banner (section 10). For Google Analytics, Google processes data on behalf of the Controller as a processor; for its advertising services it acts as an independent controller (Google’s privacy policy, Google’s business data privacy terms).
- Public authorities – where disclosure is required by law.
The sub-processors within the meaning of the data processing agreement (Annex 2 to the Terms of Service), that is the providers that may have access to data contained in projects, are: the hosting provider (if the Controller uses one) and OpenAI. The Controller informs the Customers referred to in that Annex by e-mail at least 14 days in advance of any intended addition or replacement of a sub-processor.
7. External services your browser connects to
- Pixabay: when the User uses the image search, their browser connects directly to pixabay.com using the User’s API key. Pixabay receives the IP address, browser data and search terms and processes them under its own policy (Pixabay’s privacy policy). The Controller does not send any data to Pixabay.
- YouTube: when a course contains a YouTube video, the browser loads the player from youtube-nocookie.com (privacy-enhanced mode). Google then receives the IP address and browser data and processes them under its own policy (Google’s privacy policy).
In this respect, Pixabay and Google act as independent controllers.
8. Transfers outside the European Economic Area
- OpenAI processes data in the USA, Stripe may transfer data to Stripe, Inc. in the USA, and Google to Google LLC in the USA. Transfers are based on the European Commission’s adequacy decision for the EU–US Data Privacy Framework (Commission Implementing Decision (EU) 2023/1795) – for certified entities – or on standard contractual clauses adopted by the European Commission (Commission Implementing Decision (EU) 2021/914), in accordance with Articles 45 and 46 GDPR.
- If another processor transfers data outside the EEA, it does so only on the same bases.
- A copy of the safeguards applied can be obtained by writing to the Controller.
9. Retention periods
- Account data, Content, AI credit history and AI task records – until the Account is deleted. The User can delete the Account at any time on the account page; projects and files are then deleted at once, and database backups are overwritten within 7 days.
- Payment documents and records – 5 years from the end of the year in which the payment was made (tax law).
- Server logs – up to 30 days.
- Event log and log of sent e-mails – 12 months from the event; older entries are deleted automatically every day. Entries about a deleted Account (including the entry recording its deletion) stay in the log until that period ends.
- Data needed to establish, exercise or defend legal claims (e.g. correspondence about complaints, the record of statements made when ordering) – until the limitation period for those claims expires.
- Session data – until sign-out or expiry of the session; information stored in the browser – as described in section 10.
- Data in Google Analytics – no longer than 14 months from collection. Withdrawing consent stops further collection.
- Organisation data – until the Organisation is deleted; membership – until the member leaves or is removed. An invitation that is not accepted expires after 7 days. The list of activity is built from the event log and kept like it (12 months).
- Requests from the form for training companies – 12 months from the last contact about the request; requests that ended without working together are then deleted automatically. If a request leads to a contract, the data is further processed under the rules for Accounts and billing.
- Contacts with companies – 12 months from the last message; if the conversation leads to a contract – under the rules for Accounts and billing. After an objection, a refusal or a request not to be contacted, the Controller deletes the other data and keeps only the e-mail address with the date of the objection, so as not to write again; the address is not used for any other purpose.
10. Cookies and browser storage
The Service stores in the browser information that is strictly necessary to provide the service the User is using and, on the Service’s website and only with consent, Google’s analytics and marketing cookies:
| Name | Type | Purpose | Retention |
|---|---|---|---|
| Session cookie | cookie | keeping the session, including sign-in | until sign-out or expiry of the session after a period of inactivity |
| XSRF-TOKEN | cookie | protecting forms against CSRF attacks | same as the session cookie |
| remember_web_… | cookie (only if “Keep me logged in on this computer” is selected when signing in) | keeping the User signed in between visits | until sign-out, no longer than 400 days |
| Local storage (localStorage) | browser storage | interface language, editor preferences and – if the User enters it – their Pixabay API key | until the User deletes it in the browser |
| scormbee_consent | cookie | remembering the choice made in the cookie banner | 12 months |
| _ga, _ga_… | Google Analytics cookie (only with consent to analytics cookies) | telling visitors and visits apart in statistics | up to 2 years |
| _gcl_au and other Google Ads cookies | cookie (only with consent to marketing cookies) | measuring ads and targeting them | up to 90 days; cookies stored on Google’s domains – under Google’s rules |
The session cookie, XSRF-TOKEN, remember_web_…, scormbee_consent and local storage are strictly necessary to provide the service requested by the User, so storing them does not require consent (Article 399 of the Polish Electronic Communications Law of 12 July 2024). They can be deleted or blocked in the browser settings, but sign-in and the editor will then not work properly.
Google’s scripts (Google Tag Manager, Google Analytics, Google Ads) are loaded, and their cookies stored, only after consent is given in the banner shown on the first visit; until then the browser does not connect to Google for this purpose. The browser then sends Google the IP address, browser and device data, the address of the page visited, the referring page and the identifiers stored in the cookies. Consent can be changed or withdrawn at any time through the “Cookie settings” link in the site footer; withdrawing it deletes Google’s cookies of that category and does not affect the lawfulness of processing carried out before the withdrawal. Pages whose address contains a confidential link (e.g. setting a new password, an invitation to an Organisation) do not load Google’s scripts. The editor does not use analytics or advertising tools.
A YouTube player embedded in a course (section 7) operates under Google’s rules and may store its own information in the browser.
11. Rights of data subjects
- Every person whose data is processed has the right to:
- access the data and receive a copy of it (Article 15 GDPR);
- rectification (Article 16 GDPR) – the name and e-mail address can also be changed on the account page;
- erasure (Article 17 GDPR) – among other things by deleting the Account;
- restriction of processing (Article 18 GDPR);
- portability of data processed by automated means on the basis of a contract (Article 20 GDPR) – projects can also be exported at any time;
- object to processing based on legitimate interests, on grounds relating to their particular situation (Article 21 GDPR).
- To exercise these rights, it is enough to write to [email protected]. The Controller replies without undue delay and within one month at the latest; where justified, this period may be extended by two further months. The Controller may ask for information needed to confirm identity (e.g. a message sent from the Account’s e-mail address).
- Only the use of Google Analytics and Google Ads on the Service’s website is based on consent within the meaning of the GDPR (sections 3 and 10). Consent can be withdrawn at any time through the “Cookie settings” link in the site footer, without affecting the lawfulness of processing carried out before the withdrawal. The box ticked in the form for training companies confirms the request to be contacted about it; the legal bases are described in section 3. Consent to receive commercial information by e-mail (section 17) is the consent required by the Polish Act on Providing Services by Electronic Means and the Electronic Communications Law; it can be withdrawn at any time by replying to the message or writing to [email protected].
- Every person whose data is processed has the right to lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warsaw, Poland, uodo.gov.pl) or with the supervisory authority in the EU Member State of their habitual residence or place of work.
12. Automated decision-making
The Controller does not make decisions based solely on automated processing, including profiling, that would produce legal effects concerning anyone or similarly significantly affect them (Article 22 GDPR).
13. Security
The Controller applies technical and organisational measures appropriate to the risk, in particular: passwords are stored only as hashes, connections to the Service are encrypted (HTTPS), each User has access only to their own projects and to their Organisation’s projects within their role, course sources stored in exported Packages are encrypted, and data is backed up every day. The User can turn on two-step verification (a code from an authenticator app) on the account page.
The Controller’s access to Accounts and Content.
- The Controller does not look at Accounts or Content routinely or on its own initiative. It may access Account data and Content (including seeing the Account and its projects the way the User sees them – “viewing the account”) only when this is needed to provide support at the User’s request, to resolve billing matters, to protect the security of the Service and handle reports of breaches (e.g. unlawful content), or to comply with a legal obligation.
- Only the Controller and persons it authorises, who are bound by confidentiality, have this access – always after signing in with two-step verification. Viewing an account ends by itself after 60 minutes, and while it lasts no payments, Account settings changes or AI assistant tasks are possible.
- Every such access and every action of the Controller on an Account (e.g. viewing the account together with the projects opened, granting AI credits, changing the Plan, cancelling a subscription, blocking or deleting the Account) is recorded in the event log: who, when, what it concerned and why. The log is kept for 12 months (section 9). The User may ask whether and when the Controller accessed their Account (section 11).
14. Learner data and data of other people in projects
- Exported courses run in the User’s LMS or on the User’s website and send no learner data to the Service. Dynamic SCORM packages fetch the latest published version of the course from the Service at launch; that request carries only the course channel’s identifier and technical browser data (IP address, the LMS page’s address), which the Controller uses only to deliver the course, prevent abuse and count launches. Learner data (e.g. names, results) stays in the User’s LMS; the User is its controller, and the Controller does not process it.
- If the User puts personal data of other people in projects in connection with their business or professional activity (e.g. names or photos of employees), the User is the controller of that data and is responsible for having a legal basis for processing it. The Controller processes such data on the User’s behalf as a processor, only to provide the service, under the data processing agreement (Annex 2 to the Terms of Service). This Policy does not cover that processing.
15. Organisations
- Members of an Organisation see each other’s names, e-mail addresses and roles and, for the Organisation’s projects, who created them and who last changed them. Members see the content of the Organisation’s projects according to their roles.
- The Owner and Admins of an Organisation see a list of members’ activity in the Organisation’s projects: joins and leaves, role changes, invitations, projects created, deleted and moved, exports, Dynamic SCORM publications and changes of the number of Seats – with the date and the person who did it. They also see how many AI credits from the Organisation’s pool each member used. They do not see members’ personal projects.
- An invitation contains the invitee’s e-mail address, which the Admin uses to send the invitation e-mail. The invitation link is valid for 7 days and is stored only as a cryptographic hash.
- The company name and tax identification number given when ordering the Team Plan are sent to Stripe and appear on the payment documents.
- For personal data put into an Organisation’s projects, the controller is the entity on whose behalf its Owner acts, and the Controller processes it under the data processing agreement (section 14 point 2).
16. The form for training companies
- The Controller uses the data from the form “We’ll move one of your courses for free” only to answer the request, to prepare the free move of the course and to discuss working together. The request goes to [email protected], and the sender receives a confirmation by e-mail. The Controller does not send newsletters or other marketing messages to that address.
- The name, company, e-mail address and description of the course are needed to handle the request; the website, phone and message are optional. The form does not accept files.
- The IP address is stored only as a cryptographic hash, to limit abuse (a limit on requests from one address and for one e-mail address).
- Retention is described in section 9. The sender may ask at any time for the request to be deleted or object to its processing (section 11).
17. Contacts with companies
- The Controller may write to a company whose publicly available offer suggests the Service may be useful to it, e.g. a company selling online training. It uses only general e-mail addresses published by the company on its website (e.g. office@, contact@), not the personal addresses of its employees.
- The data comes from the company’s publicly available website; its scope is described in section 2.
- The first message only asks whether the company wishes to receive information about the Service. If the company does not reply, the Controller sends at most one reminder and then does not write again. It sends commercial information only after the recipient’s consent.
- Every message says where the address comes from and how to object. It is enough to reply “no” or write to [email protected]; the Controller will not get in touch again (sections 9 and 11).
- A general company address that does not identify a natural person is not personal data; the Controller nevertheless applies the same rules to all addresses.
- The data is not disclosed to anyone other than the e-mail service provider (section 6).
18. Changes to this Privacy Policy
This Policy may change, e.g. when the law, the features of the Service or its providers change. The Controller informs Users of material changes by e-mail before they take effect. The current version, with its effective date, is always available on this page.