Privacy Policy | BezpiecznaKancelaria.pl

This Privacy Policy describes how Aurea Enterprises sp. z o.o., with its registered office at ul. Plac Bankowy 2, 00-095 Warsaw, NIP: 9591956107, KRS: 0000510950, hereinafter referred to as the "Controller", "we" or "Bezpieczna Kancelaria", processes personal data in connection with the use of the bezpiecznakancelaria.pl website and the Bezpieczna Kancelaria application.

For matters concerning personal data protection, you may contact us at the following e-mail address: privacy@bezpiecznakancelaria.pl.

1. What Bezpieczna Kancelaria is

Bezpieczna Kancelaria is a SaaS system intended for law firms and other professional entities, used, among other things, to manage cases, documents, recordings, transcripts, calendars, user permissions, communications, invoicing and integrations with external services.

Bezpieczna Kancelaria is not a law firm and does not provide legal services to law firms' end clients. Legal services are provided by the law firm or other entity using the system.

2. Our roles in data processing

Depending on the type of data, we perform different roles.

2.1. We are the data controller

We are the controller of personal data with respect to data processed for the purposes of:

operating the website,
creating and servicing user accounts,
entering into and performing agreements with clients,
processing payments and invoices,
handling business contacts and enquiries,
providing technical support,
ensuring application security,
conducting marketing activities concerning our services,
pursuing or defending against claims.

Within this scope, we determine the purposes and means of data processing.

2.2. We are the processor of client data

With respect to data entered into the system by a law firm or another client, such as case files, documents, law firm client data, recordings, transcripts, notes, messages, calendar data, invoice data, integration data and other content stored in the system, we generally act as a processor processing data on behalf of the client.

This means that the controller of such data is the client using Bezpieczna Kancelaria, for example, a law firm, and we process such data solely for the purpose of providing the service, in accordance with the agreement, terms and conditions, data processing agreement and the client's instructions.

If you are a client of a law firm using Bezpieczna Kancelaria and wish to exercise your rights under RODO, please contact that law firm in the first instance. We may assist the law firm in fulfilling such requests, but we do not independently make decisions concerning data contained in case files maintained by the client.

3. What data we process as the controller

As the controller, we may process the following categories of data:

3.1. Account user data

This includes, in particular:

first name and surname,
e-mail address,
telephone number,
name of the organisation or law firm,
position or role within the organisation,
user identifier,
account settings,
information concerning permissions and roles within the system,
login history and security events.

3.2. Contractual and billing data

This includes, in particular:

company or law firm details,
NIP, REGON, KRS, registered office address,
contact person details,
data required to issue an invoice,
payment history,
information concerning the selected package or scope of the service.

3.3. Technical data

This includes, in particular:

IP address,
session identifiers,
browser type and version,
operating system,
device identifiers,
date and time of login,
technical logs,
error logs,
security events,
information concerning the use of system functions.

3.4. Contact and support data

This includes, in particular:

data provided in contact forms,
the content of e-mail messages,
service requests,
communication history,
files or screenshots provided as part of technical support.

Please do not provide sensitive data, case files, recordings or documents containing law firm client data in support requests unless this is necessary to resolve the request and is carried out in accordance with the security procedure.

4. What data may be processed in the system as client data

Law firms and other clients using Bezpieczna Kancelaria may enter various data into the system, including the personal data of third parties. This may include, in particular:

law firm client data,
data of parties to proceedings,
business partner data,
witness data,
data of attorneys-in-fact,
employee and associate data,
data contained in documents and case files,
data contained in audio recordings,
data contained in transcripts,
calendar data,
invoice data,
data from integrations with external systems,
case reference numbers,
information concerning deadlines, activities and tasks.

Such data may also include special categories of personal data, data concerning criminal convictions, prohibited acts, court proceedings, and family, financial, health or professional circumstances, if such data is contained in materials processed by the client.

Within this scope, we are not the controller of such data. The controller is the client using the system, and we process the data solely as a technology service provider.

5. Purposes and legal bases for data processing

5.1. Account creation and servicing

We process data for the purposes of creating an account, authenticating the user, managing access, roles and permissions, and enabling use of the application.

Legal basis: performance of an agreement or taking steps prior to entering into an agreement, Article 6(1)(b) RODO.

5.2. Provision of the Bezpieczna Kancelaria service

