endoskopia.eu

Privacy policy

Information about personal data processing on Endoskopia.eu.

Last updated:

1. Data controller and contact

The controller of personal data processed in connection with the use of Endoskopia.eu is the Endoscopic Surgery Section of the Association of Polish Surgeons in Kraków, with its registered office at: Specialist Hospital in Brzeziny ul. Marii Skłodowskiej Curie 6, 95-060 Brzeziny, contact email: schetp@gmail.com. The Section is referred to below as the Controller.

For data protection matters, questions about processing and rights requests, contact the Section using the contact details or form published on the Contact page of Endoskopia.eu.

2. Browsing the website

Delivering the website requires processing technical data, such as an IP address and information about requests and the browser. These support website operation and security. Hosting is provided by Firebase; images and files may be retrieved from Sanity's CDN. Connections to these services transmit the data their operators need to handle the request.

Browsing content does not require a public account. Google sign-in is used for the administration panel to check access to submissions. The panel's browser session is held in memory and ends when the panel is left or after 15 minutes of inactivity; this does not delete the authentication provider's account.

3. Data in applications

Course, examination and membership forms include first name, surname, email, telephone number, professional licence number, specialisation, workplace, academic title, membership of the Association of Polish Surgeons and additional information. We also record the application type and reference, chosen offering and edition, date, and separate delivery states for the staff notification and the applicant's receipt.

Academic title and additional information are optional. Omitting fields required by the form prevents submission. Data is stored in Firestore and made available to authorised staff in the secured panel. The registration team receives an email containing the complete application: first name, surname, email, telephone number, professional licence number, specialisation, workplace, academic title, membership of the Association of Polish Surgeons and additional information, together with the application type, reference, date, selected offering and edition where applicable, and a panel link. The applicant receives a separate brief receipt without a copy of their contact or professional details or additional information. Please do not enter patient data, health information or unnecessary third-party personal data.

4. Purposes and legal bases

Handling course and examination applications and organisational communications relies on Article 6(1)(b) GDPR to the extent necessary to take steps requested by the applicant before entering into a contract or to perform that contract. Considering membership applications and communicating about membership serves the Controller's legitimate interest in organising the Section's activities and handling membership enquiries, under Article 6(1)(f) GDPR.

Responding to enquiries, maintaining website security, checking staff access rights and preventing abuse serve the Controller's legitimate interests under Article 6(1)(f) GDPR. This basis also covers establishing, pursuing or defending legal claims where necessary. Processing for optional analytics and the embedded map relies on consent under Article 6(1)(a) GDPR; these choices are made separately in the cookie panel.

Submitting an application does not constitute consent to analytics or marketing. Forms do not require confirmation of data accuracy or acceptance of the privacy policy. Information about data processing is available alongside the form. Accepting an application does not depend on enabling optional services.

5. Contact and form security

The contact form submits the supplied name, email address, subject and message to the Controller's server. After validation and security checks, the message is stored in a private Firestore queue and then sent through the Gmail API to website staff. The user's address is used for replies; the message is sent by the Controller's authorised mailbox. Acceptance confirms that the message was saved for handling, rather than confirming email delivery. Where an enquiry concerns steps before entering into a contract or its performance, necessary handling may rely on Article 6(1)(b) GDPR; other enquiries are handled under Article 6(1)(f) GDPR.

Application and contact forms are protected by Cloudflare Turnstile, which receives connection and browser data and a verification token during checks. The Controller limits attempts and repeated messages using cryptographic hashes of the network address, email and form data. The hashes are used to compare attempts and detect repetitions; they are security data rather than an anonymous activity record.

6. Cookies and consent management

Consent choices are managed through CookieScript. Optional services are disabled by default and require an explicit choice in the panel. They remain disabled if the panel is unavailable or there is no valid choice. Storing preferences and mechanisms necessary for a requested service are separate from optional analytics and the map.

You can change or withdraw your choices through the Cookie settings button, which reopens the panel. Withdrawal does not affect the lawfulness of processing based on consent before it was withdrawn. Storing or reading optional cookies and enabling optional services requires prior consent. Personal data processing based on that consent relies on Article 6(1)(a) GDPR. Cookie categories and the current choice are available in the CookieScript panel.

