Veni Privacy Policy

Version: 1.4 — analytics, attribution, and versioned acceptance review
Date: October 15, 2026
Scope: the Veni application, veniveni.ar, advertising landing pages, the waiting list, and the pet-tag code lookup page; walk services in CABA and GBA, Argentina, and account registration using phone numbers from Latin American countries.

This Policy explains what personal data Veni processes, why it uses that data, with whom it shares the data, and how you may exercise your rights. It applies to Owners, Walkers, visitors to the website and pet-tag page, people registered on the waiting list, and other people whose data is communicated to the service. A single account may have both Owner and Walker profiles, with different permissions and purposes.

1. Data controller and contact

The controller of Veni’s account, profile, booking, walk, support, and security databases is Kirill Platonov, CUIT 27-63194224-0, with address at Sánchez de Bustamante 2496, 10th floor, Apartment B, Autonomous City of Buenos Aires, Argentine Republic.

For questions, requests concerning your data, account deletion, or privacy incidents, email [email protected]. You may also use the Help Center and the application’s data controls. You do not need to maintain an active account to exercise your rights.

2. Data we process

The data depends on your profile and the features you use:

Data about a dog is not, by itself, information about a person’s health. It may, however, identify the Owner when associated with the account and therefore receives the corresponding protection. Do not include human medical records, full banking information, passwords, or private information unrelated to the service in free-text fields, photos, or messages.

The DNI and selfie review planned for the MVP is manual. It does not include automated facial recognition, creation of biometric templates, or criminal background checks. The optional certificate is reviewed visually. Introducing another verification technology requires prior disclosure of how it works and the application of the corresponding safeguards and authorizations.

3. Required and optional data and legal basis for processing

Data required to create and protect the account, contract and perform the walk, process payments, and respond to claims is processed to perform the contractual relationship, within the scope of Section 5(2)(d) of Law 25.326. Receipts and information required by law are processed to comply with that obligation. Each legal basis is limited to the data necessary for its purpose.

A verified email and phone number are required to operate the service. The Walker must complete their profile and verify their identity to become eligible and publish the profile. Linking Mercado Pago is not a condition for registering an account, completing verification, or publishing a profile: it is required immediately before the first Me interesa or Accept order action that may lead to a paid booking and to receive the corresponding payments. If required data is missing, Veni blocks only the feature that requires it. Errors may prevent verification or affect booking coordination; you may correct them or request a review.

Optional features include the Walker’s certificate, welfare reminders, use of automatic location during registration, linking a pet tag, and publishing contact information. Choosing not to enable those features does not prevent you from using other features for which you meet the requirements.

The waiting list is also optional. Before registration, the form must distinguish required from optional fields and explain the delivery of notices and the copy stored in the CRM in France. Withdrawing from that list does not prevent you from creating or using a Veni account. Consent to receive availability notices does not authorize unrelated promotional campaigns or communications for an indefinite period.

Where processing requires consent, Veni requests it freely, expressly, and on an informed basis. For this version, the applicable Terms and this Policy are presented together in a mandatory versioned notice with links to open both documents and one action, Accept and continue. No separate checkboxes are added for Amplitude or AppsFlyer, and their names are not displayed in the short notice: complete information on providers, purposes, data, retention, and rights appears in this Policy. Before acceptance, Veni blocks optional product-analytics and attribution events. Independent operating-system permissions—such as App Tracking Transparency where applicable—are requested separately. You may withdraw optional consent for the future or request deletion by emailing [email protected]. Withdrawal does not invalidate prior lawful processing or prevent retention under another applicable legal basis.

Reading this Policy does not constitute consent to advertising, publication of contact information, external use of images, or any optional processing. Veni does not sell personal data or authorize providers to exploit it for their own purposes unrelated to the contracted service.

4. Location, address, and GPS

During registration, Veni may request permission to determine your location and use Google Maps/Places to suggest an address. You must review and confirm it. You may deny permission and enter or correct the address manually.

The Walker’s home address and precise reference location are not displayed in public profiles or search results. The area and limited service information are displayed to evaluate requests. The exact meeting point is communicated to the Walker involved when necessary to review or perform the booking.