We process data for the purposes of providing the service, maintaining system operation, synchronising data, handling integrations, saving user settings and providing the functions selected by the client.

Legal basis: performance of an agreement, Article 6(1)(b) RODO.

With respect to data entered into the system by the client, we process the data as a processor on the basis of a data processing agreement.

5.3. Handling requests and contacts

We process data for the purposes of responding to enquiries, handling forms, conducting correspondence, resolving technical issues and handling complaints.

Legal basis: performance of an agreement or our legitimate interest in handling contacts and providing support, Article 6(1)(b) or (f) RODO.

5.4. Settlements, invoices and accounting obligations

We process data for the purposes of issuing invoices, processing payments, maintaining accounts and fulfilling tax and accounting obligations.

Legal basis: compliance with a legal obligation to which the Controller is subject, Article 6(1)(c) RODO.

5.5. System security

We process technical data and logs for the purposes of ensuring application security, detecting misuse, protecting against unauthorised access, preventing incidents, auditing events and ensuring the accountability of user activities.

Legal basis: our legitimate interest in ensuring the security of the service, Article 6(1)(f) RODO.

5.6. Development and improvement of service quality

We process limited technical, diagnostic and statistical data for the purposes of analysing errors and improving the stability, performance, usability and security of the application.

Legal basis: our legitimate interest in developing and improving the product, Article 6(1)(f) RODO.

Client data stored in documents, files, recordings or transcripts is not used for product development without a legal basis, the client's consent or another express basis arising from the agreement.

5.7. Own marketing

We may process contact data for the purpose of marketing our own products and services, insofar as this is permitted by law.

Legal basis: our legitimate interest, Art. 6(1)(f) RODO, and in cases where consent is required - consent, Art. 6(1)(a) RODO.

Consent may be withdrawn at any time.

5.8. Cookies and analytics

If we use cookies or similar analytics technologies that are not necessary for the operation of the website or application, we do so on the basis of the user's consent.

Consent may be withdrawn or changed in the cookie settings.

5.9. Pursuit of and defence against claims

We may process data for the purpose of establishing, pursuing or defending against claims.

Legal basis: our legitimate interest, Art. 6(1)(f) RODO.

6. File encryption and access to Client content

Bezpieczna Kancelaria has been designed with an emphasis on the confidentiality and security of law firm data.

Each Client file and document stored in the system is stored in encrypted form. Data is also protected during transmission. The encryption and key management mechanism has been designed in such a manner that the content may be decrypted solely by Client users who hold the appropriate permissions for the relevant file.

Neither Bezpieczna Kancelaria administrators nor infrastructure administrators possess keys allowing them to independently decrypt and read the stored content of files. Ordinary administrative, maintenance and technical activities do not provide personnel with access to the unencrypted content of Client documents.

If the Client shares a file with another user within its organisation, access to the decrypted content is obtained solely by the user covered by that permission, in accordance with the roles and access configuration in the system.

We do not ask users to disclose passwords or keys. A user's authentication credentials should remain known solely to that user.

Certain functions intentionally initiated by an authorised user, such as OCR, transcription, AI analysis, content search or export, may require the temporary decryption of a selected file or a fragment thereof. In such a case, processing takes place solely for the period and to the extent necessary to perform the selected function. If the performance of the function requires the use of a subprocessor, only the data necessary for its performance is transferred, in accordance with sections 7 and 9. This does not grant Bezpieczna Kancelaria administrators permanent or independent access to the content of the file.

The above principles apply to file content. Metadata necessary for the operation of the system, such as the file name, its size, owner, permissions, date added and technical information concerning the operation, may be processed separately to the extent necessary to provide the service, ensure security and maintain an event log.

7. Recordings, transcriptions and AI functions

If the Client uses the recording, transcription or AI assistant functions, the following may be processed in the system:

audio files,
recording metadata,
voices of call participants,
transcriptions,
summaries,
notes,
user instructions,
responses generated by the system,
data contained in documents designated for analysis.

These functions are initiated by the Client or user and are used solely to perform the selected function within the system.

If we use external technology providers to perform a function, we do so on the basis of appropriate agreements and safeguards required by RODO. The list of such providers is set out in the list of subprocessors (section "Data recipients").

8. Integrations with external services

Bezpieczna Kancelaria may enable integrations with external services, such as calendars, email systems, invoicing systems, KSeF, court systems or other tools used by the Client.

