Yttrio

Yttrio Privacy Policy

Last updated: 11 October 2026.

This policy explains how information is handled when you use Yttrio on iOS, Android or the web, browse shared events, contact us, or use an optional identity, location or payment feature. The information involved depends on the features you use. An operating-system permission or an initial sign-in does not, by itself, authorize every use described here.

1. Who is responsible and how to contact us

Yttrio is operated by the operator identified in the following contact record. The operator is responsible for Yttrio's processing of your information.

Operator and postal contact: SHAPOSHNIKOV, VASILII, Avenida Santa Fe 1834 Piso 10, Departamento A, Ciudad de Buenos Aires - C1123AAN, Argentina (AR)

For privacy requests and questions about personal data, email legal@yttrio.app. For account access and product support, email support@yttrio.app. You can also use support and privacy settings in your signed-in Yttrio account. If you cannot reach the privacy address, contact support. Do not send passwords, SMS codes, complete card details or identity-document images by ordinary email. We will explain a secure route if evidence is needed.

2. Information we collect and where it comes from

Information comes from you, people who invite or interact with you, your device, sign-in and payment providers, identity-verification results, and the operation of the service. Some service searches are processed on our servers. Optional AI assistance uses the information described in section 5.

3. Why we use information

We use information to maintain accounts; create, synchronize and show events; provide search, invitations, participation and notifications; apply visibility and eligibility rules; verify purchases and maintain one account's subscription and token state across clients; process support, cancellations and disputes; verify identity when required; prevent fraud and abuse; diagnose failures and improve reliability; record agreements and requests; and meet applicable legal obligations.

Where a legal basis is required, the relevant basis depends on the processing and applicable law: performing the service you request, legitimate interests in security and reliable operation where permitted, compliance with a legal obligation, or consent for processing that requires it. Optional marketing and product-analytics choices are separate from accepting the terms. Withdrawing a consent does not undo processing that was lawful before withdrawal.

4. Identity checks, facial processing and recorded video

Yttrio uses Didit for identity verification. The current verification flow reads a government identity document, checks live presence, compares a face with the document image, and analyzes IP/network signals. It uses facial recognition and records verification-session video. Document images, a selfie or other face images, video and derived facial-biometric/liveness information are therefore involved.

Yttrio sends an account/session reference and relevant contact information to associate the check with your account. We receive verification status, verified identity and age/document attributes, risk or warning results, and associated session references. We use these to decide whether the relevant verification level can be granted or retained, detect duplicate or inconsistent identities, and handle review or document expiry. A verification badge is not a guarantee about another user's conduct.

Didit processes verification data for the check and also handles relevant derived or pseudonymized information for its own fraud/security and model-improvement purposes. Model training is currently enabled for Yttrio's Didit organization. It can include future training, evaluation and related dataset work using relevant verification data. Yttrio's product-analytics switch does not control this separate provider setting. Didit's privacy policy and processing terms explain its roles and rights routes.

Read the verification notice before continuing. You can choose not to start verification, but functions requiring that verification level will be unavailable. Contact us to question an incorrect result or request information, restriction or deletion. Such a request is reviewed with the provider and applicable obligations; it is not a promise of instant erasure or reversal of model updates already made.

5. Providers and optional connected features

Some providers act on our instructions; others independently process data for their own account, security or service-improvement purposes. This policy does not treat every recipient as a processor acting only for Yttrio.

6. Other people who can see information

Your event's publication and visibility settings determine which event fields are public, visible to invited people or available after acceptance. Public marketplace listings and the permitted fields of a shared event link can be viewed by people outside your account. Contacts, restricted client instructions and participant information follow the event's role and access rules. Check the selected audience before publishing or sharing; recipients can copy information they can view.

We disclose the information needed to relevant participants and selected invitation recipients, the providers described above, and authorized support or operations personnel. We may disclose information when necessary to comply with a lawful request, protect people or the service, investigate misuse, or establish or defend a claim, subject to applicable law and the purpose of the disclosure. Private support evidence and internal costs are not made public merely because an event is published.

7. Your choices and device storage

You can edit supported profile and event fields, choose event audiences, manage optional product analytics and marketing in privacy settings, and change location or notification permissions in your device settings. Optional precise-location features, product analytics and marketing choices default to off. These choices do not disable the authentication, integrity, payment, diagnostic or provider processing separately described above.

The web app and mobile apps use device storage for sign-in/session operation, preferences, cached data, drafts and pending synchronization. Removing the app or clearing browser storage removes local information but does not, by itself, delete your account or server records. Current Yttrio apps do not offer advertising; do not interpret that as a statement that all providers' processing is anonymous or limited to our instructions.

8. How long information is kept

Retention depends on the record's purpose and applicable obligations. Account/profile information is kept while needed to operate the account and process closure. Event and participant records are kept for their lifecycle and any remaining cancellation, contractual or dispute purpose. Purchase, payment, refund and agreement evidence may need to remain after account closure for accounting, fraud prevention, legal obligations or claims. Support evidence is kept for the case and its applicable evidence-retention period. Technical logs, retry records and cached AI results have separate, shorter operational retention policies.

A legal hold or unresolved payment/dispute can require a particular record to be retained with restricted access. Provider-held data and backup or recovery copies follow separate deletion processes and are not removed instantaneously with a request or a screen change. Ask us about the retention applicable to your data; our response to a deletion or restriction request explains any material retention that prevents full removal. We do not describe an open deletion request as completed erasure.

9. Access, correction, deletion and other rights

Depending on applicable law, you may request access or a copy, correction, deletion, portability, restriction or objection to processing, and withdraw a consent. You may also complain to the competent data-protection authority. Use privacy and data settings in your signed-in account or email legal@yttrio.app; you can also contact support@yttrio.app. We may need a secure identity/ownership check, particularly for deletion or sensitive records. We assess the request under the applicable law and explain a refusal, limitation or permitted extension.

For account deletion, follow Delete your Yttrio account. A submitted authenticated deletion request restricts new protected activity while retaining necessary support and existing settlement, refund or dispute actions. Request receipt or a restricted account is not completed deletion. Completion requires fulfillment and verification; records with a remaining lawful retention basis may be retained separately. You can cancel a request only while its current status allows cancellation.

Account deletion does not automatically cancel renewal with Apple or Google Play. Manage renewal with the original provider; a Web purchase uses its original management route or support. You can submit a deletion request without first canceling a subscription. Removing the app also does not cancel renewal.

10. International processing and security

Yttrio's infrastructure and providers can process information in a country different from yours. The relevant recipients, locations, legal requirements and transfer arrangements depend on the feature and your location. Contact us for information about the arrangements applicable to your data; feature availability and legal requirements vary by location.

We use access restrictions, authenticated operations and encrypted network connections to protect information. No service or transmission is completely risk-free. Protect your sign-in methods and device, and contact support if you suspect unauthorized access.

11. Age and changes to this policy

Yttrio's marketplace features are intended for adults aged 18 or older; a child marketplace mode is not offered. A declaration or sign-in is not a universal verified-age check. Verification for a higher identity level includes an age check. Contact us if you believe a child has supplied information inappropriately.

We will update the date on this page when the policy changes. Where a material change requires a new notice, acknowledgement or consent, we will use the applicable in-app or other notice and choice process. A privacy-policy acknowledgement is separate from optional marketing, product analytics and the verification processing described above.