Todos los documentos legales solo están disponibles en inglés, y solo la versión en inglés es jurídicamente vinculante.
Traducir con Google Translatese abre en una pestaña nueva; solo como referenciaWhat personal data Avonao ID collects, why, who receives it, how long we keep it and how to exercise your rights.
What personal data Avonao ID collects, why, who receives it, how long we keep it and how to exercise your rights.
AVONAO, INC., 254 Chapman Rd, Ste 208 #21918, Newark, Delaware 19702, USA (a corporation formed in the State of Delaware, entity file number 10121895) is the controller of the personal data described in this policy.
Privacy questions and requests: privacy@avonao.com or the privacy rights request form on avonao.com. People in the European Economic Area, the United Kingdom, Switzerland and Brazil use the same channels, and we handle their requests at that address.
Our representative in the European Union. Our representative in the European Union under Article 27 GDPR, and our data protection officer for the European Union, is NUICORN, Chausseestraße 86, 10115 Berlin, Germany. You can contact them, and us at privacy@avonao.com, on all matters about your personal data.
This policy applies to Avonao ID, the passwordless account and sign-in service at id.avonao.com, and to the Avonao websites (the "Service"). Read it with the Terms of Service, the Cookie Policy and the list of Sub-processors.
Avonao platforms. Agined, Intramedial, Trustvice and GoPlainly are separate services, all operated by AVONAO, INC. Each has its own privacy policy for the data you create there, and each is responsible, as a separate controller, for what it does with the data it receives from Avonao ID. For sign-in and the account data held in Avonao ID, Avonao ID is an independent controller, whichever Avonao platform you use it for.
Businesses and their apps. A business whose app you allow is responsible for the data it receives from that moment on. Its own privacy policy applies, and the consent screen links to it. When a business uses an enterprise connection or signs in its own staff, we process that sign-in on the business's behalf as its processor, under the Data Processing Agreement that forms part of the business's agreement with us; the business is the controller. For account, security and website data, and for our own purposes described below, we are the controller.
In plain language: we collect what we need to run and secure your Avonao ID. An email address, a confirmed email and your answer to the age question are all we need to create it; everything else is optional and used only for the feature that needs it. Apps of other businesses get only what you allow on the consent screen. We do not sell your data and we never show ads. You can download your data and delete your account at any time, and section 7 explains exactly what that means.
| Category | What it includes | Where it comes from |
|---|---|---|
| Account data | Your confirmed email addresses, display name, language, chosen data-hosting region, when you accepted the Terms, where you created the account (which platform, if any) and the account status. | You. |
| Sign-in data | Email link or code (stored only as a hash, valid 10 minutes); passkeys (public key, name, dates); authenticator app secret (encrypted) and recovery codes (hashed); social accounts you connect: provider, the provider's account identifier, email, name and dates. We hold no passwords. | You, and the provider you connect. |
| Age and guardian data | At every sign-up: the country you give and your answer to "are you at least N years old?" (no date of birth), which is kept in your security log. If you answer that you are younger than the age of digital consent of your country: your email address, name (as you typed it, or from your Google, Microsoft or GitHub account), sign-in method, chosen data region and country, the email address of your parent or guardian, and a single-use link we send them (stored only as a hash). When they agree we keep a consent record: date, version of the texts, country, and a keyed hash of their email address, not the address itself. The guardian flow is built but switched off at launch. | You, and your parent or guardian. |
| Sessions and security log | Session: start, last use, sign-in methods, IP address, browser (user agent), a device label and country (derived from the IP address by our hosting provider). Security log: event (for example sign-in, new passkey, app connected), time, IP address, user agent and related app. | Your devices. |
| Connections to apps | Which app, when you first connected and last used it, the scopes you allowed, when you allowed or revoked them, a data receipt for every grant and revoke, and the identifier we created for you for that business. | You. |
| Avonao platforms | Which platform you connected to; whether your subscription there is none, free or paid, its renewal date and where to manage it, as the platform reports it (no prices, no billing data); a link to your earlier user id on the platform if your account was migrated. | The platform, and you. |
| Business accounts and Business Circle | Your role in a business, when you joined, invitations (email, role, dates), the business audit log (who did what and when), and the businesses you follow in the Avonao Business Circle and when. | You, and the business. |
| Avonao Wallet and agents | What you shared from your Avonao Wallet and with whom, credentials a business issued, and what your agents did (the activity record). The Avonao Wallet is a credentials vault; it holds no money. | You, businesses and your agents. |
| Billing data | From Stripe, for plans and purchases made in Avonao Billing: the outcome of a purchase (plan, status, amount and currency) and the Stripe customer and subscription identifiers. The billing contact, company details and payment method you give at checkout are entered at Stripe; we never receive your card number. | You, Avonao Billing and Stripe. |
| Verified (only when switched on) | The status of the check, Stripe's error code if it failed, the date, your trust level, and our record of your consent. | You, and Stripe. |
| Reports and moderation | If you report a business: the reason, details, the email address you give or your account, and your IP address for rate limiting. If you own a business: decisions about it and the statement of reasons. | You, and our review of reports. |
| Emails | Sign-in links and codes, security notices (for example "Google was connected to your Avonao ID"), requests and reminders to a parent or guardian and our replies to you about their decision, invitations, report confirmations and outcomes, and statements of reasons. | Us. |
| Notices to businesses (webhooks, Beta) | The business's identifier for you and the time you revoked its app or your account was deleted. | You. |
| Abuse prevention and operational logs | Rate-limit counters keyed by IP address, email address or account; the challenge token, IP address and browser signals of the Cloudflare Turnstile bot check on sign-up and business creation; service and request logs of our hosting provider. | Your devices. |
| Support records | What you write to support and in a privacy request, and our replies. | You. |
| Website analytics | Pages viewed, referrer, approximate location (country), device and browser type, and interactions with buttons and forms (never what you type), only if you allow the tools that set cookies or record how you use a page. No such tool is live today. See the Cookie Policy. | Your browser. |
If you are a person named in an app's data by someone else, that business is the source. You can use the rights in section 8 against us for the data we hold.
What an app of another business receives. Only after you allow it on the consent screen: an identifier for you that is the same for all apps of that business and different for every other business, plus technical sign-in information (time of sign-in, sign-in method, a session identifier specific to that business). With email: your primary email address, marked as confirmed. With profile: your display name and language. An app never receives your account id, your other email addresses, your sign-in methods or your security log. Avonao's own platforms (Agined, Intramedial, Trustvice and GoPlainly) receive your account id, primary email, name and language without a consent screen, because you create or use your account on those services with your Avonao ID and their own policies tell you so.
Verified. Verified is optional and switched off at launch. When it is on and you choose it, Stripe, our provider, asks you to photograph an identity document and take a live selfie, and compares the face on the document with the selfie. That face comparison uses biometric data, which is special category data under Article 9 GDPR, so we start the check only after your separate, explicit consent, given by ticking an unticked box beside the full text (Verified consent). We never receive or keep document images, selfies, biometric templates or document data. Stripe receives only a reference number from us, not your email, name or account id. You can withdraw consent at any time, in one step and without signing in again, in your dashboard under Verified; we then stop any check still running, remove your Verified status, the record of your checks and the proofs you have not used, ask Stripe to delete what it collected, and email you a confirmation. Withdrawing does not affect what was done before.
We do not store:
We do not build profiles of your use of other businesses' apps.
| Purpose | Data | Legal basis (GDPR and UK GDPR) |
|---|---|---|
| Create and run your account, sign you in and keep your sessions | Account data, sign-in data, sessions | Contract, Art. 6(1)(b). |
| Check your age and, below the age of digital consent, ask a parent or guardian | Age and guardian data | The account itself rests on contract. The guardian check is our duty to make reasonable efforts to verify the guardian's agreement: legal obligation and legitimate interests, Art. 8(2) with Art. 6(1)(f). |
| Keep a security log and secure the Service, detect and prevent fraud and abuse, rate limit | Security log, sessions, rate-limit counters, Turnstile data, operational logs | Contract, Art. 6(1)(b); legitimate interests in keeping the Service and its members safe, Art. 6(1)(f) and Art. 32. |
| Connect you to apps of other businesses and to Avonao platforms, and keep a data receipt of each grant and revoke | Connections to apps, platform data | Contract: you ask us to share, Art. 6(1)(b). |
| Run business accounts and the Avonao Business Circle | Business membership, invitations, business audit log, follows | Contract, Art. 6(1)(b); legitimate interest of the business in knowing who acted, Art. 6(1)(f). |
| Run your Avonao Wallet and agents | Wallet sharing history, credentials, agent activity record | Contract, Art. 6(1)(b). |
| Take payment for plans bought in Avonao Billing and keep the records | Billing data | Contract, Art. 6(1)(b); legal obligation for tax and accounting records, Art. 6(1)(c). |
| Handle reports and moderation | Reports, decisions, statements of reasons | Legal obligation (Digital Services Act), Art. 6(1)(c); legitimate interests, Art. 6(1)(f). |
| Tell businesses about revokes and deletions | The business's identifier for you and the time | Legitimate interests in businesses deleting data they no longer may keep, Art. 6(1)(f). |
| Respond to support and privacy requests, and keep a record that we did | Support and request records | Contract, legal obligation and legitimate interests. |
| Send service notices (sign-in, security, invitations, outcomes) | Account data, emails | Contract and legal obligation, Art. 6(1)(b) and (c). |
| Check your identity with Verified | Verified data | Explicit consent, Art. 6(1)(a) and Art. 9(2)(a). |
| Find and fix errors and keep the Service running (planned tools) | Error reports and service logs | Legitimate interests in a secure, working service, Art. 6(1)(f); Art. 32. |
| Measure how the website is used | Website analytics | Consent, Art. 6(1)(a) and the cookie rules (ePrivacy Art. 5(3)) for tools that use cookies or device storage; legitimate interests for cookieless counting. |
| Establish or defend legal claims and meet other legal duties | Records as needed | Legal obligation and legitimate interests. |
Where we rely on legitimate interests you can object (section 8). Where we rely on consent you can withdraw it at any time.
California and other US states. We collect the categories above for the business purposes listed in this section. In the language of the CCPA, we collect identifiers (email, name, IP address), customer records and commercial information (subscription state, purchase outcome), internet and network activity (requests, logs, analytics if you consent) and approximate location derived from IP address. The only sensitive personal information we handle is the biometric data of a Verified check, which Stripe processes only with your explicit consent and which we never receive; we do not use sensitive personal information to infer characteristics about you. We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not use it for targeted advertising or profiling.
We do not sell personal data to anyone, and we do not share it for advertising.
We are based in the United States. When you sign up you choose one of seven data-hosting regions: US East, US West, Europe Central, Europe West, Europe North, Asia-Pacific or Oceania. Your account data (profile, email addresses, sign-in methods, sessions, app connections, consent records, follows and security log) is stored in a database in that region, and the part of Avonao ID that handles your sign-in runs in a separate service for that region. For the three European regions the database is held under Cloudflare's EU jurisdiction, which keeps the data in the European Union; we do not choose the city. For the other regions we ask Cloudflare to place the database in the region, but that is a request and not a guarantee. A sign-up that is waiting for a parent or guardian, including the guardian's email address, is stored in the region you chose and nowhere else.
Some records are kept in our home region, US West, whatever region you chose: (1) a pseudonymous index (your account id, the region, and keyed hashes of your email addresses and sign-in identifiers, not the addresses themselves), which is how we find your region when you sign in; (2) records that belong to businesses (business accounts, apps, moderation decisions, our signing keys), including an invitation to join a business, which holds the invited email address, and a report about a business, which holds the reporter's email address if the reporter gave one; and (3) short-lived records created before we know who is signing in: a pending sign-in request from an app (up to 30 minutes; the app may have suggested an email address in it), sign-in state for passkeys and social sign-in (minutes), and the log entry of a failed passkey attempt with its IP address (13 months, like the security log). Everything else about you, including your security log, stays in your region.
Your connection reaches Cloudflare's network at the location nearest to you and our front service runs there, so your request, including your IP address, can pass through servers outside your region on its way to your data. Some actions (signing in with Google or Microsoft or with your company's single sign-on, using a business console, or us suspending an app) are handled by our home service, which then reads or changes the data in your region. Cloudflare's own network, security and logging systems are not limited to your region.
If you are in the EEA, the UK or Switzerland, your personal data is transferred to the United States and, depending on the provider, to other countries when you use the Service. Where personal data goes outside the EEA, the UK or Switzerland, we rely on the EU-US Data Privacy Framework (and its UK Extension and the Swiss-US Data Privacy Framework) where the provider is certified under it, and otherwise on the European Commission's Standard Contractual Clauses with the UK addendum (and, for Switzerland, the Swiss adaptations of the clauses). Cloudflare, Stripe and GitHub state in their data protection terms that they rely on the Data Privacy Framework first and the Standard Contractual Clauses as a second basis. The Sub-processors page shows each provider's company and transfer basis. You can ask for a copy of the safeguards at privacy@avonao.com.
| Data | Kept for |
|---|---|
| Account and everything attached to it | Until you delete your account, plus a 28-day restore window. Your account is closed to use, and your sessions and app connections end, when you confirm the deletion. Then the daily clean-up purges the account, emails, sign-in methods, sessions, app connections, consent records and data receipts, follows, business memberships and Verified results. Deletion cannot be requested while a paid platform subscription runs, and the purge never deletes an account while one is active; cancel it on the platform first. A free subscription ends with your Avonao ID. When you delete your account, businesses that use our webhooks (Beta) are told, so they can delete their copy. |
| Recovery data kept by our hosting provider | Our hosting provider keeps point-in-time recovery data of each database for up to 30 days (Cloudflare D1 Time Travel on its paid plan; 7 days on its free plan). Deleted data can stay in that recovery data until it expires. It is not used for any other purpose and is not restored except to bring the service back after a failure; after any restore we delete again what had already been purged. |
| Security log | 395 days, about 13 months, and never longer than the account. At purge, entries are anonymised: account id, IP address, user agent and details are removed. When erasure of a person is required, we remove the identifier from the entries. |
| Sessions | Until they expire (14 days without use, 90 days at most) or you end them; ended sessions are deleted 30 days later. |
| Sign-in links and codes, pending sign-in requests, authorization codes, access tokens, second-factor and passkey challenges | Minutes: 10 minutes for email codes, 60 seconds for authorization codes and 10 minutes for access tokens; deleted by the daily clean-up about an hour after they expire. |
| A sign-up waiting for a parent or guardian (your request, the guardian's email address and the links we sent them) | Until the guardian decides, or 14 days at most. If they decline, it is deleted at once; if nobody answers, the daily clean-up deletes it and we tell you by email. We send the guardian one reminder after 7 days. Nothing of it is kept afterwards except an anonymous event without names. |
| The guardian's address typed into an unfinished sign-up (in the sign-in link or the sign-in state with Google, Microsoft or GitHub) | Minutes: removed as soon as the sign-up request exists, otherwise by the daily clean-up about an hour after it expires. |
| Consent record of a parent or guardian (date, version of the texts, country, keyed hash of their address) | As long as the account; deleted with it. |
| Verified | The result and your trust level until you withdraw or delete your account, whichever is first. Stripe keeps the identity data for the retention period we configure in Stripe, or until Stripe deletes it at our request after you withdraw. The record of your consent is deleted with your account. |
| Sharing history of your Avonao Wallet (what you shared and with whom) | 90 days. |
| Credentials a business issued, as the business's record | 30 days after the credential expires. |
| What your agents did (activity record) | 396 days by default; you choose between 30 days and 3 years under My agents. |
| Business accounts | Until the business is deleted; a minimal record (name, id) remains so receipts and reports keep their reference. |
| A business's audit log | While the business exists, plus 1 year after it is deleted. |
| Reports you filed | Until 3 years after the decision on the report; open reports until decided. At purge the link to your account is removed; an email address or name you entered in the report stays with it. |
| Moderation decisions about a business | 3 years after the decision, longer only while the decision is still in force; kept after the business is deleted so the decision can be explained and contested. |
| Webhook delivery records (contain the business's identifier for you) | 30 days. |
| Rate-limit counters | 24 hours. |
| Hosting provider request logs | Up to 7 days (Cloudflare Workers Logs on its paid plan; 3 days on its free plan). |
| Messages to support and our replies | 24 months after the last message in the conversation; the mailboxes are in Microsoft 365. |
| Website analytics, error-monitoring and recording data | None is collected today. Before a tool is switched on, this table gets its retention, set to the shortest the tool allows. |
| Your cookie choice | Stored in your browser until you clear its site data or change the choice; we ask again every 12 months. |
See the Cookie Policy for the cookies and local storage we use.
Depending on where you live, you may have the right to:
These rights come from the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection, the California Consumer Privacy Act as amended (CCPA/CPRA), the comparable laws of other US states, the LGPD and PIPEDA, and apply to the extent those laws apply to you.
Most of this works directly in your dashboard: download your data as a JSON file (your account, sign-in methods, sessions, security log, connections, data receipts, businesses, follows, reports you filed, the record of your parent's or guardian's agreement, if any, and Verified results); correct your name and language and add or remove email addresses; revoke an app under "Your apps" and unfollow a business; and delete your account (28-day restore window).
For anything else, use the privacy rights request form on avonao.com, which covers GDPR requests and requests under California and other US state laws, or write to privacy@avonao.com.
For people in Brazil, the Lei Geral de Proteção de Dados (LGPD, Law No. 13,709/2018) applies to the processing described in this policy. The rights in section 8 include the rights in Article 18 LGPD, among them confirmation that we process your data, anonymisation, blocking or deletion of unnecessary or excessive data, information about the public and private entities we share it with, and information about the possibility of refusing consent and what follows from refusing.
For LGPD requests, including the rights in Article 18, use the privacy contact at privacy@avonao.com. You can also complain to the Autoridade Nacional de Proteção de Dados (ANPD). Personal data is transferred to the United States and to the data region you chose, with the safeguards described in section 6.
For people in Japan, the Act on the Protection of Personal Information (APPI) applies.
We honor the Global Privacy Control signal as an opt-out. A browser that sends it, or a Do Not Track signal, is treated as "no" for the optional tools, and we do not ask again. Tools that use cookies or device storage, and all session recording, run only after you agree in the cookie banner, and never on sign-in, sign-up, second-factor, recovery, passkey, age or guardian pages. You can change your choice at any time with "Cookie settings" in the footer. See the Cookie Policy.
California Civil Code section 1798.83 lets California residents ask which categories of personal information a business has disclosed to third parties for their direct marketing. We make no such disclosures. You can still write to privacy@avonao.com to ask.
Avonao ID is not for anyone under 16: at sign-up it asks whether you are at least 16 and does not ask for a date of birth. If we learn that someone under 16 created an account, we delete it. A guardian-consent flow for younger members is built but switched off, and this policy is updated before it is switched on. The minimum age of 16 is at or above the age of digital consent in every EU country; national rules on contracts with 16 and 17 year olds can still apply, and in the UK the Children's code covers everyone under 18 who is likely to use the service. We do not knowingly collect personal data from children. If you believe a child has given us personal data, write to privacy@avonao.com and we will delete what we can, as described in section 7.
We make no decision about you that has legal or similarly significant effects based solely on automated processing. The order of the directory follows published, fixed rules (Ranking rules); reports are decided by a person.
We protect personal data with technical and organizational measures, including hashed sign-in links and codes, hashed recovery codes, encrypted authenticator secrets, separate regional services and databases for account data, a bot check on sign-up and business creation, and a security log of account events. No system is perfectly secure. If a personal data breach affects you, we notify you and the authorities as the law requires. Report suspected incidents to security@avonao.com.
We will tell you about important changes by email before they take effect.
Crea tu cuenta en un minuto con una passkey y luego conecta las plataformas que uses.