Data from such integrations is processed solely to the extent necessary for the operation of the function enabled by the Client or user.

The Client or user may be required to grant the appropriate permissions in the external system. The scope of those permissions depends on the specific integration.

8.1. Data from a connected Google account

If a user voluntarily connects their Google account to Bezpieczna Kancelaria, we process data from Google Calendar solely to the extent necessary for the operation of the appointment synchronization function selected by the user.

What data we obtain from Google:

the email address of the Google account, used as a connection identifier,
the list of calendars visible on the connected account, including their names, identifiers, descriptions, locations, time zones, colors, access roles, primary calendar designations, and selection and visibility flags - solely for the purpose of displaying the available calendars to the user, enabling selection, and maintaining the synchronization configuration; we also store the technical calendar list entry record in the form returned by the Google Calendar API,
the complete event record from the Google calendars selected by the user for synchronization and from the BK-LOCAL and BK-PI calendars, in the form returned by the Google Calendar API. Depending on the content of the event, it may include in particular: the event identifier and iCalUID, status, title, description, location, start and end, all-day event designation, recurrence rule, series identifier and original occurrence time, creation and modification dates, etag, organizer email address, link, sequence number, attendees, reminders, video conference data, attachments, extended properties, and other technical information returned by the API. The data is stored both in separate system fields and as a raw JSON event record.

We do not retrieve or store the content of events located in Google calendars that the user has not selected for synchronization. The permissions granted by Google may, depending on the technical scope required by the Google Calendar API, allow the application to access a broader set of calendars; however, Bezpieczna Kancelaria uses them solely in relation to the calendars specified by the user.

For what purpose we use the data:

We use the data solely to provide calendar functions visible to the user. The user independently selects the Google calendars to be synchronized with Bezpieczna Kancelaria. Events from the selected calendars are copied to the application and remain linked to their corresponding events in Google Calendar.

The user may also separately enable the synchronization of Bezpieczna Kancelaria calendars with Google Calendar. After this option is enabled, copies of the following are created and maintained in Google Calendar:

BK-LOCAL - the law firm's local calendar maintained in Bezpieczna Kancelaria,
BK-PI - the calendar of court hearings originating from the integration of Bezpieczna Kancelaria with Portal Informacyjny.

Synchronization is bidirectional. A change made in Bezpieczna Kancelaria to an event from a selected Google calendar is transmitted to Google Calendar. A change made by the user in Google Calendar is retrieved and reflected in Bezpieczna Kancelaria. The function also serves to detect scheduling conflicts and keep appointments up to date in both systems.

We do not use Google data for advertising, marketing profiling, creditworthiness assessment, or any other purposes unrelated to the synchronization function.

To whom we may disclose the data:

The data may be processed by the entities specified in section 9 solely to the extent necessary to provide the function selected by the user, on our instructions and on the basis of appropriate agreements.

The content of events retrieved from Google calendars selected for synchronization is not transmitted to OpenAI. This applies in particular to titles, descriptions, locations, times, organizer data, attendees, attachments, and the remaining content of events. The agenda and the answer to a question about the daily schedule are prepared by our system on the basis of a local copy of the data, solely for a user holding the appropriate permissions. Only technical information concerning the requested date range and the total number of items in the prepared agenda may be transmitted to the AI model, without the content and details of individual events.

If a user creates an event directly in the BK-LOCAL calendar maintained by us on their Google account, the event is imported into Bezpieczna Kancelaria and becomes client content. If the client uses the AI assistant function, the content of such an event - its title, description, location, and time - is automatically prepared for semantic search, which involves transmitting it to OpenAI. It may also be transmitted to OpenAI as part of the context for the assistant's response. The first transmission occurs as part of the operation of the AI function and does not require a question to have first been submitted to the assistant. Events created manually in the BK-PI calendar are not imported into Bezpieczna Kancelaria, indexed, or transmitted to OpenAI.

No transmission to OpenAI occurs if the client does not use the AI function or if the matter linked to the event has been excluded from processing by the assistant. OpenAI processes such data as a service provider acting on our instructions. In accordance with the standard OpenAI API policies, API data is not used to train models unless the organization using the API voluntarily enables data sharing. API inputs and outputs may be stored by OpenAI for up to 30 days for the purposes of providing the service and detecting abuse, unless an approved Zero Data Retention configuration or other shorter retention rules apply to the relevant project.

