MEET FINGERLYA clearer picture of every session.Explore the signals
Support

Help, from the people who build it.

Technical questions, billing, refunds, security reports and privacy requests all go to one address, and a person reads every message. Fingerly is a product of Badele LLC, a Wyoming limited liability company.

  • Emailsupport@fingerly.io
  • Documentationdocs.fingerly.io
  • Two business daysWhat we aim to reply within.
  • Last updated2 November 2026

One address. Every kind of help.

Whatever you need, write to the same address.

  • Technical helpIntegration questions, errors and unexpected results. The documentation answers many of them.Documentation
  • BillingTop-ups, auto top-up and usage live in the console. Write to us for anything they do not answer.Pricing
  • RefundsUnused credit can be refunded within 14 days of purchase. Write from your organisation owner’s email.Refund policy
  • Security reportsFound a vulnerability or an exposed key? Tell us at the same address.
  • Privacy and data requestsAccess and deletion requests, data processing agreements, and questions from your privacy team.Privacy policy
Write to ussupport@fingerly.io

To help us answer quickly, include:

  • Your organisation’s name
  • Request IDs for anything that looks wrong
  • The SDK and its version
  • The environment and key prefix involved, never the secret itself
  • What you expected, and what happened
Email the team

What happens after you write.

We aim to reply within two business days. That is an aim, not a guarantee, and no service level agreement is offered unless one is agreed in writing.

For anything that changes your account or money, such as a refund, we may ask you to write from the email address on the account, so we know the request is yours.

  • We never ask for a secret key
  • We never ask for a full card number
  • Every message is read by a person

Reporting a security issue.

Write to support@fingerly.io with what you found, how to reproduce it, and what it could affect. Give us a reasonable time to fix it before you disclose it publicly.

While investigating, do not access or change data that is not yours, and do not load-test or disrupt the service.

Exposed a secret key? Rotate it in the console first, then tell us.

[ IDENTIFY ][ UNDERSTAND ][ DECIDE ][ FINGERLY ]
Less guessing. More knowing.

Make the next connection a trusted one.

Start with the signals, keep your own decisions, and pay only for what you identify. No credit card needed.