During a walk, Veni may record the location of the Walker’s device and display to the Owner the points or route corresponding to their order. Collection is limited to the service context; if background operation is required, this is explained before the system permission is requested. The data is not used to track the Walker outside the service. The Owner does not continuously share their location in order to receive tracking.

You can manage permissions on the device. Revoking them may prevent a complete route from being recorded or displayed, but the application includes warnings and handles signal failures. GPS does not replace the drop-off and return PINs. For group walks, route display must not reveal the names, addresses, or data of other Owners.

Veni must not send full addresses, precise coordinates, pet-tag codes, PINs, documents, or message content to product analytics tools.

5. Information visible to other people

Profiles and requests. Users may view the Walker’s professional profile, photo, offering, area, reputation, and badges described in the application. They do not have access to the DNI, verification selfie, home address, credentials, or payment account. Eligible Walkers in the area may view limited information about a public request and the dog to assess whether they can provide the service; they do not see the home address, private contact information, or full welfare history.

Booking. For a public request, only the selected Walker receives the exact meeting point and final terms before deciding whether to accept the Individual Walk Agreement; other interested Walkers do not have access to that information. Tapping I’m interested does not constitute contractual acceptance. Pre-contract access is limited to evaluating that request and requires confidentiality; if the Walker rejects, the deadline expires, or they cease to be the selected candidate, operational access to that data is withdrawn, subject to the minimum legally justified retention.

The parties to a confirmed order have access to the corresponding chat and reports. The Walker sees the dog information necessary for safety—including behavior, allergies, and relevant medication—but not the pet-tag code or full welfare history. After the service ends, access is limited to the documentation needed for their own receipts and claims.

Reviews. Reviews and the author details shown by the publication form may appear alongside the reviewed profile. Do not publish addresses, phone numbers, documents, or identifiable photographs of third parties unrelated to the walk. You may request review of content that infringes your rights.

Pet tag. Linking a code requires specific authorization to display the selected contact information to a person who correctly enters that code. Authorization may be withdrawn; display must stop from that moment. The code cannot guarantee confidentiality from anyone who knows it. The home address is never published through this feature.

Lost pet. Before publication, the application explains which dog details, area, and contact information will be visible. You may close the alert or remove the contact information. Other people may have saved a copy while it was visible, so Veni cannot guarantee deletion outside systems under its control.

The pet-tag page does not require the visitor to have an account or submit an identity or contact form. It may generate technical logs concerning access, security, and code lookup. A lookup may notify the Owner that the code was entered without revealing the visitor’s IP address or other technical identifiers.

6. Welfare and automation

Veni uses the dog’s records to display progress and reminders based on entered dates and feature rules. It does not make diagnoses, prescribe treatment, or replace veterinary consultation. Human illnesses or sensitive personal characteristics must not be inferred from those records.

The application also applies rules concerning availability, area compatibility, expiration, payments, and statuses. Reviews or incident signals may require a safety review. You may request an explanation and human review of decisions affecting your account, verification, or claim through the Help Center or the contact email. Veni does not use DNI images, selfies, chats, or routes to train general-purpose artificial intelligence models.

7. Storage, providers, and other recipients

The application’s primary data—accounts, profiles, dogs, orders, chats, payment statuses, acceptances, and personal-data requests—is stored in a PostgreSQL database managed by Veni on a virtual server contracted from DonWeb / Dattatec, in Buenos Aires, Argentina. Private files, including DNI images, selfies, welfare records, and reports, are stored on that server. This does not mean all information remains exclusively in Argentina: the following integrations also participate in the service.

The stated storage location does not guarantee that every technical access, distribution, or processing activity by a provider occurs only there. Global providers may use other centers or subprocessors in accordance with their terms and applicable safeguards.

Mercado Pago also processes information to meet its regulatory and fraud-prevention obligations under its own policy. Veni does not request its password or retain full card numbers or security codes in its databases. Authentication data and permissions for linking the Walker’s account are protected on Veni’s server.