We do not sell Google data, disclose it to data brokers or advertisers, or make it available to entities that would use it to train or improve their own artificial intelligence or machine learning models.

How we protect the data:

Data transmission is protected using the TLS protocol. The Google refresh token is encrypted using the AES-256-GCM algorithm and linked to a specific user account. Each instance of its decryption is recorded in the audit log. Short-lived access tokens are stored exclusively in the cache, with a lifetime limited to their validity period, which is less than one hour, and are not stored in the main database or in the synchronization queue. Access to tokens is restricted to the technical processes performing authorization and synchronization.

Calendar data is subject to the measures described in this Policy, in particular the segregation of data belonging to individual law firms, role-based access control, and the logging of security events.

Our personnel do not obtain access to the content of Google data, except where this is necessary to handle a user request and takes place with the user's express consent, is necessary for security reasons, or arises from a legal obligation.

How long we retain the data and how we delete it:

We retain OAuth tokens and connection settings for as long as the Google account connection remains active. Disabling synchronization for a specific calendar stops any further retrieval and transmission of changes concerning that calendar.

Disconnecting the Google account in the Bezpieczna Kancelaria settings results in the immediate deletion of the stored refresh token, the configuration and synchronization links, the queue of unsent operations, and local copies of calendars and events retrieved from Google. A short-lived access token present in the cache expires automatically no later than at the end of its validity period, which is less than one hour. Before deleting the connection, the application attempts to delete the BK-LOCAL and BK-PI calendars from the Google account. If Google refuses to perform this operation or if it is technically impossible, the calendars may remain on the Google account and the user may delete them independently.

An event created manually in the BK-LOCAL calendar that was imported into Bezpieczna Kancelaria before disconnection remains a client event in the system and is subject to the general data retention rules described in section 11. Events created manually in the BK-PI calendar are not imported into the system; if that calendar is successfully deleted from the Google account, they are deleted together with it.

The user may disconnect the integration at any time in the Bezpieczna Kancelaria settings or revoke the application's access in their Google account settings. Revoking access on the Google side stops synchronization. Deleting the account in Bezpieczna Kancelaria or terminating the provision of the service results in the deletion or return of data in accordance with the procedure described in section 11.

Limited use of Google data (Limited Use):

The use by Bezpieczna Kancelaria of raw and derived user data received through Google Workspace interfaces complies with the Google API Services User Data Policy, including the Limited Use requirements.

We do not use raw, derived, aggregated, or anonymized Google data to create, develop, train, or improve artificial intelligence or machine learning models. Nor do we disclose such data to entities that would use it for this purpose.

The use of raw or derived user data received from Google Workspace APIs by BezpiecznaKancelaria.pl adheres to the Google API Services User Data Policy, including the Limited Use requirements.

8.2. Data from a connected Apple account and Kalendarz iCloud

If the user voluntarily connects Bezpieczna Kancelaria to Kalendarz iCloud, we process data from that service solely to the extent necessary for the operation of the appointment synchronization function selected by the user.

What data we obtain from Kalendarz iCloud:

the account identifier and technical information necessary to establish and maintain the connection,
the list of calendars available within the connected account, including names, identifiers and basic metadata - solely for the purpose of enabling the user to select calendars for synchronization,
the content and dates of events contained in the calendars selected by the user for synchronization, including the title, description, location, date and time, and recurrence rule.

We do not retrieve the content of events from calendars that the user has not selected for synchronization.

For what purpose we use the data:

We use the data solely to provide calendar functions visible to the user. The user independently selects the iCloud calendars to be synchronized with Bezpieczna Kancelaria. Events from the selected calendars are copied to the application and remain linked to the corresponding events in Kalendarz iCloud.

The user may also separately enable synchronization of Bezpieczna Kancelaria calendars with Kalendarz iCloud. Once this option is enabled, the following copies are created and maintained in Kalendarz iCloud:

BK-LOCAL - the law firm's local calendar maintained in Bezpieczna Kancelaria,
BK-PI - the calendar of court hearings originating from the integration of Bezpieczna Kancelaria with Portal Informacyjny.

Synchronization is bidirectional. A change made in Bezpieczna Kancelaria to an event from a selected iCloud calendar is transmitted to Kalendarz iCloud. A change made by the user in Kalendarz iCloud is retrieved and reflected in Bezpieczna Kancelaria. The function also serves to detect scheduling conflicts and keep appointments up to date in both systems.

