Privacy policy

Last updated: 2026-11-05 · Effective: 2026-10-28

Twin2.me builds a "twin": an assistant that answers in your voice, from the material you give it. This policy covers what we collect, what for, who we share it with and how long we keep it. The meeting assistant has its own section, because it records conversations with more people in them than you, and another section covers people who don't have an account and show up in what we process. Your rights are in Your rights.

Who is responsible

The data controller is Twin2.me LLC, a Delaware (U.S.) limited liability company, File No. 10807663.

Address: 8 The Green, Suite A, Dover, DE 19901, USA.
Email: info@twin2.me
Phone: +57 321 931 7379
Who handles your requests, questions and complaints: the Twin2.me team, at info@twin2.me. It is the only channel for exercising your rights.

This policy is for people who use Twin2.me from Colombia, Mexico and the United States, and for people in those countries whose data we process without their having an account. We operate the service from the United States: your data is stored and processed there (more under "International transfers"). The company name is Twin2.me; twinme is the name of the product and the assistant.

What we collect, and what for

Your account. Name, email, mobile phone number and your profile photo if you sign in with Google. Since October 26, 2026 an account is your email plus your mobile number, and the number is required. The number is used to identify your account and to send you service and pilot-program notices on WhatsApp. Your name and email come from Google, Microsoft or Apple when you sign in with them, or you type them yourself if you sign in with email and password. For the password we store only an scrypt hash, from which the password cannot be recovered. And, to stop anyone guessing passwords, we note how many times each email address and each IP address fails to sign in, and delete that within a day.
Your pixel, if you create one. In «Ajustes › Tu cuenta» (Settings › Your account) you can upload a photo so your twin draws your face in pixel art. The photo is read once by a vision model —the one in your own AI account if you connected it, or ours from OpenAI— and then discarded: we don't store it anywhere. We only keep features from a closed list (skin tone, hair color and style, eye color, glasses, beard and clothing color): the ones you leave after editing them and, to measure and improve how we read photos, the ones the model read the last time. We don't compute any print of your face: these are generic features many people share and they can't identify you. You delete them with «Quitar» ("Remove") in «Tu pixel», and they're deleted when you close your account.
The waitlist. If you sign up on the landing page, you give us your name, email and phone number (required) and, if you want, your industry. We also note where you came from (the referring page and the utm_source parameter) and the language of the page. We use it to tell you when there is room, by email and WhatsApp, and, added up with everyone else's, to learn which channels work.
The material you upload — files, recordings, links, whatever you connect from your clouds and your apps — to build your twin. It is yours and you can delete it. This includes:
- YouTube links: we download the audio through a residential proxy and transcribe it.
- Clouds: Google Drive, OneDrive and SharePoint, and Dropbox, only if you connect them.
- Apps you link through Composio, such as Gmail, Google Docs, Notion or Slack.
- Grain, if you connect it: we store your token encrypted and bring in your transcripts.
That material can name other people (see below), and can include sensitive data —health, for example— if you upload it. We process it only to provide the service: we do not look for it and do not use it for anything else.
What you did in ScalingOS, only if you ask for it. If, when you finish your Scan+Ecosistem in ScalingOS, you tick the box to create your second brain, create your Twin2.me account with the same email you gave in the Scan and confirm bringing it with the link you are given, we ask ScalingOS for that Scan: your answers, your Ecosistem level, the report it generated, your name, your city and your country, without your phone number. To ask for it we send ScalingOS your email, only to match it. ScalingOS only hands it over if the account's email matches the one in the Scan; until then we receive nothing. Your answers about what you do best, what makes you unique, your ideal client and your dream shape how your twin speaks, just like your answers in Questions. Your company details, your limitations and the ScalingOS report stay private: your twin only uses them when you are the one talking, unless you open them up. You can remove them from Your material, like everything else.
Your calendar, if you connect it. See below.
The audio of meetings you send the assistant to. See below.
Slack, if you connect it. The twin's own bot lives in your Slack workspace. See below.
What your twin writes in your apps (an email, an event, a document) only when you ask for it in "Hablar" (Talk) and press «Hacer» ("Do it"), or through the automatic tasks from meetings (see below).
Pilot-program surveys (the short pulses and the closing survey, where you tell us which plan would work for you) and bug reports you send us, with the screenshot you attach. Check the screenshot before sending it: it shows whatever was on your screen.
Minimal telemetry about product use: what failed, how long it took (in the requests table, with your user identifier) and how many tokens an answer cost. It is not shown to anyone outside the team and is not used to profile you.

