Voltropi

Legal

This document is published in English. You can use your browser's translation to read it in your language.

Version 1 · Published on November 18, 2026

VOLTROPI Data Deletion Policy

Version 1.0 — Effective date: the day it is published

1. Purpose

This policy explains how to ask AeroGroup Holdings LLC ("AeroGroup") to delete personal data processed through VOLTROPI, and what happens when a request is validated. It complements the Privacy Policy.

2. Who handles your request

  • Data managed by a Tenant (passengers, clients, a Tenant's staff or drivers): the Tenant decides. Contact the Tenant first. If you contact us, we identify the Tenant where we can and forward or support the request, and tell you who is responsible.
  • Data AeroGroup controls (your VOLTROPI account, billing, administration, security, website contact, global-network driver account): we handle the request.

3. How to request

  1. Email support@voltropi.com, or use the contact form of the website and tell us it is a privacy request.
  2. Tell us: your name, the account or contact detail concerned (email or phone), the Tenant you dealt with if any, and whether you want full deletion or only certain data.
  3. Do not send passwords or full identity documents in the first message.

4. Verifying who you are

We verify that you are entitled to ask, proportionally to the sensitivity of the data: for example by a confirmation sent to the contact detail on record, or by confirming a few facts about the account. We may ask for more if there is doubt. If we cannot verify, we cannot delete, and we will tell you why.

5. What happens once we validate a request

Where applicable to the account concerned, we:

  1. Revoke or disconnect authorizations, for example connections with external messaging or identity services, so they stop receiving data.
  2. Block access to the account when needed, so no new data is created while the request is processed.
  3. Delete or irreversibly de-identify the data in our active systems.
  4. Pass the request on to recipients and providers that hold the data on our behalf, where applicable, and require them to delete it.
  5. Record the outcome of each step in an internal log kept only as long as needed to prove compliance.
  6. Handle backup copies and legal retentions as described in section 7.
  7. Confirm to you when the request has been completed, and tell you what could not be deleted and why. Deletion of data a Tenant controls is carried out by or on the instruction of that Tenant.

5.1 When a Tenant closes its account

A Tenant that closes its account follows this order:

  1. Export first. The Tenant can export its business and operational information in XLSX and CSV, within the permissions of each user. We confirm that the export completed before the matching deletion runs, unless the Tenant records a waiver or the export period ends, which is 30 calendar days after the closure request.
  2. Restriction. Access and messaging are switched off, and data is restricted (kept but not used) while requests or legal holds are resolved.
  3. Revocation and erasure of secrets. Integrations are revoked with the external provider first (for example the Meta authorization), then access credentials and stored payment-account numbers are erased or masked. VOLTROPI does not store full card numbers or security codes.
  4. Personal data processed for the Tenant (its passengers, clients, staff and drivers) is returned or exported and then erased on the Tenant's instruction, as the Data Processing Agreement states, except where a documented legal basis requires keeping it.
  5. What AeroGroup keeps. AeroGroup keeps its own business file of the contract and billing relationship with the Tenant (identity of the company, contracts and acceptances with their versions, invoices, payments, subscriptions, account history, incidents and audit records) under restricted access and for the periods the law and our legitimate interests require, which depend on the country and the type of record and never exceed what is needed (see section 11 of the Privacy Policy). Personal data inside those records is separated and kept only where a rule requires it and for that rule's period. This file is not a reason to keep personal data of passengers, drivers or employees. If a company returns, we recognise it using only the information we are still lawfully allowed to keep.

5.2 Global network drivers who leave

When a driver closes their account or is removed, we erase the sensitive data (identity and licence images, verification photo, documents, bank or wallet numbers, device data and location history). We do not keep a general copy of your details. We may keep only a minimal record for stated purposes and for a limited time: to prevent re-registration after a safety or fraud decision, to handle claims and disputes, to keep the financial record of payouts with your account number masked, and to recognise you if you return by choice. Where recognition is the purpose we keep irreversible fingerprints of identifiers instead of the identifiers themselves. The record is shorter when you leave voluntarily without incidents. If you ask for erasure we honour it unless a legal exception applies, and we tell you which. The time we keep that record depends on the country and the reason; we do not publish a fixed number, and if you ask we tell you what we keep and why.

6. Timing

Our deadlines are counted in business days (days that are not Saturdays, Sundays or official public holidays of the country that applies to your request) and start when your request reaches us:

StepDeadline
Receiving your request. We confirm that we received it and tell you whether we need anything else to verify you.2 business days
Handling your request. We verify, decide and carry out the steps in section 5 on our active systems.10 additional business days after the receipt period
Active systems. Once the request is approved, your data is deleted or irreversibly de-identified from our active systems, within the handling period.Within the 10 business days above
Ordinary backup copies. Once the request is approved, the ordinary backup copies that contain your data are deleted or overwritten.At most 90 business days after approval

The law of your country comes first. These are our general deadlines. Where the data protection law of a country applies to your request and requires something different (a different deadline, a different procedure, additional rights or a specific authority), we follow and respect the law of that country when we process your data and handle your request. If a request is complex and the law allows an extension, we will tell you before the deadline and explain why.

7. Backups and retention required by law

  • Backups. Deletion from our active systems comes first; we do not promise instant physical deletion of every backup copy. Ordinary backup copies are protected, are used only to recover the service, are never used to restore deleted data into active systems after your request (if a restore is ever needed, the deletion is applied again before the data is used), and are deleted or overwritten on their normal cycle, at most 90 business days after your request is approved. Backups kept for a legal obligation or a legal claim follow the next point instead.
  • Records we must keep. We may keep data that the law requires or permits us to keep, for example accounting and tax records, records needed to establish, exercise or defend legal claims, safety and fraud-prevention records, and records of the deletion request itself. These are kept only for the period the law requires for that type of record in the country concerned, and are restricted to those purposes.
  • Aggregated or de-identified information that no longer identifies you may be kept.

8. Meta integrations

Data processed through a Tenant's connected Meta accounts is also held by Meta under Meta's own terms and policies. Disconnecting an integration revokes the authorization and we erase what we hold for that connection (access tokens and account identifiers immediately; message templates and delivery records according to the retention period set for each country). We may keep limited records where the law or a legitimate need requires it, such as invoicing records, records needed for legal claims and safety records, for the periods that apply in each country. Meta keeps its own copies under its own policies; to delete data Meta holds, use Meta's tools or contact Meta. We do not promise absolute erasure of every copy, and we do not keep data indefinitely. We are preparing the technical mechanism that Meta requires for data deletion requests that originate on Meta's platforms.

9. If we refuse

We will explain the reason and tell you how to complain to the competent authority, such as the data protection authority of your country (for example the National Authority for Personal Data Protection in Peru) or, in the EU/UK, your supervisory authority. The local addendum of each country names the authority that applies there.

10. Contact

support@voltropi.com. AeroGroup Holdings LLC, 30 N Gould St Ste R, Sheridan, Wyoming 82801, United States.