We do not use this data for advertising, marketing profiling, creditworthiness assessment or any other purposes unrelated to the synchronization function.

To whom we may disclose the data:

Events retrieved from selected iCloud calendars for the purpose of displaying them in the Bezpieczna Kancelaria calendar grid and detecting conflicts are not transferred to OpenAI.

If the user creates an event directly in the BK-LOCAL or BK-PI calendar maintained by us in the user's Kalendarz iCloud, the event is imported into Bezpieczna Kancelaria and becomes Customer Content. If the customer uses the AI assistant function, the content of such an event - its title, description, location and date - is automatically prepared for semantic search, which involves transferring it to OpenAI. The transfer takes place as part of the operation of the AI function and does not require a question to have first been submitted to the assistant.

No transfer to OpenAI takes place if the customer does not use the AI function or if the matter linked to the event has been excluded from handling by the assistant. OpenAI processes such data as a service provider acting on our behalf; this data is not used to train or improve OpenAI models.

We do not sell data from Kalendarz iCloud, transfer it to data brokers or advertisers, or disclose it to entities that would use it to train or improve their own artificial intelligence or machine learning models.

How we protect the data:

We store authentication data, tokens or other connection secrets required for the operation of the integration in encrypted form and linked to a specific user account. They may be accessed solely by technical processes performing authentication and synchronization. The data is protected during transmission and storage and is subject to the measures described in this Policy.

Our personnel do not obtain access to the content of data from Kalendarz iCloud, except where this is necessary to handle a user's request and takes place with the user's express consent, is necessary for security reasons, or results from a legal obligation.

How long we retain the data and how we delete it:

We retain authentication data and connection settings for as long as the integration remains active. Disabling synchronization for a specific calendar stops any further retrieval and transmission of changes concerning that calendar. Disconnecting Kalendarz iCloud in the Bezpieczna Kancelaria settings results in the deletion of access data and synchronization configuration and stops any further access to data from that service.

Event content that was previously synchronized and stored in Bezpieczna Kancelaria as Customer Content is retained in accordance with the agreement, the account configuration and the customer's retention policy described in section 11. The user or an authorized customer may delete such data in the application. Merely disconnecting the integration stops further access to Kalendarz iCloud, but does not automatically delete data previously stored in Bezpieczna Kancelaria.

The user may disconnect the integration at any time in the Bezpieczna Kancelaria settings. Deleting the account in Bezpieczna Kancelaria or terminating the provision of the service results in the deletion or return of data in accordance with the procedure described in section 11.

9. Recipients of data

Data may be disclosed to the following categories of recipients:

providers of server and cloud infrastructure,
providers of electronic mail and transactional messaging services,
providers of technical monitoring and security systems,
payment system providers,
the accounting firm,
law firms providing services to the Controller,
providers of transcription, speech recognition or AI services, if the customer uses such functions,
providers of support tools,
operators of external services to which the customer has connected an account,
public authorities, courts or other authorized entities, where required by law.

We enter into appropriate data processing agreements with entities processing data on our behalf.

The current list of subprocessors we use:

Hetzner Online GmbH (Germany, European Economic Area) - server and hosting infrastructure (servers, databases, file storage).
OpenAI (USA) - transcription of recordings and AI functions; the transfer of data outside the EEA takes place on the basis of standard contractual clauses (SCCs).
ElevenLabs (USA) - transcription and speech recognition; the transfer of data outside the EEA takes place on the basis of standard contractual clauses (SCCs).

9.1. Operators of connected external services

If the user connects Bezpieczna Kancelaria to the user's own account with an external service, data may be exchanged with the operator of that service on the user's instructions and solely to the extent necessary for the operation of the selected integration.

This applies in particular to:

Google - the operator of the Google Calendar service,
Apple - the operator of the Kalendarz iCloud service.

Insofar as they provide Google Calendar and Kalendarz iCloud services to the user, Google and Apple act as operators of their own services, on the basis of their own terms and privacy policies. In this respect, they are not subprocessors of Aurea Enterprises sp. z o.o. The user independently decides whether to connect the account and may disconnect the integration at any time.

Information on the data processing rules applied by these operators can be found in the Google Privacy Policy and the Apple Privacy Policy.

10. Transfers of data outside the European Economic Area

As a rule, we seek to ensure that data are processed within the European Economic Area.

