FuaFlow Teams
EN ↓

Aviso de privacidad de FuaFlow Teams

Vigente desde el 4 de noviembre de 2026

Lo importante, en cuatro renglones

Quién responde por estos datos

FuaFlow Teams la desarrolla y opera José Arturo Ornelas Brand, con domicilio en Calle San José de los Reynoso 115, Col. Bosques del Prado Sur, C.P. 20130, Aguascalientes, Ags., México. Para cualquier asunto de datos personales: [email protected].

Respondemos nosotros por lo que guarda el relevo, por lo que RevenueCat guarda de tu suscripción y por lo que nos mandas por correo. De lo que tú apuntas en Teams sobre tu equipo, y de los leads que repartes, respondes tú: tú decides qué apuntar y a quién mandarlo, y nosotros no lo vemos. También respondemos por los datos con los que verificamos tu empresa para FuaFlow Market.

Qué hay en tu teléfono

Cada envío se guarda en tu teléfono hasta que llega. Cuando el CRM de esa persona contesta que lo recibió, se borra lo que decía; si no contesta, se borra a los 7 días, que es lo más que lo guarda el relevo.

Si estás en un grupo de agenda

Un grupo de agenda junta a líderes de una misma oficina, grupo o región para pedirse a alguien para una cita. Entras solo si lo armas tú o con el código que te pasa otro líder, y sales cuando quieras.

FuaFlow Market (si tu plan lo incluye)

Lo que guarda el relevo

El relevo corre en Railway, Inc. (Estados Unidos), y se llega a él a través de Cloudflare, Inc. (Estados Unidos), que lo protege de ataques: Cloudflare ve tu dirección IP y cada petición al relevo, pero no lo que dicen los sobres, que van cerrados. El relevo guarda:

Fuera del nombre de tu equipo, el de tus grupos de agenda y los mensajes que alguien reporta, en el relevo no hay nombres de personas, teléfonos, números del día, metas, citas, direcciones, ventas ni leads: todo eso viaja cerrado y solo lo abren los teléfonos a los que va.

La copia de tu llave

Si guardas la copia de tu llave, se cifra en tu teléfono con la contraseña que pones ahí. Es PBKDF2-HMAC-SHA256 de 600,000 vueltas y AES-256-GCM. La contraseña no se guarda en ningún lado.

Permisos del sistema

Todos son opcionales. Se piden la primera vez que usas la función que los necesita (las notificaciones, al abrir la app por primera vez), y puedes negarlos o quitarlos cuando quieras en los ajustes del sistema. Si niegas uno, la app sigue funcionando; solo se apaga esa función.

En iPhone, los nombres de las personas de tu equipo pueden aparecer en la búsqueda del sistema (Spotlight) y en Siri y Atajos. Ese índice vive en tu teléfono.

Lo que sale cuando tú lo pides

Nada de eso sale solo: lo mandas tú, y lo recibe la app que elegiste, con sus propias reglas.

Respaldos y exportaciones

Suscripción

Teams se paga con una suscripción de Apple o Google, en tu cuenta de la tienda; nosotros nunca vemos tu tarjeta. Para saber qué plan tienes, la app usa a RevenueCat, Inc. (Estados Unidos). RevenueCat recibe:

No le llega nada de tu equipo, ni tu nombre, ni tu llave. RevenueCat trata esos datos por nuestra cuenta y solo para eso (su política).

Para qué se usan

Todo lo anterior sirve para que la app haga lo que dice:

No vendemos ni compartimos datos con nadie más, no hay publicidad y no se usan para entrenar inteligencia artificial.

Cuánto dura y cómo se borra

Tus derechos

Puedes pedir acceso, rectificación, cancelación u oposición sobre los datos que tenemos (los del relevo, RevenueCat, la verificación de tu empresa y los correos), o revocar tu consentimiento:

Menores de edad

FuaFlow Teams es una herramienta de trabajo para adultos.

Cambios

Si este aviso cambia, publicamos la versión nueva en esta página con su fecha antes de que entre en vigor.

English version

FuaFlow Teams privacy notice

Effective November 4, 2026. This is a translation; the Spanish version above prevails.

