1. Controller and contact
The controller is IVAN-OLEKSANDR Yakymiv Centrum Szkoleń, operating as STC Academy, ul. Żubrza 16 lok. 1, 54-229 Wrocław, Poland; NIP 8943278173, REGON 543837967. Portal: academy.org.pl; operator website: stc.enterprises.
Data enquiries: rodo@academy.org.pl. General contact: info@academy.org.pl; account support: support@academy.org.pl; telephone +48 800 003 181. IPHI, IBRO, ISDIC, CODI and the Just Do It Support Centre Association do not become controllers of account data solely through academic cooperation.
2. Data categories and sources
Data comes from you through your profile, course choices, lesson markers and correspondence, and from your chosen authentication provider. Infrastructure also processes connection data. Browsing the public catalogue does not require an account.
Current account forms do not require a Polish PESEL number, date of birth, home address, identity scan or health data. Psychology and health courses are educational; accounts are not intended to collect diagnoses or medical histories. Exercise answers remain with you: current introductions have no assignment-upload form.
You may optionally add your own profile photo, telephone and postal address: recipient, street and building / apartment, second address line, postal code, city and country. The photo personalises your account; contact details support communication and agreed paper-document delivery. Saving an address does not order delivery. These details are not published in the certificate register. Photos are accessible and removable only through your own account. Replacing or removing a photo updates the record and deletes the previous stored file.
3. Google, LinkedIn and existing sign-in
Google and LinkedIn use OAuth 2.0 / OpenID Connect. Each method’s availability is displayed on the sign-in page. A method awaiting launch is not an active connection. Selecting an enabled method takes you to the provider for authentication.
The portal requests openid, profile and email scopes. It uses the provider’s account identifier (sub), provider name and, where supplied, your full name and email. Tokens can also contain issuer, audience, expiry and authentication information and basic profile attributes. The implementation does not store or display profile photographs or use extra attributes for marketing profiles.
These scopes do not grant access to Gmail, Drive, calendars, contacts, LinkedIn messages, connections, employment history or posting on your behalf. STC Academy never receives your provider password. Provider tokens are used to confirm sign-in and are not stored in the database as continuing access to your services.
Accounts are linked by provider identifier, not email similarity. Adding another method requires an action from an authenticated profile and preserves learning and documents. Provider sign-in demonstrates control of that provider account, not official identity, qualifications or employment.
Where existing ChatGPT access is available, it supplies user ID, email and the provided name for the same account functions. It does not give the Academy access to your private ChatGPT conversations.
You may choose an available method, but account features require successful authentication. Authorising profile sharing is not marketing consent. Account processing is based on service performance, not compulsory consent to the whole policy. Revoking provider permissions does not itself delete the Academy account or earlier documents.
4. Purposes, legal bases and retention
The table separates service delivery, legal obligations and legitimate interests. We do not apply a single indefinite retention period to everything. When a purpose ends, data should be deleted or effectively anonymised unless a separate basis requires a necessary subset to remain.
| Purpose and data | Legal basis | Retention period / criterion |
|---|---|---|
| Account creation, sign-in and materials: user ID, provider, email, profile name and session data. | GDPR Article 6(1)(b): performance of the electronic service contract or requested pre-contractual steps. | While the account and service remain active; afterwards only data needed for specific legal duties or claims. |
| Learning: course and lesson IDs, enrolment date, completion markers and activity dates. | Article 6(1)(b): delivery of platform and educational services. | While the account and material access are maintained; afterwards only records necessary for service documentation or claims. |
| Issuing and verifying documents: participant name, document number, course, type, date and status. | Article 6(1)(b): document delivery; (f): legitimate interests in authenticity and fraud prevention. Paragraph (c) applies only where a specific law requires retention. | For the documentation and verification service; subsequently only as required by law or necessary for claims. Deletion requests require a separate review of the registry entry. |
| Enquiries, support and complaints: contact details, correspondence and information needed to resolve the matter. | Article 6(1)(b) for contractual matters and pre-contractual requests; (f) for other correspondence and claims; (c) for applicable statutory duties. | Until the matter is resolved, then as needed to evidence its handling and until the applicable limitation period expires. |
| Security and availability: session data, IP address, browser information, request times and errors processed by infrastructure. | Article 6(1)(f): account protection, abuse detection, diagnostics and availability. | Until diagnostic or security needs end, taking the provider’s log cycle into account; incident data until investigation and related claims are resolved. |
| Data rights and compliance: requests, proportionate identity checks and handling records. | Article 6(1)(c): controller obligations, particularly GDPR Articles 12–22. | During handling and as long as necessary to demonstrate compliance and address claims. |
| Optional profile and agreed document delivery: your own photo, telephone and postal address. | GDPR Article 6(1)(b): user-requested profile functions and agreed document delivery service. | Until you remove or replace the data, close the account or the agreed delivery need ends; any further necessary retention requires a relevant legal basis. |
5. Certificates, statements and public verification
Documents belong to the account holder and contain data needed for their particular purpose. Current participation statements concern three introductory lessons; full-course document samples are not issued participant documents. Profile name changes do not automatically amend earlier documents; request corrections from the operator.
An exact number returns the number, course subject, type, issue date and registry status, not participant name or email. Full documents are available to their owner. If you share a document, its recipient will see its contents.
NFC protection applies only to paper certificates issued by the Academy if that format is launched. Its verification token links to the document number and follows registry protection rules. The current demonstration sample has no active chip or token. Actual operation must be explained before such documents are issued.
6. Recipients
Authorised staff and necessary service providers may access data: OpenAI / ChatGPT Sites publication infrastructure, Cloudflare hosting and databases, and home.pl email services. Roles depend on the service. Processors operate within the entrusted service and applicable processing terms; sign-in providers also act as independent controllers for their own services.
Where necessary, legal advisers, claims-support providers and legally authorised authorities may receive data. Institute experts may access only what an agreed course or assessment requires, under an appropriate basis and access rules. A course’s institute label does not grant access to the participant database.
The site currently loads fonts from Google Fonts. Google receives technical request data, including IP and browser information. This does not disclose the learner or document database. Linked external websites apply their own privacy rules.
7. Transfers outside the EEA
Global providers may process data outside the European Economic Area, particularly in the USA. We do not claim every operation and copy stays only in Poland or the EU. Contact rodo@academy.org.pl for recipients and safeguards applicable to a particular service.
Transfers may rely on an applicable European Commission adequacy decision. The EU–US Data Privacy Framework covers only organisations with the relevant certification and processing scope. Otherwise, GDPR Chapter V safeguards, such as standard contractual clauses with transfer assessment and additional measures where required, apply. Using a provider or accepting this policy does not replace a lawful transfer basis.
8. Cookies, language and sessions
__Host-stc_session maintains Google / LinkedIn sign-in for up to 7 days. The database stores a hash of the random session token, not its plain value. __Host-stc_oauth_google and __Host-stc_oauth_linkedin protect an initiated sign-in for up to 10 minutes and are removed when the portal finishes or handles cancellation. Authentication cookies use Secure, HttpOnly and SameSite=Lax.
stc_locale remembers the selected language for up to one year. The lang URL parameter can also specify it. This setting contains no profile or learning history. Change it using the selector or clear it in your browser.
Technologies necessary for the requested service are used within Article 399 of the Polish Electronic Communications Law. The portal code currently does not run its own advertising pixels, Google Analytics or cross-site marketing tracking. Future optional technologies require separate information and prior consent where legally required. Infrastructure and sign-in providers may operate their own session and security mechanisms under their service terms.
9. Rights and requests
Subject to GDPR conditions, you may access and obtain copies, rectify, erase or restrict data, and obtain portability where automated processing relies on consent or contract. You may object to legitimate-interest processing for reasons relating to your particular situation. Objection to direct marketing is unconditional.
Where a specific operation relies on consent, withdrawal does not affect earlier lawful processing. Erasure is not absolute: data necessary for a legal duty or establishing, exercising or defending claims may remain after an account-closure request.
Send requests to rodo@academy.org.pl. We may verify identity proportionately, for example through the account email, without routinely requiring an identity scan. We respond without undue delay, normally within one month. Complex or numerous requests may require two additional months; reasons and notice are provided within the first month. Requests are generally free, subject to GDPR exceptions.
You may complain to Poland’s supervisory authority, the President of UODO: uodo.gov.pl. Contacting the Academy first is not a condition for complaining.
10. Security, profiling and children
Measures include HTTPS, provider-token signature verification, time-limited sessions, account access controls and restricted public verification. No internet channel offers absolute security. Do not share sign-in codes or send sensitive information that is unnecessary for your enquiry.
We do not make solely automated decisions with legal or similarly significant effects under GDPR Article 22. Calculating progress and checking participation-statement conditions are not professional assessments or employment / qualification decisions. We do not conduct marketing profiling.
Standard independent accounts are intended for adults. A minor’s participation requires separate arrangements with the operator and an appropriate legal basis. Do not create a child’s account without authority. The current form has no parental-consent mechanism.
11. Changes and new features
This policy covers the described portal functionality. Before sales, new payments, newsletters, extra analytics, assignment assessment or actual NFC handling begin, we provide information appropriate to the new processing and obtain required consents. Registration or purchase is not marketing consent.
The current version and date appear here. Material changes for existing accounts are communicated through the portal or an appropriate channel. Policy updates do not automatically expand data categories, provider permissions or consent.
Questions about your personal data?
Email rodo@academy.org.pl. Describe your request and identify the relevant account or document if necessary. Do not send your password or an identity-document scan.
rodo@academy.org.pl