If, in connection with the use of specific providers or functions, data are transferred outside the European Economic Area, such transfers take place exclusively using the mechanisms provided for under RODO, in particular a European Commission adequacy decision, standard contractual clauses or other required safeguards.

Information on transfers outside the EEA is provided in the list of subprocessors (section „Data recipients").

11. Data retention period

We retain data for no longer than is necessary to fulfil the purposes for which they were collected.

In particular:

we retain user account data for the duration of use of the service and subsequently for the period required for settlements, handling claims or complying with legal obligations,
we retain billing and accounting data for the period required by tax and accounting laws,
we retain contact data processed in connection with an enquiry for the duration of handling the matter and subsequently for the period necessary to demonstrate the course of the matter or defend against claims,
we retain security logs for a period of 12 months,
we process marketing data until an objection is raised, consent is withdrawn or the data cease to be useful,
we retain data entered into the system by the client in accordance with the agreement, account configuration and retention policy selected by the client.

Following termination of the agreement, the client's data may be deleted, returned, exported or anonymised in accordance with the agreement and the service termination procedure.

12. Rights of the data subject

To the extent that we are the data controller, the data subject has the right to:

access the data,
receive a copy of the data,
rectify the data,
erase the data,
restrict processing,
data portability,
object to processing based on our legitimate interest,
withdraw consent where processing is based on consent.

Withdrawal of consent does not affect the lawfulness of processing carried out before its withdrawal.

To exercise these rights, please contact us at: privacy@bezpiecznakancelaria.pl.

We respond without undue delay, no later than within one month of receipt of the request. In complex cases, this period may be extended in accordance with RODO.

If the request concerns data processed by a client in the system, e.g. data contained in the files of a matter handled by a law firm, we may forward the request to the relevant client or advise that the client should be contacted directly.

13. Right to lodge a complaint

The data subject has the right to lodge a complaint with the supervisory authority competent in personal data protection matters.

In Poland, this authority is the President of the Personal Data Protection Office.

UODO contact details: Personal Data Protection Office, ul. Stawki 2, 00-193 Warsaw.

However, we encourage you to contact us before lodging a complaint. Many matters can be resolved more quickly without formal proceedings.

14. Automated decision-making

We do not make decisions concerning users based solely on automated processing that would produce legal effects concerning them or similarly significantly affect them.

AI, transcription, summarisation, search or document analysis functions are auxiliary in nature and are intended to support the user's work. Final decisions concerning matters, clients, documents or legal acts are made by the user or the client using the system.

15. Data security

We implement technical and organisational measures intended to protect data against unauthorised access, loss, alteration, disclosure or destruction.

In particular, depending on the scope of the service, we use:

data encryption,
access control,
user roles and permissions,
event logging,
authentication mechanisms,
segregation of client data,
backups,
security monitoring,
incident response procedures,
restriction of personnel access to data.

No IT system guarantees absolute security, but we design Bezpieczna Kancelaria so as to minimise the risks associated with the processing of law firm data.

16. Professional confidentiality and clients' professional secrecy

We understand that data processed in Bezpieczna Kancelaria may be subject to professional secrecy, advocate-client privilege, legal adviser-client privilege, trade secrecy or other confidentiality obligations.

Bezpieczna Kancelaria is a technology system, and the client using the service is responsible for assessing what data may be entered into the system and what professional obligations apply.

We provide technical and organisational measures designed to protect the confidentiality of data, in accordance with the agreement, security documentation and system settings.

17. Children's data

Bezpieczna Kancelaria is not a service directed specifically at children. We do not knowingly create accounts for persons who are not authorised users of the client.

However, children's data may be contained in documents or case files processed by clients of the system. In such a case, the client is the controller of such data and we process them as a processor.

18. Amendments to the Privacy Policy

We may amend the Privacy Policy, in particular in the event of changes to the system, technological changes, changes of providers, legal changes or changes to the scope of the services.

The current version of the Privacy Policy is published on bezpiecznakancelaria.pl.

We may also inform users of material changes in the application or by e-mail.

19. Contact

For matters concerning privacy and personal data protection, please contact:

Aurea Enterprises sp. z o.o., ul. Plac Bankowy 2, 00-095 Warsaw. E-mail: privacy@bezpiecznakancelaria.pl.

Language

This document is available in Polish and English. The Polish version is the source text; in case of any discrepancy between the versions, the Polish version prevails. The English version is a translation provided for convenience only.