Veni is responsible for handling questions and claims. No external helpdesk is currently used, and tickets are not transferred to an external first-level service. Complaints and disputes are managed in Veni’s database and internal panel. Email communications continue to use email infrastructure; the absence of a helpdesk does not mean the absence of technology providers. If a helpdesk is introduced, Veni will disclose the provider, shared data, and location before that processing begins.

Information is also communicated to the booking counterparty within the scope of Section 5, to professionals or emergency services where necessary and legally appropriate, and to authorities in response to a valid request. Providers acting on Veni’s behalf must be subject to instructions, confidentiality, and use limitations. You may ask about recipients and conditions at [email protected]. Their involvement does not remove Veni’s obligations.

8. International transfers

The operation includes processing in Argentina and international transfers: public photos to Cloudflare R2 in the EU region, a copy of the waiting list to the CRM in France, errors to Sentry in Germany, app analytics to Amplitude through Veni’s United States organization and endpoints, attribution to AppsFlyer, emails to Resend in the United States, and data required for the global services of Google, Apple, and Cloudflare. A provider’s location does not establish that all of its data centers or subprocessors are in that country.

Before making a transfer, Veni must identify the destination and have the required mechanism in place: a country recognized as providing adequate protection by the AAIP, contractual safeguards accepted by that authority, or another legal exception applicable to the case. Where appropriate, standard contractual clauses are used to protect data and limit its use. Accepting the Terms or reading this Policy does not constitute unrestricted authorization to transfer data to any country.

You may request information about the destinations actually used and the corresponding safeguards at [email protected]. If processing changes materially, Veni will disclose the change and request new consent where legally required.

9. Retention and deletion

Veni retains data only while necessary for its purpose or while a specific obligation applies. Closing an account does not justify indiscriminate retention of all its content. The following ordinary retention criteria and limits apply:

Deletion from the waiting list must cover both the database in Argentina and its copy in France. Sentry and Resend limits must be applied through the provider’s retention or deletion settings. If a provider retains certain records as an independent controller due to its own obligation, its terms and the corresponding rights apply; this does not authorize Veni to continue using them for another purpose.

These limits do not require data to be retained for the entire period if it ceases to be necessary earlier, nor do they suspend deadlines for addressing your rights. If a legal obligation, dispute, authority order, or third-party rights prevent deletion of specific records, Veni will explain the reason and retain only the relevant data, with restricted access and no commercial reuse. Its necessity will be reviewed when that basis ends.

Backups must remain outside ordinary use and expire through rotation within a maximum of 90 days; a restoration must reapply deletions. This mechanism does not permit continued use of data that has already been validly deleted. Effectively de-identified information that no longer identifies or can be relinked to a person may be retained for statistics.

10. Security and confidentiality

Veni undertakes to protect data through role-based access controls, secure transmission, credential protection, restricted access to documents and attachments, traceability of sensitive actions, and recovery measures. DNI images and verification selfies are not published. Drop-off and return PINs must not be sent in notifications or remain visible after use; the validation record required for the order is retained.

Private files on Veni’s server are stored encrypted, and Mercado Pago linking tokens are also protected by encryption. Photos intended for publication follow the public-media flow. A DNI image, verification selfie, or private report must not be sent through that flow. Storage encryption is not end-to-end encryption and does not prevent authorized personnel from accessing data for the stated purpose.

No system is infallible. In the event of an incident, Veni must assess its scope, contain it, and make any required communications to affected people and authorities. You may report a problem to [email protected] without sending passwords, PINs, or full card numbers.

11. Your rights and how to exercise them

You may request information about processing and the source and recipients of your data; access an understandable copy; correct or update data; request deletion where appropriate; and withdraw optional consents. The application includes controls to request export and deletion. The export protects third parties’ private data and does not include their credentials or information unrelated to your request.

Email [email protected], stating the right you wish to exercise and the email or phone number associated with the account. Veni may verify your identity proportionately to avoid disclosing information to another person; it does not require a complete copy of your DNI by default where a less intrusive method is sufficient. If you act on behalf of someone else, your authority will be verified.

An access request is answered within 10 calendar days. An appropriate correction, update, or deletion is completed within 5 business days, in accordance with Law 25.326. Access is free at intervals of no less than six months, and sooner where a legitimate interest is demonstrated. Exercising these rights is not conditional upon payment of a debt or maintaining an active profile.