Primary and secondary purposes

Primary (what we need to provide the service): creating and running your twin; identifying you and keeping your session; connecting your clouds and apps; transcribing, distilling and answering; making the minutes and the automatic tasks (on by default; you turn them off in Settings); sending you service notices (access, invitations, minutes, security); preventing abuse and fraud; handling your requests; measuring failures and service costs (telemetry); and complying with the law.
Secondary (not needed for the service to work): pilot-program surveys and notices (pulses, reminders, the closing survey).

How to refuse the secondary ones: write to info@twin2.me and we stop sending them, or turn off the emails in Settings ("Ajustes"). Saying no to secondary purposes changes nothing about your service: you keep using Twin2.me the same.

Sensitive data: recognizing your voice

Twin2.me can learn to recognize you by how you sound in your recordings, so it can mark which parts of a meeting are you without asking every time. This is biometric data and, for that reason, sensitive data. Today this feature is not available: it is off for everyone and we compute nobody's voiceprint. If we turn it on, this is how it will work:

It is optional. You are not required to give this data or to answer anything to use Twin2.me: the service works the same without it.
Only with your express written permission. It will be the "Recognize my voice" button («Reconocer mi voz») in Voices: your click is your express electronic written consent. Without that click we compute no voiceprint, for anyone. The permission is stored with a timestamp; so is revocation, and you can revoke it whenever you want with "Stop recognizing my voice" («Dejar de reconocer mi voz»).
What for. Only to mark which parts of a meeting are you.
Only your voice. The print is seeded from your spoken Answers (or an equivalent calibration you provide). We do not store voiceprints of other people in the meeting.
On our servers, encrypted. An open model (CAM++) runs on our machine; audio is not sent to a third party for this. What we store is an encrypted vector, not the seed audio.
How long we keep it. We delete it when you revoke, when you close your account, or after 12 months without use, whichever comes first. In no case do we keep it more than 3 years after your last interaction with us.
We never sell, lease, trade or profit from it. We don't disclose it to anyone, except to process it for you or if the law requires it.
Without your permission nothing else changes: we still tell which parts of a meeting are you by your name.

Your calendar

If you connect Google Calendar or Outlook, we do it through OAuth and with a consent separate from signing in: you can use Twin2.me without connecting any calendar.

What we read. Only your primary calendar, and at three moments:
- When you open Calendario (Calendar) in Twin2.me, the events in the range you are looking at (a week, a month or, at most, a year), private ones included: title, time, whether it has a video call, your response and how many guests there are. Only to show them to you on that screen: they are not stored.
- When you ask your twin about your schedule in Talk, the events in the range you ask for (31 days at most), only for that answer: those are not stored either.
- If your plan includes the meeting assistant, every few minutes, the events for the next 24 hours: title, start and end time, who organizes it, who is invited (name and email), and the text where the video-call link usually lives. The assistant skips events marked private and never stores them.
What for. To show you your schedule, so your twin can organize your day and, with the assistant, to know which meeting to join and at what time, and to put a name to who is speaking in the transcript.
What we write. Two things. We add the assistant's email to the guest list of the meetings you mark, and remove it if you change your mind. This is done without notifying the other guests, and we touch nothing else on the event. It is what lets the assistant join without somebody having to admit it by hand. And, only on Google Calendar and only when you press «Hacer» ("Do it") on a card in Talk, we create on your primary calendar the events you asked your twin to add: with no guests and without notifying anyone.
What we store. For each meeting the assistant is going to join: the title, the time, who is invited, and the join link encrypted — it carries the room password, so it never leaves through our API and never appears in a log. Your calendar tokens are stored encrypted with AES-256-GCM.
Disconnecting. When you disconnect a calendar, meetings that have not started yet are canceled and the permission is revoked. Whatever already reached your material stays, because it is yours, and you can delete it from there.

