ARIVA - Privacy Policy
Version 1.0 · in force from 28 October 2026
This English version is a translation. If it differs from the Romanian version, the Romanian version prevails.
1. Who is responsible for the data
QUANTUM POS SRL, unique registration code (CUI) RO17007933, Trade Register J2004008540131, offers the ARIVA platform. Registered office: Aleea Solidarității nr. 7, bl. B, sc. C, et. P, ap. 34, Constanța, 900294, România. Correspondence address: Strada Ion Adam 22, Constanța, 900620. For data-related requests: contact@selio.io, +40 241 515517.
QUANTUM POS is responsible for the processing operations whose purposes and means it determines for the platform: account, addresses, group participation, security and support. The restaurant is responsible for its own processing operations necessary for the sale, preparation, delivery, invoicing and resolution of problems with the order. Roles are determined for each activity; providing the platform does not automatically turn QUANTUM POS into a mere processor for all the data.
The contact above is the point of contact for privacy requests.
2. What data we use
| Situation | Relevant data |
|---|---|
| Google, email or SMS sign-in | Account identifier, name, email, phone number, the available photo and technical authentication data, depending on the method chosen. |
| Address and recipient | The address, coordinates, place identifier and, if filled in, the label, floor, instructions and the recipient's contact details. |
| Cart and order | Products, quantities, configurations, notes, amounts, receiving method and the data needed to complete the order; a cart is not a submitted order. |
| Group Order | Name, available photo, participation, title, selections, Done and data for recovering your own cart. |
| Protection and operation | Technical, device, connection and event data necessary for authentication, security and diagnostics. |
| Support | The message and the contact details provided; do not send passwords, SMS codes or full card details. |
The data comes from you, from the sign-in method or from the person who indicates a recipient. Inform the people whose data you enter and use only the necessary information.
The optional note about allergies concerns the order in question, not a reusable medical profile. Do not enter diagnoses or other unnecessary medical details. Information about a personal allergy may be data concerning health even if it is used temporarily. The note does not guarantee that the restaurant can fulfil the request; ask for clarification about ingredients and allergens before ordering. We do not use transactional emails to transmit notes about allergies.
3. Purposes and grounds
| Purpose | Basis used, within the limits of necessity |
|---|---|
| Account, addresses, cart, group and the requested service | Performance of the applicable contract or steps requested before entering into it. |
| Fraud prevention, security, diagnostics and defence of rights | The legitimate interest in protecting the service and users, with an assessment of necessity and of the balance with the person's rights. |
| Accounting, tax and other applicable obligations | The specific legal obligation of the responsible entity, only for the necessary data. |
| Optional features based on consent | Separate consent for the purpose concerned, which can be withdrawn. |
| Support | Performance of the requested service or the legitimate interest in resolution, depending on the subject of the request. |
Mandatory data is necessary for the action for which it is requested; without it, that action may not be possible. We do not use this to justify uses unrelated to the service.
Under the declared model, QUANTUM POS and the restaurants do not use ARIVA data for marketing, commercial profiling or promotional lists. This does not exclude the providers' technical anti-fraud checks. Accepting the Terms or simply filling in a note does not replace the specific legal conditions for health data or a consent required separately.
4. Location, authentication and providers
You can enter the address manually without access to the device's location. When you use the address search or the map, the necessary data is processed through Google Maps. For orders at the table, where the distance check is active, the position may be necessary and may accompany the order. The browser's permission for location is not general consent for other purposes.
We use Google services for authentication, infrastructure and protection, including reCAPTCHA. For sign-in by SMS, Google states that the numbers are sent and stored, including for the prevention of spam and abuse across its services. The notice and consent required for this method are distinct from the cookie preferences and from the Terms.
We use an email service provider for transactional messages, sent from no-reply@ariva.food. For support, use contact@selio.io, not the no-reply address. We do not send notes about allergies through these emails.
Card payment through a payment service provider is planned. This policy does not indicate that the method is already active: the processing related to payment applies only when the method is actually offered in Checkout. Payment details and transaction confirmation follow the flow available at that time.
The ariva.food presentation website does not use cookies and does not include forms; it is hosted through Firebase Hosting (Google). When the website is accessed, Google processes the IP address for abuse prevention and for analysis of the use of the hosting service.
Messages sent to hello@ariva.food and the contact details provided are used by QUANTUM POS SRL to respond to requests.
5. Who can see the data
Order data is accessible to the restaurant and to the authorised persons who take part in its fulfilment, to the extent necessary. The ARIVA rule does not give the restaurant general access to the account or to all your saved addresses. Technical providers are involved for their services; authorities or advisers may receive data when there is a legal basis and a need.
In Group Order, the holder of a valid link sees the group title, the host's name and the delivery address before joining. Members see names, available photos, selections and per-product notes, as well as the Done status. They can redistribute the link. Do not distribute the invitation publicly and do not enter sensitive data in notes.
A guest without an account receives an anonymous technical identity; this does not mean anonymity with respect to the system. The data needed to recover the cart may remain temporarily after exit or after deletion of the group.
6. International transfers
Providers' services may involve processing outside the European Economic Area. Google's documentation indicates that data of the authentication service used by ARIVA is processed in the United States; the European region of a database does not guarantee that all services or data remain in the EU.
Transfers must be based on the applicable mechanism, such as an adequacy decision or appropriate safeguards, including standard contractual clauses, as the case may be. You can request, at contact@selio.io, information about the recipients, the applicable mechanism and obtaining a copy of the safeguards. Through this policy, we do not ask for a general consent that would replace these requirements.
7. How long we keep the data
The schedule below is the retention policy adopted for the copies managed by QUANTUM POS. Operational implementation, including deletions and backups, must be validated before the document enters into force; the table does not certify automations that have already been implemented.
| Category | Approved period and starting point | Limits |
|---|---|---|
| R1 - Account and saved addresses | For as long as the account is used; after 24 months of inactivity, a notification and a further 30 days for reactivation, then deletion. | Authenticated activity initiated by the user, not the mere renewal of the token; we do not require signing in again if already signed in. A deletion request does not wait for inactivity; addresses can be deleted separately. |
| R2 - Identity of a guest without an account | 30 days after the last completed participation, if there is no active group or recovery in progress. | Deleting the group does not automatically delete the Auth identity; the provider's copies are distinct. |
| R3 - Operational order details | Up to 30 days after delivery/pickup or closure by cancellation/refusal. | Exact coordinates, instructions and notes only for as long as they are necessary. It is not a complaint deadline and does not automatically delete saved addresses or necessary documents. |
| R4 - Minimal proof of the order/payment | Up to 3 years after delivery/pickup or cancellation/refusal; for evidence of a subsequent refund or of the closure of a dispute, up to 3 years from that event. | Only the necessary evidence, not all the raw notes/addresses or the authentication identity. It is not a universal legal time limit; necessity and exceptions require validation. |
| R5 - Own accounting documents | Approved reference point: 5 years from 1 July of the year following the end of the financial year in which they were drawn up. | The accountant validates the applicable law, the inventory and the special rules. It is not a basis for keeping the customer's entire account. |
| R6 - Ordinary support | Up to 12 months after the request is closed. | Unnecessary attachments are removed earlier; requests under Regulation (EU) 2016/679 (GDPR) and disputes are separate. |
| R7 - Proof of resolution of GDPR requests | Up to 3 years after the final response. | The minimum record necessary, not full exports or copies of documents kept by default; it does not change the legal deadline for responding. |
| R8 - Own logs | Up to 30 days from the event for diagnostics; up to 90 days, also from the event, where justified for security. | Minimal data, without passwords, OTP, tokens or complete order bodies. We do not extend the periods to providers' logs. |
| R9 - Own configurable backups | A maximum of 30 days from the creation of each backup. | Includes versions and recoverable copies configurable by us; access only for recovery. Lifecycle, soft delete and the reapplication of deletions after restoration are validated. It does not cover all the providers' internal copies. |
Group Order has two hours for selections. The normal clean-up threshold is expiry plus 24 hours, and the recovery of archived products has a separate window of 24 hours from archiving. These thresholds do not guarantee the simultaneous physical deletion of all copies.
The choice regarding cookies is valid for six calendar months from the explicit action. Browser storage and providers' storage have the distinct durations explained in the Cookie Policy.
Where possible, we remove earlier any data that is no longer necessary. Legal obligations or disputes may require the selective retention of certain evidence, not the unlimited retention of the entire account. The restaurant and the providers may have their own retention obligations.
For the Google authentication service used by ARIVA, the provider documents the deletion of authentication information from active systems and backups within a maximum of 180 days after the project owner initiates the deletion of the user. This limit is not the duration of all Google data and does not replace the ARIVA schedule.
8. Rights and requests
Under the conditions laid down by law, you can request access, rectification, erasure, restriction and portability, and you can object to processing for which the right to object applies. You can withdraw consent for the future without affecting the lawfulness of prior processing.
Write to contact@selio.io. We verify identity in proportion to the request; do not send your password or authentication codes. As a rule, we respond within one month at most. Where the law allows an extension because of complexity or the number of requests, we inform you of the extension and the reasons within the first month. You can lodge a complaint with the National Supervisory Authority for Personal Data Processing (ANSPDCP).
Deleting data from the browser does not automatically delete the data on the server. Deleting a group does not delete the fiscal documents or the necessary evidence of the order. Rights may have legal limits, which we explain in the response.
9. Changes and cookies
The version and the date of application are indicated in the document; relevant changes are communicated before they apply. Consult the Cookie Policy separately. Neither creating the account nor browsing constitutes consent to all the processing described here.