If deletion does not apply in whole or in part, the legal reason is explained and retention is limited to the necessary data. While the accuracy of disputed data is being verified, it must be blocked or identified as under review, as applicable. Closing an Owner or Walker profile does not automatically delete the other profile; the scope is clarified when processing the request.

You may file a complaint with the Agency for Access to Public Information (AAIP), the supervisory authority under Law 25.326, if you believe your rights have been affected by non-compliance, and may pursue the applicable habeas data action. Information and complaint channels: AAIP — rights concerning your data and report non-compliance.

12. Notifications, advertising, and local storage

Communications concerning access, orders, payments, security, and claims are part of the service. You may manage device notifications; disabling them may prevent you from receiving a notice on time, so information must also be available within Veni.

The app and website use technical mechanisms for sessions, preferences, and security. Cloudflare protects traffic, and Turnstile is used on /sos to prevent abuse. The application uses Amplitude for product analytics and AppsFlyer for installation, campaign, and QR attribution only after acceptance of this version. Google Analytics 4 is used only on veniveni.ar and advertising landing pages, never inside the application. The website uses basic consent mode: the Google tag is fully blocked until consent, analytics_storage is enabled only afterward, and advertising modes remain denied. Sentry records app and API errors for the diagnostic purpose described in Section 7.

Non-essential analytics must be accompanied by information and a consent option before activation where applicable; rejecting or withdrawing consent does not prevent waiting-list registration or booking a walk. Veni must not include precise addresses, documents, payment data, contact information, or message content in those analytics. Waiting-list campaign parameters are used to identify the source of registration and do not, by themselves, authorize other advertising purposes. You may manage cookies in the browser and exercise your rights regarding this processing by contacting the email address above.

Sending promotions and using identifiable photos outside the service require optional authorization. You may withdraw that authorization through the same channel or by email. Consent to promotions is not required to open an account or make a booking.

12.1 Amplitude and AppsFlyer limits in the application

Veni sends only events and properties approved in its measurement plans. These may include a pseudonymous user or installation identifier, active role, screen or flow step, platform, app version, technical device information, approximate area, source/campaign/QR, and opaque request or order identifiers.

These tools do not receive name, email, phone number, DNI, selfie, address, precise coordinates or route, PIN, payment data, chat or free-text content, dog name or photo, or health and welfare data. In Amplitude, IP/location enrichment, advertising ID, autocapture, session replay, audiences, and AI features remain disabled unless a later documented decision, privacy review, and new user disclosure authorize them. In AppsFlyer, partner postbacks and advertising sharing are disabled by default; any use requiring App Tracking Transparency also depends on the separate operating-system permission.

Veni stores an auditable acceptance record containing user identity or identifier, Terms and Privacy versions, language, app version, date and time, and an immutable hash of each document. After acceptance, the user returns to the active context and role; acceptance does not authorize advertising, sale of data, or use of prohibited data categories.

13. Third-party data and minors

Veni is intended for people aged 18 or older. Accounts must not be created for minors, and their documents or images must not be deliberately uploaded. If data concerning a minor is detected, its deletion and the necessary protective measures will be evaluated.

If you provide an emergency contact or authorize another person to receive the dog, inform that person in advance how their data will be used and ensure that you have their authorization where applicable. Veni uses the data only for that coordination or emergency. That person may also exercise their rights by email. Avoid including faces, addresses, license plates, or third-party information that is not necessary in photos, reports, and no-show evidence.

14. Changes and availability

The current version must be available in the Legal section before data is collected. When this version replaces an earlier one, Veni displays the blocking versioned notice before normal app use is enabled again; it cannot be dismissed by tapping outside, using Back, or swiping. You may request this Policy and the version provided to you at registration by email. Veni will communicate relevant changes and, if they introduce purposes requiring consent, request consent before beginning that processing. Continued use does not replace such consent.

A change of operator must identify the new controller, their contact information, the date, and the effect on data and contracts, while respecting existing rights. Questions about this Policy: [email protected].