Data from Google

Besides signing in, which only gives us your name, email and photo, Twin2.me asks Google for access to two things, each with its own consent and only if you connect them: your Google Calendar and a Google Drive folder, read-only.

We use that data only to provide the features you see and switch on in Twin2.me, and to make them work for you:

Calendar: showing your schedule in Calendar; answering you in Talk when you ask about it; creating the events you approve in Talk; and, with the meeting assistant, knowing which meeting to join and when, inviting the assistant to it, and putting a name to who is speaking in the transcript.
Drive: bringing the files in the folder you choose into your material, so your twin learns from them. Building your twin is what you connect Drive for: what it learns can show up in its answers to the people you let talk to it, and only what is marked publishable gets there. You can remove any file from your material.

We do not use it for anything else. We do not sell or transfer it, we do not use it for advertising, profiling or credit decisions, and we do not use it to train or improve AI models, ours or anyone else's. We share it only with the processors listed under "Who we share it with", only to provide these features, and none of the model providers we choose trains on what it receives. If you connect your own AI account, your twin uses it under the terms you agreed with that provider. Nobody at Twin2.me reads it unless you ask us to in order to fix a problem, it is needed to investigate abuse or a security incident, or the law requires it.

Twin2.me's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The meeting assistant

If your plan includes it and you switch it on for a specific meeting, a twinme-branded assistant joins that video call (Google Meet, Teams or Zoom), records the audio and leaves the transcript in your material. Here is what it does and what it does not:

It announces itself. It joins under a name that says what it is, and posts a message in the meeting chat, in Spanish and in English, saying that it is recording and for whom. On Zoom it also triggers the platform's own recording indicator, which cannot be suppressed, and it accepts on its own the notices Zoom shows to whoever joins —that the meeting is being recorded, that AI Companion is on—: without that it would stay stuck at the door. It does not switch any of those features on.
Audio only. It does not record video, does not record screen sharing, and does not speak.
The audio is deleted. It is transcribed and, as soon as the transcript is ready, the audio file is erased: what remains is the text. We do not keep both.
Other people in the room are protected. The transcript enters your material as a private source; what other people said does not reach the search index or your twin's answers except after a leak filter and a quarantine that you resolve, not an operator of ours. Third parties' full names are blocked. If you were in a meeting recorded by someone else and you are not a user, see People who don't have an account.
The minutes are for you. From the transcript we draw a summary, what was left to do —and who took it on— and what mattered, even if you were not there. You see them in Calendar and we email them to you, which you can turn off in Settings. Nobody else receives them, they do not feed what your twin tells other people, and removing the meeting from your material removes them.
Your twin does your tasks, and it comes switched on. Automatic tasks are on by default. If the minutes say you have to do something that is done in an app you connected —sending an email, scheduling, creating a document—, your twin does it in your name with that app and tells you in Talk. Anything that moves money, and anything past a few actions per task, per meeting and per day, is left for you to approve; trading and crypto apps are blocked. It works from what was said in the meeting, including what other people said. To turn it off: go to Settings and switch off automatic tasks.
What we do not control. The organization hosting the meeting can stop the assistant from joining. That is not a failure: it is their decision, and we respect it.

Recording a conversation is your responsibility. In many places the law requires notifying everyone on the call, and in some it requires their express consent. The assistant gives notice on its own — its name and a chat message — but that does not replace you: you are the one who switches recording on, and you are the one answerable for having whatever permission your jurisdiction requires. If someone in the room objects, ask the host to remove the assistant and delete the meeting from your material.

