Legal documents
WorkDrivePro Privacy Policy
Privacy policy: data, legal bases, providers, retention and rights.
1. Summary
WorkDrivePro processes the data needed to create and protect an account, synchronise records entered by the user and handle their requests.
In the current version:
- personal data is not sold;
- there is no advertising, marketing or advertising profiling;
- no behavioural analytics or Vercel Web Analytics have been integrated;
- there are no payments or subscriptions;
- no automated decisions with legal or similar effects are made;
- no employer is given access to the account;
- the Vehicle and Refuelling features do not use GPS, request the device's location or obtain vehicle telemetry; and
- Google Maps and sharing applications are opened only when the user requests it.
WorkDrivePro is currently a personal project, free of charge — current price 0 € — without monetisation or an economic purpose. This does not exclude the application of the General Data Protection Regulation, because the application allows third parties to hold accounts and synchronises information in the cloud.
2. Controller and contact
A data protection officer has not been appointed because, in view of the current activities, none of the circumstances requiring mandatory appointment has been identified. Enquiries may be sent to the contact above.
3. Scope
This policy applies to:
- the WorkDrivePro application;
- the account, authentication and synchronisation with Supabase;
- the website, private dashboard and support API hosted on Vercel, which publish legal information, account deletion information and the email confirmation result, handle the authenticated form and allow authorised administrator accounts to manage enquiries;
- delivery of operational emails through Resend; and
- messages sent to support or the privacy contact.
This version is offered exclusively in Spain, France, Germany, Austria, Ireland, Malta and Luxembourg to people aged 18 or over. The owner is established in Spain. The interface, essential instructions and public documents are available in Spanish, English, French and German. New multilingual installations start with the “System” option: they use the device language if it is one of the four available languages, or English otherwise. Existing installations retain Spanish or the selected language. The language can be changed in the application settings; a manual choice is retained. Changing the language does not alter the entries made by the user.
Language and territory are separate decisions; nationality and residence are not inferred from the selected language. The territorial scope does not involve geolocation or IP-based blocking and does not limit applicable mandatory rules.
Terms relating to workdays, allowances and kilometres describe personal organisation features. Translation does not automatically adapt their calculations to another country's employment, tax or transport legislation. Amounts are expressed in euros and distances in kilometres unless a feature expressly states otherwise.
Support channels are described in the owner information. Availability of the interface in four languages does not promise a native-language support team for each one. The local language preference does not activate remote translation of account content.
4. Data, purposes and legal bases
| Data | Purpose | Legal basis | Nature |
|---|---|---|---|
| Profile name or alias, email address, account identifier, confirmation status and session metadata | Create the account, verify the email address, sign in and out, recover access and administer the account | Performance of the Terms of Use and steps requested before registration, Art. 6.1.b GDPR | The profile name or alias and email address are necessary; the identifier, status and metadata are generated when managing the account. The password is described in the following row |
| Password | Authenticate the user | Art. 6.1.b GDPR; security is also based on legitimate interests, Art. 6.1.f | Supabase Auth receives and manages it; WorkDrivePro does not display it or store it in plain text. The repeated password entered at registration is checked locally and is not sent as a separate item of data |
| Company name, if provided | Personalise the profile and certain reports | Art. 6.1.b GDPR, at the user's request | Optional; may be left blank |
| Workdays, dates, times, shifts, breaks, holidays, public holidays and notes | Record, calculate, view and synchronise personal organisation | Art. 6.1.b GDPR | Optional, depending on the features used |
| Allowances, items, quantities, currency, amounts and calculations | Create requested summaries and reports | Art. 6.1.b GDPR | Optional, depending on the features used |
| Legacy records of minutes of driving, other work and availability created by earlier versions | Retain and synchronise them during the technical transition, preserve the integrity of their deletion and erase them where appropriate, including when the account is deleted | Art. 6.1.b GDPR | They can exist only if they originate from earlier versions. The current version does not allow these records to be created or viewed through a Tachograph section |
| Name, description, URL, notes and last use of saved routes | Save and open a route when requested | Art. 6.1.b GDPR | Optional |
| Entered number plate, vehicle identifier, date, initial and final odometer readings and calculated distance | Identify the selected vehicle, manually record kilometres travelled, obtain totals and synchronise closed records | Art. 6.1.b GDPR, at the user's request | Optional. The pending entry contains the number plate, date and initial reading and remains only on that device until closed or deleted; closing it creates the complete record that can be synchronised |
| Linked number plate, refuelling date, odometer reading, volumes of diesel and AdBlue, individual costs, total amount and note | Record and view refuelling, calculate summaries, include it in requested reports and synchronise it | Art. 6.1.b GDPR, at the user's request | Optional. The note is optional and limited to 500 characters; it must contain only necessary information about the refuelling |
| Appearance, interface language, text scale, notification preference and other general settings | Remember the settings chosen on the device | Art. 6.1.b GDPR | Optional; default values apply if not provided. They are kept locally, are not synchronised with Supabase and may remain after an account is deleted |
| Resolved communication-language code —es-ES, en-GB, fr-FR or de-DE— included in the return path of a password-recovery request | Select the language of the requested recovery email and return the flow to the app | Performance of steps requested by the user, Art. 6.1.b GDPR | Sent to Supabase only when recovery is requested, derived from the current interface language and does not alter the immutable legal language of consent or create a remote preference. The path may appear in technical authentication logs |
| Personal dashboard order | Remember the selected order on that device | Art. 6.1.b GDPR | Optional; it is saved locally, associated with the account identifier, and is deleted when data linked to the account is purged on that device |
| Account identifier and remote default configuration values | Create the technical structures associated with the account and preserve their integrity | Art. 6.1.b GDPR | They are generated when the account is created; the current application does not synchronise the general preferences selected on the device with them |
| Identifier and local status of a pending password recovery or account deletion | Safely resume or check an interrupted sensitive flow without repeating an uncertain operation | Art. 6.1.b GDPR; legitimate interest in the security and integrity of the flow, Art. 6.1.f | Generated only when the relevant flow starts and deleted when it is completed, safely resolved or the associated local data is purged |
| Owner UUID, record and relationship identifiers — including vehicle, kilometre-reading and refuelling records — revisions, technical dates, cursors, change queue, retries, error text and deletion markers | Synchronise devices, resolve changes, diagnose errors and preserve integrity | Art. 6.1.b GDPR; legitimate interest in integrity and security, Art. 6.1.f | Necessary for synchronising and diagnosing the data the user chooses to save; a pending kilometre-reading entry does not enter the synchronisation queue |
| Accepted legal version, language and hash of the document presented, account identifier and server-generated date | Record which Terms were presented and accepted | Art. 6.1.b GDPR; legitimate interest in evidencing the relationship, Art. 6.1.f | Necessary to create the account |
| Technical data that may include IP address, date and time, user agent, authentication and request events, URL, headers and infrastructure logs | Operate and protect the service, prevent abuse, diagnose faults and investigate incidents | Legitimate interest in security, availability and integrity, Art. 6.1.f GDPR; Art. 6.1.c where a specific legal obligation requires an incident to be investigated, documented or notified | May be generated when connected services are used; the actual content depends on the event and the verified configuration |
| Account identifier and email address, optional alias, category, subject, message, request UUID, reference, status, revision and dates of an enquiry submitted from the app | Authenticate and register the request, display its reference, classify it, allow it to be viewed in a private inbox and respond to or follow up on it | Art. 6.1.b GDPR to provide requested support concerning an account; Art. 6.1.f GDPR to prevent abuse and maintain the security and integrity of handling | The session and account email address are required to use the form. The alias is optional. Only the minimum necessary information should be provided. The form does not send an automatic acknowledgement to the account's email address. Only authorised administrator accounts can access the inbox |
| Account identifier, request UUID and date of receipt of the anti-abuse receipt | Prevent duplicate submissions, apply limits and generate a stable reference | Legitimate interest in the channel's security, availability and integrity, Art. 6.1.f GDPR | Generated when submission is accepted and retained for a maximum of 30 days, independently of the retention period for the registered enquiry |
| Destination email address, operational message content and delivery metadata for confirmation, recovery or support notifications | Deliver emails needed to verify the account and recover access, and forward the enquiry to the support mailbox | Performance of the Terms or requested steps, Art. 6.1.b GDPR; legitimate interest in security and delivery traceability, Art. 6.1.f | Resend processes delivery. Open and click tracking are disabled |
| Contact details, communication content and technical elements of a security report | Investigate, contain and document incidents or suspicious access | Legitimate interest in protecting accounts and systems, Art. 6.1.f GDPR; Art. 6.1.c where a specific legal obligation applies | Passwords, access codes and complete exports must be omitted |
| Identity, contact details, request, communications and, only where there are reasonable doubts, verification items | Handle the exercise of rights and demonstrate that requests have been addressed | Compliance with legal obligations, Art. 6.1.c GDPR, in conjunction with Arts. 12 to 22 GDPR | An identity document is not requested at the outset; any item supplied solely to verify identity is deleted once verification is complete |
| Identity, submissions, correspondence and evidence relating to a claim | Manage, establish, exercise or defend claims | Legitimate interest in defending claims, Art. 6.1.f GDPR; Art. 6.1.c where a specific legal obligation exists | Only content relevant to the claim is retained |
| Data included in PDFs | Generate the requested report locally | Performance of the Terms of Use, Art. 6.1.b GDPR | The PDF corresponds to the selected sections and periods: it may show the number plate associated with a workday and, if Refuelling is included, the date, number plate, odometer reading, volumes, amounts and note. It does not include pending entries or the initial readings, final readings or distances from the Vehicle section. It is generated by a user action and cannot restore the account |
The legitimate interests described consist of protecting accounts and systems, maintaining synchronisation consistency, preventing abusive use, diagnosing faults and establishing or defending claims. Data minimisation and restricted-access measures are applied. The user may object on grounds relating to their particular situation.
There is no legal obligation to provide data to create an account. The profile name or alias, email address and password are WorkDrivePro's contractual requirements; without them, the account cannot be created or used. Data for other features is optional, but each feature needs the data the user chooses to enter into it to produce the requested record, calculation or file.
General consent is not used as the legal basis for necessary features. The registration checkbox accepts the Terms of Use and confirms that this policy has been read. If an optional purpose based on consent is introduced in the future, that consent would be requested separately and could be withdrawn without affecting processing carried out before withdrawal.
5. Sources and data subjects
Data comes mainly from the user, their actions in the application, their device and technical providers that generate the records necessary to authenticate, synchronise and protect the service.
Vehicle and Refuelling data is entered manually. WorkDrivePro does not read number plates using a camera, connect to the vehicle or a fuel pump, obtain GPS coordinates or automatically collect location, journeys or telemetry.
WorkDrivePro does not currently obtain data from employers, advertising networks or data brokers.
6. Sensitive data and third-party data
WorkDrivePro is not designed to process special categories of data — for example, health, ideology, trade union membership, religion, biometrics or sex life — or information about convictions or offences. A number plate may be personal data when it allows a vehicle to be linked to a person, and its combination with dates, kilometre readings or refuelling may reveal patterns of activity. Only a number plate that the user is entitled to manage should be recorded. The application must not be used to store other data that identifies or could identify other people either. The Spanish Data Protection Agency also explains that a number plate may constitute personal data when it allows a person to be indirectly identified in its guidance on vehicle number plates.
Entering such data in free-text fields is prohibited, as is entering passwords or secrets. If it is added by mistake, the user must correct or delete the record as soon as possible. If they cannot do so, they can contact catalinu88@yahoo.com, describing the problem without reproducing the affected data. When WorkDrivePro becomes aware that data of this kind has been added, it may restrict access to it or erase it to the extent necessary to reduce the risk, respecting applicable legal obligations and providing information where appropriate.
In particular, an optional refuelling note must not contain health data, bank details, passwords, access codes, unnecessary information about other people or other sensitive data.
7. Storage on the device
WorkDrivePro keeps functional and synchronisation data in a SQLite database on the device to allow offline use. This includes number plates, closed kilometre-reading records, pending entries, refuelling records and their amounts and notes when these features are used. This database does not incorporate WorkDrivePro-specific encryption. It may be protected by the operating system's general lock and encryption, whose configuration depends on the device.
The session and PKCE state are stored separately using the operating system's secure storage, such as Keychain or Keystore. Communications with the backend use connections encrypted in transit.
In the audited Android configuration, general backup of app data is disabled. The same outcome is not asserted for all iOS versions or system backups until it has been verified in each published version.
PDFs are generated without a password or application-specific encryption. The user chooses the initial destination but does not necessarily control all subsequent copies: the operating system, cloud service, receiving application or recipient may retain or reproduce them. WorkDrivePro cannot withdraw copies already delivered outside the application.
8. Cloud storage and synchronisation
An account is mandatory to access the service; there is no exclusively local guest mode. With a valid account and session, the application attempts to synchronise profile data and data from the features used with Supabase when signing in, when opening WorkDrivePro or bringing it back to the foreground, and when the user requests manual synchronisation. Restoring the connection does not in itself start synchronisation while the application remains in the same state; pending changes wait for the next synchronisation event.
Appearance, interface language, text scale, notification preference and other general settings remain local and are not synchronised with Supabase. The personal dashboard order is also local, but is associated with the account on that device.
Number plates, closed kilometre-reading records and refuelling records are included in synchronisation when those features are used. A pending kilometre-reading entry that does not yet contain a final reading remains solely on the device; only closing it creates a complete record suitable for synchronisation.
The audited Supabase project's primary region is eu-west-1 (Ireland). Data separation is based on authentication and owner-based access policies. The primary region does not exclude logs, support or ancillary processing by subprocessors in other countries.
9. Providers and recipients
WorkDrivePro does not disclose data for the purpose of displaying advertising or sell personal data. The following may be involved:
Supabase
Resend
Resend's DPA incorporates the Standard Contractual Clauses and provides for its participation in the EU–US Data Privacy Framework. The identity and function of its subprocessors are maintained in its official list.
Vercel
Password recovery does not use that page: the link returns directly to the application.
Yahoo Mail
The contact catalinu88@yahoo.com uses a personal Yahoo Mail service as the support mailbox and reply address. It receives both messages sent directly and notifications generated by Resend from the form. Yahoo International Limited, based in Ireland for EEA users, provides that service under its own terms and purposes as an independent controller; it is not presented as a processor for WorkDrivePro.
Data processed by Yahoo under its own policy may include message content and metadata for its operational and security purposes and the other purposes described there, subject to available controls. Passwords, complete exports, identity documents and particularly sensitive data must therefore not be sent by email. If they are needed for a request, an appropriate channel will be agreed first.
Google Maps and other applications
When a route is tapped, the URL is passed to Google Maps or the application selected by the device. For EEA users, Google identifies Google Ireland Limited as the provider of its consumer services. When a PDF is saved or shared, the file is passed to the selected file system, application and recipient. These third parties act under their own terms and policies from the moment they receive the information.
Authorities and advisers
Data may be provided, to the minimum extent necessary, to courts, authorities, law enforcement agencies or advisers where there is a valid request, a specific legal obligation or a need to establish, exercise or defend claims.
10. International transfers
The transfers envisaged in this version are as follows:
- Supabase: although the primary database is in Ireland, the contractual processor is Supabase Pte. Ltd in Singapore, and there are international access arrangements and subprocessors. Its DPA incorporates the Standard Contractual Clauses in Decision (EU) 2021/914; under the current model, module 2, controller to processor, applies. Acceptance of the agreement has the same effect as signing the clauses. The identity and function of subprocessors are maintained in Supabase's official list; its DPA allows processing wherever Supabase or those subprocessors maintain facilities, subject to transfer safeguards.
- Vercel: Vercel Inc. states that its principal processing facilities are in the United States and that it uses subprocessors in other locations. Its Pro-plan DPA incorporates the 2021 Standard Contractual Clauses: module 2 for data processed as a processor and module 1 when it acts as a controller of service-generated data.
- Resend: Plus Five Five, Inc. processes in the United States the addresses, content and metadata necessary to deliver emails. The
eu-west-1region controls the sending point but does not move that storage to the EEA. Its DPA incorporates the Standard Contractual Clauses and provides for the EU–US Data Privacy Framework; the subprocessors on its official list may also be involved. - Yahoo Mail: Yahoo International Limited is in Ireland, but its service transfers information to destinations including Australia, the United Kingdom, India, the United States, Canada, Singapore, Taiwan and Israel. As an independent controller, Yahoo states that it uses adequacy decisions and Standard Contractual Clauses, depending on the destination.
- Google Maps: Google Ireland Limited provides the service in the EEA and uses servers in various countries. Google states that it relies, as applicable, on adequacy decisions, the EU–US Data Privacy Framework and Standard Contractual Clauses.
Additional information or a copy of the Supabase, Vercel or Resend safeguards may be requested from WorkDrivePro by writing to catalinu88@yahoo.com. For the safeguards applied by Yahoo or Google as independent controllers, the channels listed in their respective policies should be used. Copies may redact trade secrets and third-party data without removing essential information about the safeguard.
11. Retention
WorkDrivePro applies the following maximum retention periods:
| Data | Retention |
|---|---|
| Account, profile and active functional data | While the account remains active or until the user deletes a record or the account. This includes number plates, kilometre-reading records and refuelling records, if used |
| Pending kilometre-reading entry | Only on the device, until it is closed, deleted or the account's local data is purged; it is not synchronised while it remains open |
| Deleted functional records and their deletion markers | As a general rule, a maximum of 90 days from creation of the marker to propagate and resolve deletion across devices. For number plates, kilometre-reading and refuelling records, a marker not yet acknowledged by the server remains in a pending technical state until confirmation or reconciliation, hidden from ordinary features and used exclusively to prevent the record from reappearing. Following confirmation, it is deleted in the next applicable purge cycle and, in all cases, within a maximum of 90 days of that confirmation. A number plate is not purged while kilometre-reading records, refuelling records or a pending entry retain a reference to it; that relationship must first be resolved. As a narrow technical exception for referential integrity, a deleted allowance item may be retained for longer while an undeleted historical daily allowance continues to refer to it. Once the relevant reference ceases to exist, the record is deleted in the next purge cycle. Restricted retention may also apply because of a specific legal obligation or claim |
| Synchronisation queue: successfully confirmed operations | Maximum 7 days from server confirmation, solely for operational checking and recovery |
| Synchronisation queue: failed or unresolved operations | Maximum 30 days from the first failure; on reaching that deadline they must be removed from the ordinary queue, or isolated only where a specific incident justifies their restricted retention |
| Device synchronisation cursors and metadata | While needed to maintain account consistency; deleted when local data associated with the account is purged |
| Local data on the current device | Until confirmed account deletion, deletion of app data or uninstallation, depending on the system. The dashboard order associated with the account is deleted during local purging; general preferences not linked to the account may remain. Other devices require separate action |
| Record of acceptance of the Terms | While the account is active; the current implementation deletes it together with the account |
| Enquiries in the private support inbox | Open enquiries are retained for a maximum of 365 days from receipt. Resolved or closed enquiries are deleted no later than 180 days after entering that status, without exceeding the overall 365-day limit. Deleting the account also deletes its enquiries from the inbox. If a communication becomes part of a rights request, incident or claim, only the necessary evidence may be processed separately for the relevant period stated below |
| Minimal anti-abuse receipt for the support form | Account identifier, request UUID and date: maximum 30 days. It contains no alias, category, subject or message and is independent of the enquiry stored in the inbox |
| Delivery copy in Resend | Addresses, content and metadata of sent email: 30 days by default, except for restricted retention where a specific obligation or incident exists |
| Copies or communications in the support mailbox | While being handled and for up to 12 months from closure, unless they become part of a rights request, incident or claim; Yahoo may retain data under its own cycles as an independent controller. This period applies to email and does not extend the private inbox's period |
| Rights requests and evidence of response | While being handled and subsequently for up to 3 years from the response or closure to evidence their handling, unless proceedings remain open or a different statutory period applies. Documents or identifiers supplied solely to verify identity are deleted as soon as verification ends; only the minimum necessary result is retained |
| Claims and evidence needed for their defence | While being handled and, following closure, for up to 5 years where the general limitation period for personal actions applies, or for the relevant special period. Only relevant data is retained under restriction and it is deleted when the period expires or the proceedings end |
| Operational, security and infrastructure logs | Maximum 30 days from generation. If an event becomes part of a specific investigation or claim, only necessary data may be retained under restriction for the period applicable to the case |
| Provider operational backups | Ordinary maximum window of 7 days. After a provider's service ends, residual data may remain for a maximum of 30 days if the applicable DPA or contract so provides. If a backup is restored, subsequent deletions are reapplied |
| Saved or shared PDFs and legacy external JSON files | The user chooses the PDF's initial destination. WorkDrivePro cannot control or withdraw PDFs already delivered or JSON copies saved outside the app by earlier versions; their subsequent retention may also depend on the device, application, cloud service and recipient |
Where a specific investigation, claim or legal obligation exists, only the necessary data may be retained under restriction until the corresponding liability ends. It will not be used for ordinary service provision during that restriction.
12. Account deletion
The account can be deleted from the WorkDrivePro settings. The action requires an authenticated session and typing exactly ELIMINAR, including when the interface is in another language. The instructions are translated, but this confirmation word remains unchanged. The form identifies the action and its consequences before allowing it to be confirmed.
When the server confirms the operation:
- it deletes the authentication user;
- it cascade-deletes the associated remote profile, configuration, acceptance record and functional data, including that account's enquiries retained in the private support inbox;
- it ends and clears the session only on the device from which the operation is performed; and
- it purges the local data associated with the account on that device and legacy internal JSON copies that the application can recognise as belonging to that account.
General application preferences not linked to the account may remain on that device. Session material or local data on other devices is not cleared remotely and may remain until it is revoked or expires, the application is reopened with a connection or the app's data is cleared on each device.
The operation cannot withdraw PDFs or legacy JSON files already saved, renamed or shared, data received by third parties or local data on other offline devices. Nor does it mean that technical logs or provider copies disappear before their rotation cycles end.
Uninstalling the application does not, on its own, delete the remote account.
13. Rights
The user may request:
- access to their data and the information provided for in Article 15 GDPR;
- rectification of inaccurate data;
- erasure;
- restriction of processing;
- objection to processing based on legitimate interests; and
- portability where its requirements are met.
Requests should be sent to catalinu88@yahoo.com. The email address associated with the account and the right to be exercised must be stated. Identity documents should not be attached at the outset. Additional information will be requested only if there are reasonable doubts about identity, and an appropriate channel will be provided.
The response will be provided without undue delay and, as a general rule, within a maximum of one month. That period may be extended by a further two months for complex or numerous requests, with notice of the extension and its reasons given within the first month.
Removing JSON export from the interface does not limit the right of access or, where applicable, portability. These rights are exercised through the channel and within the scope described in this section.
If you reside in France, you may send catalinu88@yahoo.com specific instructions concerning the retention, erasure and disclosure of your personal data after your death, in accordance with Article 85 of the French Data Protection Act. Receipt and content of those instructions will be confirmed separately: they are not inferred from acceptance of the Terms of Use. You may amend or revoke them and, where the law permits, appoint a person to implement them. In the absence of instructions, French statutory rules will apply and requests from entitled persons will be acted on only after their identity and authority have been verified. The CNIL provides further information about personal data after death.
Article 77 GDPR allows you to lodge a complaint with a supervisory authority, in particular in the Member State of your habitual residence, place of work or the alleged infringement. The controller’s establishment in Spain does not restrict this right to the Spanish authority. These channels are available in the countries targeted by this version:
- Spain: Agencia Española de Protección de Datos (AEPD).
- France: Commission nationale de l’informatique et des libertés (CNIL).
- Germany: directory of the Länder data protection authorities; the competent authority depends on the case.
- Austria: Österreichische Datenschutzbehörde (DSB).
- Ireland: Data Protection Commission (DPC).
- Malta: Information and Data Protection Commissioner (IDPC).
- Luxembourg: Commission nationale pour la protection des données (CNPD).
This list facilitates access to authorities; it does not create exclusive jurisdiction or limit other administrative or judicial remedies. We do not infer your residence or the competent authority from the selected language. The official GDPR text is available on EUR-Lex, and the European Data Protection Board publishes its list of national authorities.
14. Minors
WorkDrivePro is intended exclusively for people aged 18 or over. It does not seek to knowingly collect minors' data. If an account belonging to a minor is detected, processing will be restricted, the situation will be verified proportionately and the account will be deleted where appropriate.
15. Automated decisions
WorkDrivePro does not carry out profiling or make decisions based solely on automated processing that produce legal effects or have a similarly significant effect.
16. Security
Measures applied include encrypted connections, separation of data by user, owner-based remote access policies, secure session storage and an authenticated flow for deleting the account.
These measures do not eliminate all risks. The SQLite database and PDFs do not have WorkDrivePro-specific encryption; nor do JSON copies created by earlier versions. The user must keep the system up to date, lock the device and protect their credentials. These precautions do not reduce the security obligations applicable to the controller.
An incident or suspicious access may be reported to catalinu88@yahoo.com, without including passwords or access codes.
17. Changes
The version and date of this policy appear at the beginning. Changes will apply prospectively. Where they materially affect processing, information will be provided before they take effect. Consent will be requested only where it is the legal basis for a specific purpose; users will not be asked to “accept” a privacy policy as a whole.
This revision limits the offering to Spain, France, Germany, Austria, Ireland, Malta and Luxembourg and retains the documentation in Spanish, English, French and German. It identifies the local language preference and evidence of the contractual language and content presented. The Privacy Policy is informational and does not constitute general consent to data processing.
Any future economic purpose, service for businesses, advertising, analytics, payment, affiliate arrangements, sponsorship or secondary use of data will be subject to legal review and a prior update before activation.