What matters, in four lines

  • What you record about your team lives on your phone. There is no account or password: your identity is a key that lives on your phone.
  • To talk to your team's FuaFlow CRM, Teams uses our server, the relay. What goes through it is sealed: the relay moves an envelope it cannot open. The little it does keep is listed under "What the relay keeps".
  • Your team's names and phone numbers, the leads you distribute, the customers of the sales passed to you and the ones who ask you through FuaFlow Market belong to other people. You (or your company) answer to them.
  • No ads, no usage analytics, no trackers. App errors stay on your phone.

Who is responsible for this data

FuaFlow Teams is developed and operated by José Arturo Ornelas Brand, Calle San José de los Reynoso 115, Col. Bosques del Prado Sur, 20130 Aguascalientes, Ags., Mexico. For anything about personal data: [email protected].

We are responsible for what the relay keeps, what RevenueCat keeps about your subscription, and what you email us. You are responsible for what you record in Teams about the people on your team and for the leads you distribute: you decide what to record and whom to send it to, and we don't see it. We're also responsible for the data we use to verify your business for FuaFlow Market.

What is on your phone

  • Your team: each person's name, phone numbers and emails, photo, position and the fields you fill in (for example employee number, nickname, territory, start date or best time to call). Also their stage (candidate, interview, training, active, former) and which teams they're in.
  • How everyone is doing: your reviews (on track, needs help, call later, meeting, no answer), what they need, the next step, your text and voice notes, the photos you attach and your calendar (meetings, one-on-ones, trainings and interviews).
  • What arrives from your team's FuaFlow CRM, only from those who join your team with your code:
    • their name, their phone, and which app and version they use;
    • their numbers for the day (calls, contacted, meetings, sales and amount, with its currency if they send it, and how many times they backed someone up at an appointment), while sending them is on; the switch is in their CRM;
    • how many of the leads you gave them were new and how many they already had;
    • the notice that they left the team;
    • their SOS: the reason, a note if they write one and, if their phone has it, their location: latitude and longitude to 5 decimals, its accuracy and how long ago it was taken (up to 2 hours). No one is ever tracked;
    • their "Voy a mi cita" check-ins: only the deadline and that it is a meeting, with no location or client, and the notice that they confirmed they're fine. If they don't confirm in time, Teams tells you; if their CRM sends an SOS because of it, it reaches you like any other;
    • their appointments, if they are directly on your team and share them from their CRM: the time, the status, the type, the area, whether they ask for a companion and in which role, whether they need a demo, how many people will be there, the note, the address and the names of who buys and who pays, and whether they confirmed. The address and the names are erased from your phone 7 days after the appointment;
    • their busy hours, without saying what they are, to know who is available;
    • whether they're going to the paired appointment you set up or can't make it, with a note if they write one, and whom they prefer to go to their appointments with;
    • the chat messages of the paired appointments you are part of: the text, the meeting point (place and time) and the phone number of whoever shares it. They are erased from your phone 7 days after the appointment;
    • the sales they pass to you, only if you turned on "I handle my team's sales and deliveries": the customer (name, phone numbers, email and address), the products, the amount and the note. They stay until you delete them, because they are now the company's customers;
    • about what you lent them: whether they have it, gave it away or passed it to someone else;
    • if you link your own FuaFlow CRM, your numbers for the day, like anyone else's on your team.
  • What you send to your team: its name, your name, your phone if you add it (so they can reach you in an SOS), goals, the leads you distribute (the rows of your file: name, phone and, if present, email, note and other columns) and the notice that you removed someone. Also:
    • the directory: the names of your team, so everyone knows whom they can go to an appointment with. If you turn on "Share the directory with my team", also each person's appointment roles and the phone number of whoever shared it when joining;
    • the pair for an appointment, only to those going: who goes with whom and in which role, the leaders' names and their public keys, so their FuaFlow CRMs can write to each other sealed, and your phone number if you are the companion. Never the phone number of anyone on your team;
    • what you write in the chat of a paired appointment, to those in it;
    • what you lend (demos, gifts and things to close a sale) and to whom, and the notice that you delivered a sale.

