Privacy Policy
Effective date: 2026-10-08 · Version 1.1 · Comprehensive privacy notice (Aviso de Privacidad Integral) under Mexican law
This Privacy Policy explains how VINOC, S.A.P.I. DE C.V. ("VINOC", "we", "us") collects, uses, shares and protects personal data when you use esim2sip: the website esim2sip.io, the customer console at console.esim2sip.io, the public API at api.esim2sip.io, the eSIM install pages we send on your behalf, our transactional e-mails, and the esim2sip Console mobile app for Android and iOS (package / bundle id io.esim2sip.console).
This English text is a translation provided for convenience. The Spanish version (Aviso de privacidad) is the legally binding one under the Mexican Federal Law on the Protection of Personal Data Held by Private Parties (Ley Federal de Protección de Datos Personales en Posesión de los Particulares, "LFPDPPP") and its Regulations. If the two versions differ, the Spanish version prevails. A Portuguese version is also available.
1. Who is responsible for your data (data controller)
The controller (responsable) of the personal data described here is:
- VINOC, S.A.P.I. DE C.V., a company incorporated under the laws of the United Mexican States, operator of the esim2sip service.
- Registered address: [Domicilio: …]
- Tax id (RFC): [RFC: …]
- Privacy contact (personal-data department): hello@esim2sip.io
2. Who this policy covers
esim2sip is a business-to-business service: a wholesaler (the account) provisions eSIM-based mobile lines and connects them as SIP extensions to the phone systems (PBXs) of its own clients (companies). We process personal data of:
- Account users — the people who sign in to the console, the API or the mobile app (account owners and members, company administrators and viewers).
- Contacts entered by our customers — for example the e-mail address of an end user to whom an eSIM install link is sent, or the recipient of a notification channel.
- Call parties — the telephone numbers that appear in the call records of a line.
- Website visitors — people who browse esim2sip.io.
Where a customer enters personal data about its own clients or employees (company names, extension labels, delivery e-mails, PBX addresses), the customer is responsible for having a lawful basis to do so and for informing those persons; we process that data on the customer's instructions to provide the service.
3. Personal data we collect
We collect only what the service needs. The categories below reflect what the platform actually processes today.
3.1 Account and user data
- Display name, e-mail address, role, preferred language and time zone.
- Sign-in credentials: a password hash (argon2id; we never store the password itself), passkey public keys (WebAuthn) and, if you use "Sign in with Google", the identifier and e-mail address of your Google account.
- Sessions: refresh-token records with the IP address, browser or app ("user agent"), device name and time of each sign-in; the date and time of your last successful authentication.
- Invitations: the e-mail address invited and the inviting user.
- Support-view sessions: when our support staff view your account in read-only mode at your request, the session is recorded in your audit log.
3.2 Company and client data entered by the customer
- Company names, cost centres, tags, notes and white-label branding (logo, colours, display name).
- PBX connection details: host name or IP address, port, transport, and the SIP username and password of each extension (encrypted at rest, see section 10).
- eSIM delivery recipients: the e-mail address of the person who receives an install link, the language chosen, and delivery events (sent, opened install page, revoked).
- Notification channels: recipient e-mail addresses and, if configured by you, Slack or Google Chat webhook URLs (encrypted at rest, write-only).
3.3 Billing and fiscal data (account owners)
- Legal name, tax id (RFC), tax regime, postal code, billing e-mail address and billing currency.
- Invoices, credit notes, statements, charges, prepaid balance and ledger.
- Electronic invoices (CFDI) issued through an authorised certification provider (PAC), including the fiscal data required by the Mexican tax authority (SAT).
- Payments by bank transfer: amount, date, currency and the transfer reference you give us, and, when we import a bank statement, the counter-party text of the transfer as shown by our bank.
3.4 Line, eSIM and registration data
- For each line: the SIM identifiers assigned by the mobile core (ICCID, IMSI), the eSIM activation code (LPA) and QR code, the virtual number, and the line's state (active, locked, suspended).
- SIP registration status of the line on the mobile network (IMS) and on your PBX, registration history and uptime, and the public IP address and port from which the PBX registers.
- Results of SIP connectivity tests you or our support run against your PBX.
3.5 Call metadata (call detail records)
For every call handled by a line we keep a call detail record: calling and called numbers, direction, start, answer and end times, duration, SIP result codes and cause, codec and the internal node that handled the call. We do not record or store the content (audio) of calls. Call records are needed for billing, fair-use monitoring, troubleshooting and to answer your questions about a call.
3.6 Diagnostics: SIP packet captures
To diagnose a connectivity problem, our support staff can start a time-limited capture of the SIP signalling exchanged between our edge and your PBX or the mobile core (a "SIP trace"). Captures contain SIP messages (numbers, addresses, headers, SDP); they never include media (voice). Captures are started only on request or in the course of a support case, are limited in size and duration, and are deleted automatically (section 9). A redacted call ladder may be shared with you.
3.7 Audit logs and technical logs
- Audit log of actions in your account: who did what, when, on which object, with the IP address and user agent of the request. Account users can view a masked version in the console.
- Server logs and metrics for reliability and security. Logs never contain passwords, tokens, SIP passwords or eSIM activation codes; metrics carry no personal data.
- Bot protection: unauthenticated actions (sign-in, password reset, invitation acceptance, install pages) are protected with Google reCAPTCHA Enterprise, which evaluates device and interaction signals.
3.8 Website
esim2sip.io is a static website. It collects no personal data itself; our hosting provider keeps standard access logs (IP address, user agent, pages requested) for security. The site loads the Inter font from Google Fonts, which means Google receives your IP address when the page loads. We use no analytics or advertising scripts.
3.9 Mobile app access requests
The esim2sip Console mobile app Request access form collects a phone number. The number is stored with that access request, is used for customer support and the account, and is not used for tracking.
4. Sensitive personal data
We do not collect sensitive personal data (as defined in article 3 of the LFPDPPP: health, genetic or biometric data, racial or ethnic origin, religious or philosophical beliefs, political opinions, union membership, sexual orientation), nor financial or asset data beyond the invoicing and bank-transfer information described in section 3.3. If you enable biometric unlock in the mobile app, the biometric check is performed by your device's operating system; no biometric template ever reaches us. Please do not send us sensitive data in support requests.
5. Purposes
5.1 Primary purposes (necessary for the service)
- Creating and administering your account, authenticating users and keeping sessions secure.
- Provisioning mobile lines and eSIM profiles on the mobile core, connecting them as SIP extensions to your PBX, and monitoring their registration and health.
- Routing, completing and recording calls (call detail records), including fair-use and fraud monitoring.
- Billing: computing charges, issuing invoices, credit notes and CFDI, recording payments, collections and service suspension for non-payment.
- Sending transactional e-mail: invitations, password resets, eSIM install links, invoices, alerts, scheduled reports, security notices.
- Sending push notifications and in-app notifications to the mobile app when you enable them.
- Providing customer support, diagnosing connectivity problems (SIP tests, SIP traces) and keeping the audit log.
- Securing the platform: preventing abuse, bot traffic and unauthorised access; investigating incidents.
- Complying with legal obligations, in particular Mexican tax law (CFDI, accounting records) and lawful requests from competent authorities.
5.2 Secondary purposes (not necessary for the service)
- Sending product news and service announcements about esim2sip by e-mail to account users.
- Producing aggregate, non-identifying usage statistics to improve the service.
You may refuse the secondary purposes at any time without affecting the service by writing to hello@esim2sip.io with the subject "Limitación de uso" or through the notification preferences in the console. We never use your data for behavioural advertising, profiling or automated decisions with legal effects on you.
6. The esim2sip Console mobile app
The esim2sip Console app (Android and iOS, io.esim2sip.console) is a client of the same service: it shows the same data as the web console. Specifically, the app collects or processes:
| Data | Why | Sent to us? |
|---|---|---|
| Account identifiers and e-mail address | Sign-in and showing your account | Yes (same as the web console) |
| Session (refresh) token | Staying signed in; stored in the device keychain / keystore | Yes, to authenticate |
| Push token, installation id, platform, app version, OS version, device locale, time zone, optional device name | Delivering push notifications you enabled and listing your devices under Security | Yes; the push token is encrypted at rest |
| Phone number entered in the Request access form | Linked to that access request; used for customer support and the account; not used for tracking | Yes, with the request |
| Biometric unlock | Local convenience performed by the OS | No |
| Camera / clipboard | Only when you copy an activation code or show a QR code; nothing is read from the clipboard | No |
| Android only, with carrier privileges: SIM subscription identifiers (ICCID, IMSI, MCC-MNC) of an esim2sip eSIM installed on the phone | Matching the installed eSIM to your line and configuring APN and IMS settings on the device | Only the identifiers of esim2sip lines, to verify the line's status; nothing else |
Carrier privileges on Android. When an esim2sip eSIM profile is installed on an Android phone, the profile can grant the app "carrier privileges". With them the app may read the subscription identifiers of that eSIM (ICCID, IMSI, MCC-MNC) and write the access-point (APN) and IMS settings the line needs. These settings are written on the device only. The app never reads SMS, call logs, contacts, location or the identifiers of other SIMs, and sends nothing beyond what the service needs to confirm the line's status. On iOS the app opens Apple's eSIM installation flow with the activation code and has no access to SIM identifiers.
No advertising, no tracking, no sale. The app contains no advertising SDK, no third-party analytics and no tracking across apps or websites; it does not request the advertising identifier (IDFA / AAID). We do not sell or rent personal data and we do not share it for cross-context advertising. Crash-reporting and analytics SDKs are not used.
Account deletion. You can request the deletion of your user account from inside the app (Settings → Account → Delete account), from the web console (Settings → Data & privacy) or by e-mail (section 13). Removing a device or signing out deletes its push token.
8. International transfers
The service is hosted on Google Cloud in the United States (region us-central1). Personal data is therefore stored and processed outside Mexico and, for users elsewhere, outside their country. We protect these transfers with written data-processing terms with each provider, encryption in transit and at rest, access limited to named staff, and, for users in the EU/EEA and the UK, providers that offer the European Commission's Standard Contractual Clauses (Google, Mailgun). By using the service you acknowledge this hosting model.
9. Retention
We keep personal data only as long as needed for the purposes above or as the law requires. The periods below are enforced by the platform itself (database time-to-live rules and scheduled clean-up jobs) and are also shown in the console under Settings → Data & privacy.
| Data | Kept for | How it is deleted |
|---|---|---|
| Call detail records | 1 year | Automatic expiry (ClickHouse TTL) |
| Hourly / daily call totals, registration intervals and uptime | 13 months | Automatic expiry |
| Line status history | 1 year | Automatic expiry |
| SIP test results | 180 days | Automatic expiry |
| SIP packet captures (SIP traces) | 24 hours by default, never more than 7 days | Automatic deletion on the edge node |
| Audit log | 2 years | Automatic expiry |
| Sessions (refresh tokens with IP address and user agent) | 30 days after last use (+1 day) | Scheduled clean-up job |
| Password-reset records | 30 days | Scheduled clean-up job |
| Data-export files | 24 hours | Scheduled clean-up job |
| Mobile push tokens | Until you remove the device, sign out or the token becomes invalid | On request / automatic |
| Users, companies, extensions, eSIM data | While the account exists; closing an account keeps its records until deletion is requested | Erasure on request (section 13) |
| Invoices, payments, CFDI and related fiscal records | At least 5 years, as the Mexican Federal Tax Code requires (also after an erasure) | Never deleted by the platform |
Back-ups of the databases are retained for a limited period and overwritten on a rolling basis; data deleted from the live system disappears from back-ups when they expire.
10. Security
- In transit: all connections to the website, consoles, API and mobile app use TLS with HSTS; SIP signalling between our edge and your PBX can use TLS, and the mobile core is reached over an encrypted link.
- At rest: disks and object storage are encrypted by the cloud provider; in addition, secrets such as SIP passwords, eSIM activation codes, webhook URLs and push tokens are encrypted field by field with AES-256-GCM under keys derived with HKDF-SHA256 and bound to the record they belong to.
- Authentication: passwords are hashed with argon2id; passkeys (FIDO2 / WebAuthn) and Google sign-in are supported; account owners can require passkeys for their users; access tokens are short-lived and signed with EdDSA; sessions can be listed and revoked.
- Access control: every request is scoped to your account and, for company users, to their company; our administration portal is reachable only through a private network, requires a passkey, and every administrator has a role that limits what they can see; access to personal data by staff is logged.
- Abuse protection: rate limits, reCAPTCHA Enterprise on unauthenticated entry points, and automatic suspension safeguards.
- Incident response: if a security breach significantly affects your rights, we will inform you without undue delay, as article 20 of the LFPDPPP requires.
12. Your rights (ARCO), revocation of consent and limitation of use
You have the right to Access the personal data we hold about you, to Rectify it when it is inaccurate or incomplete, to Cancel (delete) it when it is no longer needed for the purposes above, and to Object to its processing for legitimate reasons (the "ARCO" rights), as well as to revoke the consent you have given and to limit the use or disclosure of your data.
Many of these you can exercise yourself in the console: edit your profile, export your account's data (Settings → Data & privacy, a ZIP with your data and 12 months of call records), manage sessions and devices, and choose which notifications you receive.
For everything else, send an e-mail to hello@esim2sip.io with the subject "Derechos ARCO" stating:
- your full name and the e-mail address of your esim2sip user (or, for contacts who are not users, the account or invitation that concerns you);
- a copy of an official identity document, or of the power of attorney if you act on someone's behalf;
- a clear description of the data and the right you want to exercise, and, for rectification, the correction and its supporting document;
- an e-mail address for our answer.
We answer within 20 business days of receiving a complete request and, if we grant it, make it effective within the following 15 business days, as articles 32 to 36 of the LFPDPPP provide; these periods may be extended once for the same length when justified. Access is provided as electronic copies free of charge; you only bear reasonable shipping or reproduction costs if you request otherwise. We may refuse a request when the law allows it, for example when the data must be kept for tax purposes, when the request would infringe third-party rights, or when the requester cannot be identified; we will tell you the reason.
If you believe your rights have been infringed, you may file a complaint with the Mexican data-protection authority, the Instituto Nacional de Transparencia, Acceso a la Información y Protección de Datos Personales (INAI, home.inai.org.mx), or its successor.
13. Deleting your account and data
You can send the request from this page. It asks only for the email of the account.
- Your user: request deletion in the mobile app (Settings → Account → Delete account), in the console (Settings → Data & privacy) or by e-mail to hello@esim2sip.io from the address of the user. We anonymise the user record, delete passkeys, passwords, Google links, sessions and devices, and re-address pending invitations. The last active owner of an open account must first transfer ownership or close the account.
- Your account: the account owner may ask us to close the account; lines are released and the account's users, companies and extensions are deleted on request after closure.
- What we must keep: invoices, CFDI, payment records and the audit trail of your account, which the tax code and our accountability obligations require; in the audit log the deleted user appears as "erased user".
- Data our customers entered about you: if you received an eSIM install link or a notification from an esim2sip customer, contact that customer first; we will help them fulfil your request.
14. Users in the EU/EEA, UK and other jurisdictions
If you use esim2sip from the European Economic Area, the United Kingdom or another jurisdiction with its own data-protection law, the following additional information applies. VINOC, S.A.P.I. DE C.V. is the controller and has not appointed a representative in the EU or UK; contact hello@esim2sip.io.
- Legal bases: performance of the contract with our customer (section 5.1); compliance with legal obligations (tax, lawful requests); our legitimate interests in securing and improving the service (security logs, audit, aggregate statistics, service announcements to existing customers); and consent where we ask for it (optional push notifications, secondary purposes).
- Your rights: access, rectification, erasure, restriction of processing, data portability (the console export), objection (including to direct marketing at any time), withdrawal of consent, and the right to lodge a complaint with your local supervisory authority.
- Transfers: Mexico is not covered by an EU adequacy decision; transfers to us and to our US providers rely on the Standard Contractual Clauses and the safeguards in section 8.
- Automated decisions: we make no decisions based solely on automated processing that produce legal or similarly significant effects on you.
15. Children
esim2sip is a business service and is not directed to persons under 18. We do not knowingly collect personal data from minors. If you believe a minor has provided us data, write to hello@esim2sip.io and we will delete it.
16. Governing law
This policy and the processing of personal data by VINOC are governed by the laws of the United Mexican States, in particular the LFPDPPP, its Regulations and the Guidelines for privacy notices (Lineamientos del Aviso de Privacidad). Any dispute is subject to the competent authorities of Mexico, without prejudice to the mandatory rights that the law of your residence grants you.
17. Changes to this policy
We may update this policy to reflect changes in the service, in our sub-processors or in the law. Changes are published on this page with a new version number and effective date; material changes are also announced by e-mail to account owners and, in the mobile app, with a notice at the next sign-in, at least 10 days before they take effect. The current version is always at esim2sip.io/privacy/ (Spanish: esim2sip.io/es/privacy/; Portuguese: esim2sip.io/pt/privacy/).
18. Version history
- 1.0 — 2026-09-28: first complete policy; replaces the provisional notice of 2026-09-25. Adds the esim2sip Console mobile app, sub-processor and retention tables, ARCO procedure and the section for EU/UK users.
- 1.1 — 2026-10-08: the controller is VINOC, S.A.P.I. DE C.V. The mobile app Request access form collects a phone number linked to that request, for customer support and the account, not for tracking. The app does not use crash-reporting or analytics SDKs.