Contact

Contact AmbiSecure — talk with the engineering team.

This is the contact point for AmbiSecure's engineering team — the people who build the SIM-Auth Platform and the eSIM, eUICC, Secure Element, and embedded-PKI capabilities around it. Reach out for a partnership inquiry, a telecom sandbox collaboration, a technical discussion, or an enterprise and IoT security question.

The engineering team works across eSIM and eUICC provisioning (GSMA SGP.22 / SGP.32, SM-DP+, RSP), Java Card and GlobalPlatform secure-element applets, embedded PKI and X.509, and FIDO2 / WebAuthn authentication. Technical inquiries that name the standards and interfaces in scope get the most useful first reply.

Form

Send us a structured inquiry

Pick the closest scope. We respond within two business days. For sandbox collaboration we'll typically request additional context before sharing documentation.

Inquiries that name the standards and interfaces in scope get the most useful first reply.

How this works: this form sends your enquiry directly to us, and we reply by email. It is protected by Google reCAPTCHA. Please do not include passwords or other sensitive account details. How your enquiry is handled. Full details are in our privacy notice.

How your enquiry is handled. This site is operated by Ambimat Technologies Pvt Ltd, a company within the Ambimat Group. Ambimat Technologies Pvt Ltd is responsible for enquiries sent through this site. When you press Send, what you entered — your name, email address and message, and any optional details you filled in — is submitted to Ambimat's enquiry system, Central Intake, which runs on Amazon Web Services. The address of the page you sent it from is recorded with it and, where available, the website you came from (its host name only) and the campaign details of a tagged link that first brought you to an Ambimat site.

It is used to route your enquiry to the right team and to reply to you. The team is notified that a new enquiry has arrived, and an automated acknowledgement is normally sent to the email address you gave. Each submission is checked on the server to filter automated spam and to stop the same enquiry being recorded twice.

Google reCAPTCHA loads when you start using the form, not before, and assesses whether the submission comes from a person; Google's Privacy Policy and Terms of Service apply to it. Google Analytics runs on this site only if you accept it (Cookie preferences); before you choose, and if you reject, this site does not load Google Analytics or Google Tag Manager at all. Nothing you type into the form is sent to Google Analytics. If you would rather not use the form, write to contact@ambimat.com.

Direct

Direct channels

For confirmed delivery, prefer email. We do not publish phone or instant-messenger contact for inbound technical inquiries.

Partnership & sandbox

contact@ambimat.com

Technical discussion

Use the form on this page. Indicate scope and we will route to the relevant engineer.

Address

Part of the Ambimat Group, India.
Ambimat parent company

Note: We do not respond to requests that imply unauthorized access, SIM cloning, key extraction, or any form of operator bypass — regardless of how they are framed. AmbiSecure builds secure identity, not workarounds.
Before you write

What a first message should cover

The more precisely a message names the layer, the stage, and the constraints, the faster it reaches the right engineer with a useful answer.

The interface in scope

Which layer you are working at — eSIM / eUICC provisioning (GSMA SGP.22 / SGP.32, SM-DP+, SM-DS, LPA), Secure Element and Java Card applets, embedded PKI and X.509, or FIDO2 / WebAuthn authentication.

The stage you are at

Concept review, architecture evaluation, an operator sandbox, or a fleet already in the field. Scope and depth are sized to the stage rather than assumed up front.

The constraints

Target silicon, connectivity assumptions, certification requirements such as Common Criteria, and any regulatory frame the deployment has to sit inside.

After you write

How the engagement runs

Engagement is narrow, documented, and inspectable — the same discipline described on the telecom-integration and about pages.

1 · Documentation first

Architecture, applet behaviour, key inventory, and threat model are shared for reading before any code is exchanged.

2 · Bounded scope

Each engagement is proposed with defined inputs, outputs, and exit criteria rather than a broad early commitment.

3 · Operator-controlled sandbox

Validation runs inside infrastructure the operator controls, with operator-set boundaries, observability, and termination authority.

4 · Findings

Interoperability evidence and stated assumptions are returned so a security team can review efficiently and decide the next step.

Frequently asked questions

How do I start a technical discussion with AmbiSecure?

Use the structured inquiry form on this page and select the closest scope — partnership, telecom sandbox collaboration, technical discussion, or enterprise and IoT security. We respond within two business days, and for sandbox work we request additional context before sharing documentation.

Which channel should I use for confirmed delivery?

Email is the reliable channel — reach us at contact@ambimat.com for partnership and sandbox inquiries. We route technical discussions to the relevant engineer based on the scope you indicate, and we do not publish phone or instant-messenger contacts for inbound technical requests.

What kinds of requests will AmbiSecure not engage with?

We build secure identity, not workarounds. Requests that imply unauthorised access, SIM cloning, key extraction, or operator bypass receive no response, regardless of how they are framed.

How quickly does AmbiSecure respond?

Within two business days. Sandbox collaboration usually starts with a request for additional context before any documentation is shared.

What should an operator include to speed up a sandbox request?

The interface in scope (SGP.22/SGP.32, SM-DP+, applet layer), the stage of evaluation, target silicon, and any certification or regulatory frame the deployment sits inside.