Each item is kept on your phone until it arrives. When that person's CRM confirms it got it, its content is erased; if it never confirms, it's erased after 7 days, the longest the relay holds it.

  • Your key: the secret half lives in your phone's keychain, and the public half is given to the relay. It's how your team recognizes you.

If you are in an agenda group

An agenda group brings together leaders of the same office, group or region so they can ask each other for someone for an appointment. You're only in one if you set it up or join with the code another leader gives you, and you can leave whenever you want.

  • To whoever leads each of the other teams in the group you send, for the next 7 days: your name; the name of each person on your team, their appointment roles and their busy hours, without saying what they are; and for each appointment, the name of whoever has it, the time, the status, the area, the type, the role it asks for, whether it needs a demo and who goes as companion. Never the address, the customers or phone numbers.
  • You receive the same from them about their teams. It's erased from your phone once that day is over, or when their team leaves the group.
  • If you ask for or offer someone for another team's appointment and both leaders say yes, each one gets from the other the name of their person and the public keys of that person and their leader. Each leader sends the pair only to those on their own team; the two FuaFlow CRMs write to each other, sealed, and both leaders receive that appointment's chat.

FuaFlow Market (if your plan includes it)

  • What's public: your store (its name, logo, cover, description, hours, areas, how you take payment and the details of your privacy notice: controller, address and contact) and your products (name, description, photos by link, price, deals, availability, options, specs, delivery and questions). Anyone with your link sees them, once your business is verified. The relay keeps them in plain text, because they're public, until they expire or you remove them. It also keeps in plain text how many requests each product gets and how long your team takes to take them, without who asked, and the date your payment covers, so requests stop when it ends.
  • Verification: we ask for your tax status certificate and talk to whoever runs the business. We write down your name or legal name, your tax ID (RFC), the date, what we checked and who checked it; we don't keep the certificate. We keep that record while your business is on FuaFlow Market and for one year afterwards, and we use it only for verification and to handle reports.
  • Your customers' requests arrive sealed, only for you and for whoever handles them. On your phone, Teams keeps for each one: the customer's name, phone and area, how and when they want to be contacted, what they're looking for, what they ask for with the option they picked, how many times they've asked and bought from your business, their keys and identifier; who you passed it to and who took it; their answer to “Have you been helped?” (including “Yes, and I bought”), and their private rating (stars and comment), which is about how someone on your team helped them. Taken, canceled, blocked, withdrawn or returned ones are deleted from your phone 30 days after their last change, when you open Teams; the ones nobody has taken yet stay until they close, and their 30 days start then. If the customer asks to be deleted, Teams deletes all of that customer's requests with your business when it connects. To the customer, the one who answers for this data is your business, with its privacy notice.
  • What the relay keeps about requests: the sealed envelope, the business, who it's for (identifiers, not names), the customer's identifier and the dates, without the product; to count each customer only once a day in each product's numbers, a fingerprint made from the customer, the product and the date, deleted the next day; if a request is left with nobody to handle it and is deleted so it can be resent, the customer's identifier and the business, for one day; blocks (the business and the customer's identifier), until the customer deletes their data; product reports (the product, the reason, who reported it and when), until 30 days after the product is removed or expires; and “delete my data” requests, for 30 days.

What the relay keeps

The relay runs on Railway, Inc. (United States), and is reached through Cloudflare, Inc. (United States), which shields it from attacks: Cloudflare sees your IP address and every request to the relay, but not what envelopes say, which travel sealed. The relay keeps:

  • your public identifier, your public key and your envelope key (the one others use to seal what they send you), and when your phone last connected;
  • your team's name, in plain text: it can be read, so choose one you don't mind being read. Also who created it and when;
  • if you link your FuaFlow CRM, that the CRM is yours;
  • if you are in an agenda group, the group's name, in plain text, which teams are in it and who set it up, and the codes to join while they're valid: a fingerprint, 1 hour at most. When the last team leaves, the group is deleted. Between the teams of a group, the relay only lets the agenda pass between those who lead them, and what concerns appointments between the people in them;
  • who is in your team (their identifiers, not their names), with which role, who invited whom, since when, and whether and when they left or you removed them;
  • invitations while they're valid: a fingerprint that can't rebuild the code, uses left, expiry (1 hour at most) and who used it;
  • envelopes waiting for a phone that is off, sealed, with who sent them, who they are for, their size, their time and what type they are (for example, the day's numbers or an SOS), never what they say. They are kept on the relay's disk, so a restart doesn't lose them, up to 7 days and at most 50 per phone, or 4 per teammate if that is more. Once delivered they are erased (from the disk, within an hour at most). When the queue is full, the oldest from whoever has the most waiting goes first, and SOS and confirmations are never thrown away while there is another envelope to drop. If you remove someone, whatever was pending between you is thrown away;
  • your IP address, up to a day in memory, to stop abuse: it is how new keys, teams and applications coming from one network are counted each day. It isn't written to disk or to the relay's logs. Railway and Cloudflare do record the address of each request in their own logs;
  • if you allow notifications, the token Apple (on iPhone) or Google (Firebase Cloud Messaging, on Android) gives your phone to receive them. When an SOS, a "Seen it" or an "I'm OK" arrives, the relay asks for an alert to ring. What concerns a paired appointment (the pair, whether they're going, the chat), what someone on your team asks to borrow and what you're asked for or offered in an agenda group also ring, like a message. If someone leaves your team, the alert shows without a sound. When anything else is waiting with the app closed, a quiet "something new" alert, at most every 15 minutes. The alert doesn't say who, where or what: it's a fixed text for each type. Apple or Google (United States) receive that token, that text and the type of alert;
  • if you report a message in an appointment chat, your phone sends us that text, the identifier of who wrote it, your reason if you write one, the appointment and your identifier, because the chat is encrypted and we can't read it any other way. We keep it for 90 days to review it, and we can remove whoever abuses from the relay. If you ask us to forget you, we remove your identifier from your reports; the report stays until the 90 days are up;
  • service logs, one line per event (a phone connecting, an envelope left waiting for someone, someone joining or leaving a team), with the time and the identifiers. No IP, no names, no envelope content, and not who writes to whom.

Apart from your team's name, your agenda groups' names and the messages someone reports, the relay holds no people's names, phone numbers, day numbers, goals, appointments, addresses, sales or leads: all of that travels sealed and only the phones it's meant for can open it.

Your key copy

If you save a copy of your key, it's encrypted on your phone with the password you set there, using PBKDF2-HMAC-SHA256 with 600,000 rounds and AES-256-GCM. The password isn't stored anywhere.

  • On iPhone, the copy goes to your iCloud Drive.
  • On Android, it goes to the Google Drive folder you choose, without signing in to Google inside the app.
  • That file travels with your account: we don't see it, and without your password no one can open it, not even us.
  • The key never goes into the regular backup or into Google's automatic backup.

System permissions

All optional. They're requested the first time you use the feature that needs them (notifications, when you first open the app), and you can deny or revoke them anytime in system settings. If you deny one, the app keeps working; only that feature turns off.

  • Contacts: only if you save your team to your phone's Contacts, so their calls show who's calling. To avoid duplicates, the app checks your address book on the phone; the contacts you already had aren't touched and nothing is uploaded.
  • Microphone: only to record a voice note. The audio stays on your phone.
  • Camera and photos: only to take or attach a photo, through the system picker; the app only gets the photos you choose.
  • Location: only when you tap "Use my current location" to save an address. Never in the background. To turn the coordinates into an address, the system asks its map service (Apple's, on iPhone).
  • Calendar: only if you turn on "My personal calendar", to see your events next to Teams'. They're read on your phone and sent nowhere.
  • Notifications: local reminders your phone schedules and, on iPhone, the relay's alerts when someone on your team asks for help or something is waiting with the app closed (see "What the relay keeps").
  • Face ID or biometrics: only if you turn on the app lock. The system does the check; the app never sees your biometric data.

On iPhone, the names of the people on your team can appear in system search (Spotlight) and in Siri and Shortcuts. That index lives on your phone.

What leaves when you ask for it

  • An address lookup in the system's map service, and a short map link you paste: the app opens it once to read the location.
  • What you send to another app: the number or username and the message when you tap WhatsApp, Messages, Telegram, Signal, FaceTime, Mail, Instagram or Messenger.
  • What you share: a PDF, a CSV, "Share with your AI" (a text you copy and paste into the AI you use: the app connects to none) or "Add to my calendar".

None of it goes out on its own: you send it, and the app you chose receives it, under its own rules.

Backups and exports

  • The backup is a .zip with your database, your voice notes and your photos. It's saved on your phone and, if you choose, in your own cloud (iCloud Drive on iPhone, or the Google Drive folder you pick on Android).
  • If you turn on "Encrypt backups", what you export or upload is encrypted with a password only you know.
  • The backup does not include your key.
  • What you export (CSV, PDF) or share with another app is up to you; once it leaves Teams, protecting it is on you.

Subscription

Teams is paid with an Apple or Google subscription, on your store account; we never see your card. To know which plan you have, the app uses RevenueCat, Inc. (United States). RevenueCat receives:

  • an anonymous identifier the app creates;
  • the purchase data the store reports: product, dates, price, currency and country;
  • technical data about the connection and the phone: IP, model and versions.

Nothing about your team, your name or your key. RevenueCat processes this data on our behalf and only for this purpose (its policy).

What it's used for

All of the above is used so the app does what it says:

  • leading your team;
  • getting your goals and leads to the people on your team, and their numbers to you;
  • helping your team with appointments: giving an appointment a companion, letting them write to each other and, if you are in an agenda group, asking each other for someone across teams;
  • knowing which plan you have;
  • showing your store on FuaFlow Market, getting customer requests to you and verifying your business;
  • stopping abuse of the relay or the chat;
  • working offline.

We don't sell or share data with anyone else, there are no ads, and nothing is used to train artificial intelligence.

How long it lasts and how to delete it

  • On your phone: "Delete my data", in Settings ("Delete all data" in version 1.0), erases what you recorded on that phone: people's records, activities, appointments, notes, voice notes, photos and products, and the copies the app keeps there. Your business's data stays so your team can keep working: the catalog you send your team, your FuaFlow Market store, open requests, sales to deliver, the day's numbers and your settings. Uninstalling the app does erase everything on the phone. What you saved elsewhere (backups in your cloud, your key copy, exports) is deleted where you put it.
    • It only erases what's on that phone: your team and the linked teams keep working for everyone, because your team may include people who lead their own team and pay for their own FuaFlow Teams.
    • That's why your key stays: while you lead your team, the relay keeps your team, your public key and your notification token. To have it forget you, write to [email protected].
  • On the relay:
    • envelopes are thrown away after 7 days or once delivered (from the disk, within an hour at most);
    • the notification token, when Apple or Google reports it no longer works (for example, because you deleted the app);
    • invitations and agenda group codes, when they expire;
    • chat reports, after 90 days;
    • if you leave a team or are removed, you stop receiving and whatever was pending between you is thrown away. To have us delete what the relay keeps about you or your team, write to [email protected].
  • FuaFlow Market: your store and products, until they expire or you remove them, or 7 days after what you paid for ends; your customers' data on your phone, as “FuaFlow Market” above says; the verification record, while your business is on FuaFlow Market and for one year afterwards.
  • At RevenueCat: write to us and we'll request it for you. The store keeps your account's purchase history.

Your rights

You can request access, correction, deletion or objection regarding the data we hold (the relay's, RevenueCat's, your business verification and emails), or withdraw your consent:

  • write to [email protected] with your name and how to reply to you, which data it's about and what you want us to do. Since there are no accounts, we'll tell you how to show the key is yours;
  • we reply within 20 business days at most and, if it applies, we carry it out within the next 15 business days. It's free;
  • we have no copy of what your team keeps on their phones: ask whoever recorded it;
  • if you disagree with our answer, you can file a data protection request with Mexico's Secretaría Anticorrupción y Buen Gobierno within the following 15 days; if we don't answer, once the deadline has passed.

Minors

FuaFlow Teams is a work tool for adults.

Changes

If this notice changes, we'll publish the new version on this page with its date before it takes effect.