People who don't have an account

Twin2.me processes data about people who never gave it to us and have no account: they show up in what a user uploads, connects or records, or in what they talk about with their twin. This policy applies to all of them. For any of the groups below, you can ask for access to, correction of or removal of your data by writing to info@twin2.me: tell us who you are and where you appear, we check it is you, and we act. As a rule for Colombia and Mexico, the user who brings us that data is the one who must have obtained your authorization (or given you the notice that applies) for us to process it on their behalf; if they didn't, tell us and we remove it.

Participants in recorded meetings

What: your voice in the audio (which is deleted once transcribed), what you say in the transcript and, if the calendar carries it, your name and email as a guest.
What for: making the transcript and the minutes for the user who sent the assistant. We make no voiceprint of you.
Basis: the authorization or notice obtained by the user who switches the assistant on (the assistant also announces itself in the chat). Your full name is blocked in answers, and what you say goes through a quarantine before entering the search index.
How long: the audio, until the transcript is ready; the text, while the user keeps that meeting in their material and their account.

Guests in Spaces

What: the messages you write in a Space (in Spanish, "Espacio") a user invited you to (the /espacio page, with a link and no account), and an access cookie (twin2me_pase, 30 days).
What for: so you can talk with the user's twin. The user can read what you write, and you see a notice that you are talking to an AI.
Basis: your decision to enter and write, after that notice.
How long: while the account of the user who created the Space exists.

WhatsApp contacts

What: your phone number, the identifier Meta gives your account (BSUID), your WhatsApp name and your messages, when you write to the twin of a user who connected WhatsApp.
What for: so the twin can answer you.
Basis: the authorization the user obtains, your writing to them on your own initiative, and the AI and privacy notice you get in the first reply.
How long: today we have no limit: they are kept while the user's account exists. You can ask us to delete them sooner.

Slack

What: the messages in the channels where a user put their twin's bot, with the names they have in Slack. Mentions of the bot and its replies stay in the twin's history.
What for: so the bot can serve whoever mentions it and the twin has context.
Basis: the authorization of the user who installed the bot in their workspace.
How long: channel messages, 30 days; what stays in the twin's history, while the user's account exists.

People mentioned in the material a user uploads

What: whatever the documents, emails or recordings a user uploads or connects say about you.
What for: so the user's twin learns from their own material. Originals are not indexed and only what is marked publishable gets out.
Basis: the authorization or notice the user obtains.
How long: while the user keeps that material.

Referentes: public figures

What: public information about some 20 real public figures. Every month we use Brave Search to look for their interviews, biographies and speeches (no social media), read them and distill them. Users talk with a simulation built from that. It is not affiliated with or endorsed by the person, and we say so on screen.
What for: so users can learn from those people's public ideas.
Basis: data of a public nature (Article 10 of Colombian Law 1581 of 2012; publicly accessible sources in Mexico).
How long: while the public figure is in the catalog.
Removal: if you are one of those people, or their representative, write to info@twin2.me and we remove your simulation. Today we do the removal by hand.

External connectors (MCP)

What: when someone connects Claude, ChatGPT or ScalingOS to a user's twin, those connectors receive the twin's identity and the material the user marked publishable.
What for: so the twin is available in those tools.
Basis and how long: the user's decision. We do not store the questions that come in that way, only usage counts.

Who we share it with

We do not sell or transfer your data, and we do not use it for advertising. To operate we rely on these processors, and on nothing else:

Provider	What it receives	Country	Does it train on it?
Amazon Web Services	Everything: the server, the database, files (S3), the meeting assistant (Fargate), alarms and backup email (SES).	U.S. (Ohio)	N/A: it only hosts it.
Resend	Your email address and the content of the messages we send you: sign-in links, invitations, minutes, reminders. No open or click tracking.	Brazil (São Paulo)	N/A: it only sends it.
Deepgram	Meeting audio, in batch and live, to transcribe it.	U.S.	No (we opt out of training on the audio).
Groq	Text, for the language model, and the audio you upload, to transcribe it with Whisper.	U.S.	No.
OpenAI	The text that enters the search index and the questions asked to your twin (for embeddings); images you attach in Talk and the photo for your pixel (vision, without storing them); and, sometimes, chat or distillation text. Never your original files.	U.S.	No (API).
Anthropic	Chat text, when we are the ones providing the model.	U.S.	No.
Composio	The permissions of the apps you link and everything that goes through them (what we bring in and what your twin reads or does). It does not store the content.	U.S.	N/A: it does not store the content.
Google	Your sign-in; your Calendar and Drive if you connect them; our email and the account the assistant uses to join Meet.	U.S.	We do not use that data to train; see "Data from Google".
Microsoft	Your sign-in (Entra); Outlook Calendar, OneDrive and SharePoint if you connect them; Teams, when the assistant joins a meeting.	U.S.	Its own terms apply; we give it no material for that.
Apple	Your sign-in, if you sign in with Apple.	U.S.	N/A: it only identifies you.
Zoom	Your authorization (OAuth) if you connect Zoom, and the meeting the assistant joins, through its SDK.	U.S.	Its own terms apply; we give it no material for that.
Dropbox	Your authorization and the files we bring in, if you connect it.	U.S.	N/A: it is your cloud.
Grain	Your token (encrypted) and the transcripts we bring in, if you connect it.	U.S.	N/A: it is your source.
Slack	The twin's bot in your workspace and the messages in the channels where it is.	U.S.	N/A: it is your workspace.
Meta (WhatsApp Cloud API)	The messages between you and your twin, and those of people who write to your twin, if you connect WhatsApp.	U.S.	We cannot promise that (see below).
Our WhatsApp engine	The number you link and the messages that pass through it (see below).	U.S.	No: it is ours and does not train.
Brave Search	The names of the public figures we look up for Referentes.	U.S.	N/A: it receives no user data.
Residential proxy	The YouTube URL you paste and the traffic of the audio download.	Varies: exits through the proxy provider’s network	N/A: it only passes the traffic.
ScalingOS	Your email, only to ask it for your Scan if you ask for that.	Colombia	N/A: it is a source, not a recipient.
Your own AI account	What your twin sends it, if you connect OpenAI, Anthropic, Gemini, Mistral or another provider, or your Claude subscription.	Per your provider	Up to you: your terms with that provider apply.

Composio has a signed data processing agreement (DPA) with us and works with "Don't store data": it does not store the content. It does keep an audit log for up to 1 year and temporary files for 24 hours.
Your own AI account. If you connect yours, traffic goes to yours and not to ours, distilling your material included, unless it runs out and your plan includes our backup. The terms you accepted with that provider apply: for example, Gemini's free tier does train on what it receives. You decide which one you use.
WhatsApp has two parts. (a) Meta's Cloud API, only if you connect WhatsApp: the messages between you and your twin go through Meta's WhatsApp Business platform. That includes the questions your twin asks you and your answers, and, with the meeting assistant, the follow-up questions a meeting leaves, which name the meeting and refer to what was said in it. Meta handles them on our behalf and keeps them for at most 30 days. You can answer the same questions in Twin2.me without connecting WhatsApp. (b) Our own engine: a separate service of ours, with its own server and database, that links a WhatsApp number in a way similar to WhatsApp Web. It is not an official WhatsApp client. Today the pilot-program reminders to your mobile phone go through it.

None of the model providers we choose (Groq, OpenAI and Anthropic) trains on your material, and Deepgram transcribes without using your audio for training. Meta is the exception we cannot vouch for: its terms for this service let it use messages to improve it and say nothing about training models, so we do not promise it. If any of this ever changed, this page would change first.