7. Analytics and Google Maps

Consent to the Performance category in CookieScript allows Google Analytics statistics to be enabled through Firebase when the service is available for this website. Analytics is used to assess website usage, including page views; it may include browser identifiers and information about devices and website usage events. Withdrawing consent disables further analytics collection by the website. Advertising storage, advertising user data and ad personalisation remain disabled.

The embedded Google Maps map is external content assigned to the Targeting category in CookieScript. It loads after consent to that category; Google then receives connection data and may use identifiers under its own policies. Without consent, the address and a map link remain available. The category's name does not enable advertising or a newsletter and does not constitute consent to marketing messages.

8. Service providers and recipients

The Controller uses Google/Firebase and Google Cloud for hosting, server functions, Firestore and authentication; the Gmail API for notification emails; Cloudflare Turnstile for form protection; Sanity for content and files; and CookieScript for consent management. Google Analytics and Maps operate according to the choices described above. Application data is stored in Firestore, not in the Sanity CMS.

Course, examination and membership application contents are available to the Controller's authorised staff in the secured administration panel and in a complete email notification to registration staff. The notification includes the contact and professional details and additional information supplied in the form, as well as the application type, reference, date and selected offering and edition where applicable. Contact form emails include the name, email address, subject and full enquiry so staff can reply. The receipt sent to the applicant's address includes the reference, date and application type, and the offering and edition where applicable; it does not include a copy of the applicant's profile, the enquiry text or a panel link. Data in notifications and correspondence is also handled by the sender's and recipient's email providers. Infrastructure providers and their subcontractors receive the data needed to deliver the services used.

9. Transfers outside the EEA

Using the providers listed above may involve processing data outside the European Economic Area, including in the United States. This concerns infrastructure used to deliver the website, authenticate users, protect forms, handle messages and provide optional services.

Information about recipients and processing countries, the bases and safeguards for transfers, and how to obtain a copy of the relevant safeguards is available from the Controller using the contact details at the beginning of this policy.

10. Retention periods

Course and examination application data is retained for the time needed to consider the application, provide organisational communications and handle participation in the relevant edition. Membership application data is retained while the application is being considered and, after acceptance, to the extent needed to administer membership. For rejected or withdrawn applications, the criterion is completion of their handling and related correspondence. Longer retention is limited to data needed to meet applicable legal obligations or establish, pursue or defend claims, for the period required by those obligations or necessary for the claims concerned.

Correspondence and notification copies are retained for the time needed to resolve and document the matter, taking account of the obligations and claims described above. Technical data used to protect the website is retained for the time needed to prevent abuse, investigate incidents and maintain security. Attempt counters and duplicate-detection records have short validity windows; their expiry does not delete an application. Cookie categories and the current choice are available in the CookieScript panel. Withdrawing consent stops further collection by the optional service; it does not itself confirm deletion of previously collected data. Requests for erasure may be sent to the Controller.

11. Your rights and requests

Subject to the GDPR, you have rights of access, rectification, erasure and restriction of processing. The right to portability concerns data you provided to the Controller that is processed by automated means on the basis of consent or a contract. You may object to processing based on legitimate interests on grounds relating to your particular situation. Consent may be withdrawn at any time. The scope of these rights depends on the processing purpose and legal basis. You may lodge a complaint with the President of Poland's Personal Data Protection Office.

Address requests to the Controller using the contact details at the beginning of this policy, describing what you request and providing, for example, an email address or application reference. If there are reasonable doubts about identity, the Controller may request additional information necessary to confirm it. A response is provided without undue delay, normally within one month of receiving the request. Complex or numerous requests may require a two-month extension; the Controller gives notice of the extension and its reason during the first month.

12. Automation and policy changes

The website has no profiling function or automated decision on admission to a course, examination or membership. Safeguards may reject a submission attempt as spam or when a limit is exceeded; they do not replace the organiser's decision. This policy is updated when processing changes. A material change to optional-service purposes may require a new consent choice; an earlier choice does not automatically cover a new purpose.