OFIVELO · LEGAL INFORMATION
Privacy
This notice covers ofivelo.com, Ofivelo accounts and app-related features. It also distinguishes Ofivelo’s role from your workshop’s role.
Reviewed 2 November 2026
Who is behind Ofivelo
Ofivelo is an individual project by Bruno Almeida, currently in testing. Ofivelo is the project name, not a commercial company.
- Project controller
- Bruno Almeida
- Privacy contact
- [email protected]
Who processes the data
Bruno Almeida is the controller for data needed to operate the Ofivelo website, accounts and support. Contact: [email protected]. A workshop deciding why and how its customer, vehicle and service records are used is the controller for those records. Ofivelo acts as a processor when handling them on workshop instructions; this requires the agreement under Article 28 GDPR. Contact us to identify the responsible workshop and route a request.
Data and sources
We may process email, account identifiers, authorised profile information, assigned access, support messages and connection/security logs. Workshops provide customer contacts, vehicle details, registration plates, mileage, jobs, quotes, bookings, messages and recorded payments. Customers can submit booking requests, messages and maintenance reminders. Where a workshop supplies your data, the invitation and first contact point to privacy information; the workshop must explain the source and its own processing.
Purposes and legal grounds
The table below distinguishes processing managed by Ofivelo. Workshops determine the legal grounds for their own records, such as the requested service contract or applicable legal duties. Consent is not treated as a blanket authorisation for the entire service.
| Purpose | Main data | Legal ground |
|---|---|---|
| Account and requested services | Email, identifier, authentication and access | Contract or steps requested by the individual — Article 6(1)(b). |
| Security and abuse prevention | IP, access events and limited technical logs | Legitimate interest in service security and continuity — Article 6(1)(f), subject to balancing individual rights. |
| Support and rights requests | Contact and necessary request details | Article 6(1)(b) for service support; Article 6(1)(c) for legal duties concerning rights. |
| Optional authorised functions | GPS location and available preferences | Specific consent where required — Article 6(1)(a) and applicable terminal-access rules. |
Required data and optional choices
Email and authentication are required for an account; without them you cannot enter the customer area. Workshop access requires a valid invitation or association. Social login, GPS, published workshop contacts and optional notification channels depend on a choice. Email/password login and name search are available without allowing GPS.
Recipients
Supabase provides authentication and database services; Cloudflare hosts and protects the website; Resend delivers existing transactional emails such as invitations and quotes. Each receives data needed for the operation. Authorised workshop members access records within their permissions. Google, Meta/Facebook and Microsoft participate in authentication only when you choose that method. Support email uses the corresponding mail service. Authorities may receive data where legally required. Customer payment views display workshop records and do not process a card payment on this website.
Location and international transfers
The Supabase data project is configured in eu-west-2, London, United Kingdom. The UK currently benefits from a European Commission adequacy decision. This does not mean all providers or operations stay in the UK or EU: hosting, support, email and authentication may involve other countries. Transfers requiring safeguards must rely on an applicable adequacy decision or Article 46 safeguards such as standard contractual clauses and supplementary measures. Ask the privacy contact for recipient information and a copy or description of applicable safeguards.
Retention
Accounts and access are retained as needed to provide the service or until a deletion request is handled, subject to applicable legal duties and specific legal claims. Deleted operational app records may be recoverable by the workshop for 30 days. Workshop records can have separate legal retention requirements; the workshop must explain them. Reminders stay until deleted or the account is erased; completing a task does not delete it. Support requests are kept as needed to resolve them and any dispute or applicable legal period. Technical logs and backups follow provider configurations and contractual periods; backup removal follows rotation with restricted access and no reuse for unrelated purposes. Ask for periods or criteria applying to your case.
Location and reminders
When you request GPS search, the browser asks permission and coordinates calculate distances to published workshops. They are not added to your customer profile or a location-history table. Maintenance plans store vehicle, task, date, target mileage, notes and status. Address search and automatic maintenance email/WhatsApp reminders are not active on the website. Recipients, data and authorisation choices must be identified before activation. Exporting a reminder to your chosen calendar places the imported data under that calendar service’s terms.
Security, automated decisions and children
Access is limited by account and workshop, with authentication and server controls. Do not send passwords, authentication codes, card details or unnecessary identity documents in messages. These features do not make solely automated decisions with legal or similarly significant effects or build advertising profiles. The service is intended for workshops and customers able to use their services, not children.
Rights and complaints
You may request access, rectification, erasure, restriction, objection and, where conditions apply, portability. Consent can be withdrawn without affecting earlier lawful processing. GDPR limits apply, including legal retention duties. Your data and rights explains requests and deadlines. You may complain directly to Portugal’s CNPD or another competent supervisory authority without first complaining to Ofivelo.
Changes
The review date identifies this version. Material changes to purposes, recipients or choices will be reflected in notices at collection points or through the account as necessary. Updating this text does not itself authorise a new purpose requiring consent.
QR scanning and technical data
When you use the QR reader, Google Code Scanner (ML Kit) processes camera images on your device; the images and scanned result are not sent to Google. The SDK sends device and app information, identifiers, performance metrics and feature events to Google for diagnostics, maintenance and usage analysis. Automatic zoom also sends a scan session identifier, zoom changes and barcode frame coordinates. You can accept invitations from your account without using the QR reader.
Facebook and external services
The site links to Ofivelo on Facebook, Google Play and, in workshop details, maps or contact apps. It does not load a Facebook feed, embedded social buttons, Meta Pixel or advertising tools. Following an external link or choosing social login initiates interaction with that provider and its policies. You do not need Facebook to visit the informational site.