International transfers

Where your data is. It is stored in the United States (AWS, Ohio). Almost all our providers are there too. Email is sent by Resend from servers in Brazil.
Colombia. The United States is a country with an adequate level of protection according to the Superintendencia de Industria y Comercio. For sending email from Brazil, and for any other case, we rely on your authorization, which you give us by accepting this policy, and on each processor handling the data on our behalf under its terms of service (with Composio, a DPA as well).
Mexico. What we send to our providers is a remission to processors that handle the data on our behalf, and it does not need your consent. We make no transfers to third parties for their own purposes. The only exceptions: if a law or a competent authority requires it, and if Twin2.me merges or another company acquires it. In that case whoever succeeds us is bound by this policy and we will tell you. ScalingOS is a source you ask for, not a recipient: we only send it your email to ask for your Scan.

How long

Your material, while you have an account or until you delete it. Deleting a source deletes it for real, file included. For a meeting it also takes its minutes, the guest list, the names of who spoke and the follow-up questions you had not answered yet; what is left is the meeting's title and date from your calendar.
A meeting's audio, until the transcript is ready. After that it does not exist.
Calendar events that never got recorded are cleaned up with the rest of the meeting history.
Slack messages from channels, 30 days.
WhatsApp and Spaces contacts and messages, while the account of the user who receives them exists.
Request telemetry (latency and user identifier), 30 days. Failed sign-in attempts, 24 hours. The bot's logs, 30 days.
Database backups, 30 days. Disk snapshots, the last 7 daily ones. Previous versions of files in storage, 90 days; those of twin files expire after one day. What you delete may remain in those copies until they expire.
Your voiceprint, if it is ever turned on, under the schedule in Sensitive data.
The waitlist, surveys and bug reports, while the program's activity lasts or until you ask us to delete them, if sooner.
Your account, until you close it. Then everything hanging off it goes. All that remains is an anonymous record with the SHA-256 hash of your email, so we don't invite you again unless you ask and to prevent abuse; it does not let anyone recover the email.
Closing your account. You can close it whenever you want by writing to info@twin2.me from your account email. If you are a pilot, you can also do it yourself in Settings, under "Dejar de ser piloto" (Stop being a pilot).
At processors: Composio keeps the audit log for up to 1 year and temporary files for 24 hours; Meta keeps WhatsApp messages for up to 30 days.

Cookies and tracking technologies

We only use strictly necessary cookies. All of them are HttpOnly, Secure and SameSite=Lax. We use no analytics or advertising cookies, and we do not track you across sites.

Name	What for	Duration
`twin2me_sesion`	Your user session.	7 days
`twin2me_pase`	A guest's access to a Space.	30 days
`twinme_sso`	The meeting assistant's sign-in (an internal process of ours).	Internal
`twin2me_admin`	The team's administration panel session.	8 hours
`localStorage`	Only interface preferences, in your browser.	Until you clear it

Only the sign-in page (/entrar) loads third-party scripts: Google's (accounts.google.com) and Apple's, for their sign-in buttons; those providers can see your IP address and set their own cookies, under their own policies. The rest of our public pages load nothing from a third-party domain: no fonts, no measurement tags, no social widgets.

Do Not Track and Global Privacy Control (GPC). Because we do not track you across sites and do not sell or share your data for advertising, there is nothing to switch off. We still treat the GPC signal from your browser as an opt-out and honor it.

How we protect it

No model is trained on your data. A twin has no weights: it is your corpus, your distilled voice and your persona specification on top of a model that does not change. There is no model trained on you.
Your original files are not indexed and a query does not touch them. Only what is marked publishable enters the search index.
Your cloud and calendar permissions are stored encrypted with AES-256-GCM, and so are meeting links, because they carry the room password.
Your files do not pass through our server: they upload straight to storage with a signed, single-use permission.
If there is a security incident affecting your data, we will tell you without undue delay and, where the law requires, the authority: the Superintendencia de Industria y Comercio in Colombia and whichever authority each U.S. state's law sets.

