Vuelvo Verify Privacy Policy

1. Controller and contact

Controller: NODO PLUS S.A.S., Tax ID 901379054, Calle 5 # 4 - 11, Tibasosa, Boyacá, Colombia. Privacy contact: support@vuelvoloyalty.com.

2. Scope

• Authorized business users who sign in and select an organization and location.
• Users who register an Android phone for incoming-payment verification.
• Users who capture or upload a payment receipt for a verification request.
• People whose payment information appears in a receipt or eligible bank alert processed for the business.

3. Processing roles

For payment data managed by a business, the business generally acts as Controller and Vuelvo as Processor under its documented instructions. Vuelvo may act as Controller for user accounts, security, support, fraud prevention, and legal compliance.

4. Data we process

• Account and identity data: name, email address, user ID, identity provider, roles, permissions, and security records.
• Business context: organization, location, phone registration, receiving bank configuration, masked receiving-account information, and configuration status.
• Receipt and verification data: receipt image, amount, currency, reference, date and time, bank, payer information when present, verification status, and audit events.
• Bank alerts: sender and text of matching bank SMS; title, text, source app, bank, capture times, and opaque identifiers for matching notifications from authorized banking apps.
• Technical and support data: app version, device and request identifiers, integrity information, connection diagnostics, and messages that a user sends to support.

5. Access limitations

Vuelvo Verify requests only the access needed for its payment-verification flow. It does not request or read contacts, call logs, or unrelated SMS. It does not request Gmail access from the Android app and does not use SMS or notification data for advertising, marketing, lending, credit scoring, or generalized artificial-intelligence training.

6. Android SMS and bank-notification capture

When an authorized user activates the Android Collector, Vuelvo separately requests permission to receive and read SMS and access to notifications. These features can operate in the background while the app is not open. For SMS, the app locally examines the sender, text, and date of new messages and, only when the user chooses to recover alerts, up to 100 recent SMS from the previous 72 hours. For notifications, it first verifies that the bank app package and certificate are authorized and only then reads the title and text.

Only alerts matching the linked bank, incoming-payment wording, and an amount are transmitted over HTTPS to Vuelvo’s backend. For SMS, the app transmits the bank, sender, text of up to 2,000 characters, publication and capture times, and an opaque message identifier. For notifications, it transmits the approved bank app package and certificate fingerprint, title of up to 240 characters, text of up to 2,000 characters, times, and an opaque identifier. It also transmits the configuration version, device and request identifiers, signature, and integrity data needed to authenticate the source; the Play Integrity token is verified and not retained.

Messages showing signs of a password, OTP, login, authentication, or security code are discarded locally and are not transmitted. An SMS or notification is supporting evidence and never confirms a payment by itself. The backend uses eligible evidence to extract payment details, prevent duplicates, match alerts to receipts and receiving accounts, show results to authorized business users, and maintain traceability.

• We do not sell this data or use it for advertising.

7. Receipt capture and verification

A user may photograph or choose a receipt from the device gallery. The image is uploaded privately to process the verification request, and temporary local or server copies are removed according to the retention periods below. Vuelvo shows the verification result, including when the receipt needs information or controlled manual review; receipt processing alone does not execute or reverse a payment.

8. Purposes and legal bases

We process data to provide the requested payment verification service, honor consent for SMS and notification access, protect the service, prevent fraud, maintain auditability, provide support, and comply with law. We rely on contract, consent for optional device access, legitimate interests in security and continuity, and legal obligations as applicable.

9. Sharing and service providers

We do not sell personal data. We share only what is necessary with infrastructure, storage, authentication, security, monitoring, and support providers that operate the service; with the business that authorized the verification workflow; or when legally required. Providers operate under confidentiality, security, and limited-processing obligations.

10. International transfers

Some service providers may process information outside Colombia. We apply reasonable contractual, technical, and organizational safeguards under applicable law.

11. Retention and deletion

• The encrypted local Android queue expires within 72 hours. The in-app action to revoke this phone removes its local identity, configuration, and queue.
• The sender and text of matching SMS, and the title, text, and metadata of matching bank notifications, are scheduled for automatic deletion from the backend seven days after capture.
• Normalized Android evidence, such as amount, currency, reference, date, bank, opaque identifier, and parser result, is scheduled for automatic deletion after 180 days. Minimum reconciliation, security, or audit records that must be retained do not include the complete SMS or notification.
• Receipt images and temporary upload artifacts are removed after processing or cancellation according to the applicable storage and reconciliation rules.
• Account, business, verification, and support records are retained only for the period needed to operate the service, resolve disputes, maintain security, and satisfy legal duties.

12. User control and revocation

The user can decline or later revoke SMS permission and notification access in Android settings. An authorized business administrator can revoke the phone registration, which prevents the backend from accepting new deliveries. The user can also request access, correction, portability, objection, restriction, or deletion by emailing support@vuelvoloyalty.com or using the public form. We verify identity and authority before acting.

Request data deletion

13. Security

• HTTPS/TLS protects data in transit.
• The Android queue uses AES-256-GCM and non-exportable Android Keystore keys.
• Requests use signed payloads, device registration, and integrity checks.
• Access is restricted by authenticated user, business, location, role, and need.
• Data minimization, bank-package validation, OTP filtering, retention limits, monitoring, and access reviews reduce risk.

14. Cookies

The Vuelvo website may use cookies and local storage that are essential for authentication, security, and preferences. Browser controls can block or delete them, although some functions may stop working.

15. Children

Vuelvo Verify is directed to authorized business users and not to children. Businesses must obtain any authorization required for the personal data they manage.

16. Changes, governing law, and effective date

We may update this Policy and will communicate material changes through the Service, email, or a new update date. Colombian law and mandatory rules where the Service is provided apply. This version is effective on the date shown above.