Artificial intelligence and automated decisions

What your twin says is generated by an AI. It can be wrong. Guests in a Space see a notice that they are talking to an AI, and on WhatsApp your twin says so in its first reply to each contact.
We make no automated decisions with legal or similar effects about you, and we do not profile you.
What the automatic tasks from meetings do on their own is carry out in your apps what the minutes say is yours to do, within the limits and approvals described in The meeting assistant. They come switched on and you turn them off in Settings. Anything that moves money always asks you.
We follow the principles of transparency, purpose, security and accountability that Colombia's data protection authority asks for AI: we process only the data we need, we tell you what we do with it, and you can hold us to account.

Your rights

In every country

How to exercise them. Write to info@twin2.me from your account email, with: your name, where you want the answer, which right you are exercising and over which data, and, if you are not writing from your account or a representative is asking, a document proving identity or representation. If something is missing, we ask for it within the next 5 business days; in Colombia, if you don't complete it within 2 months, we take it as withdrawn. Exercising your rights is free. We verify your identity before handing over or changing anything. If you have no account, tell us who you are and where you appear.
A copy of your data, if you ask for it.
Closing your account. You can close it whenever you want by writing to info@twin2.me from your account email. If you are a pilot, you can also do it yourself in Settings, under "Dejar de ser piloto" (Stop being a pilot). Everything hanging off it goes.

Colombia

Law 1581 of 2012 and Decree 1074 of 2015. You can know, update, rectify and delete your data, withdraw your authorization, ask for proof of it, and be told how we use your data. Access is free at least once a month and every time this policy changes.

Inquiries: we answer them within 10 business days, extendable by 5 more business days if we explain why.
Claims (to correct, delete or withdraw): 15 business days, extendable by 8 more business days.
Complaint to the SIC. You can only go to the Superintendencia de Industria y Comercio (www.sic.gov.co) after having made a claim to us (a prerequisite).

Mexico

Federal Law on the Protection of Personal Data Held by Private Parties. You have the rights of access, rectification, cancellation and opposition (ARCO), you can withdraw your consent and limit the use or disclosure of your data.

We answer within 20 business days and, if it applies, carry it out within the following 15 business days.
If you are not satisfied, you can go to the Secretaría Anticorrupción y Buen Gobierno, which is the authority.
To refuse the secondary purposes, see "Primary and secondary purposes".

United States

Depending on your state's law, you can know what data of yours we hold and ask for a copy, delete it, correct it and receive it in a portable format. We do not sell or share your personal data for targeted advertising, and we do not use it for that. We do not discriminate against you for exercising your rights. Sensitive data, such as your voice, only with your consent.

Timing. We answer within 45 days at most; if we need more, we tell you.
Appeal. If we deny a request, reply to our email with the word "appeal" and we review it again and answer within 45 days at most. If you are still not satisfied, you can go to your state's attorney general.
Authorized agent. You can make a request through another person you authorize in writing; we will ask for that authorization and for them to verify your identity.
Categories we collect (last 12 months): contact and identification data; the content you upload or connect (text, audio, images, files); product usage data; and, if you ever turn it on, your voiceprint. We share them with the processors in the table above, only to provide the service.
California "Shine the Light." We do not give personal information to third parties for their own direct marketing.

Minors

Twin2.me is only for people aged 18 or over. It is not directed at minors and we do not knowingly collect data from anyone under that age. If we learn that we hold a minor's data, we delete it. If you think that has happened, write to info@twin2.me.

Changes and effective date

Effective: 2026-10-28. Last updated: 2026-11-05 (adds your pixel).
If we make a material change, we tell you by email or inside the app before it applies. If the change alters what we use your data for, we ask for your authorization again.
The database holding your data is kept for as long as the activity it is used for lasts: the service and the pilot program, plus whatever time the law requires of us.