the questions teams actually ask
Frequently asked questions.
Migration, faceprints, data handling, pricing, and compliance posture — answered plainly. Each answer is deep-linkable.
- How do I migrate from AWS Rekognition?
You don't rewrite — you re-point. SightRadar speaks the same request and response shapes as AWS Rekognition, so you keep the AWS SDK you already use and set one
endpoint_url. Your existingIndexFaces,SearchFacesByImage, andCompareFacescalls keep working.Our migration guide shows the exact two-line change side by side with boto3.
- What is a faceprint?
A faceprint is a compact numeric summary of a face — the biometric template a recognition system compares, stored by SightRadar as an embedding (a vector of numbers), never as the original photo. Two images of the same person produce faceprints that land close together; different people land far apart. The original image cannot be reconstructed from the faceprint.
More terms are defined in the glossary.
- Is my data used for training?
No. SightRadar processes your data only to return your results. We do not pool it with other accounts, do not use it to train general-purpose models, and never sell it. Detect and compare process images in memory and don't persist them; indexed faces live in collections you can delete any time via API or console.
See the trust page and Privacy Policy for the full posture.
- What does it cost?
Pricing is prepaid and pay-as-you-go, billed per photo processed (never per face), in USD. Real-time index is $0.00093 per photo, batch index is $0.00062 per photo, and search by face ID is $0.00062 per search. Stored faces cost $6 per million per month. There's no subscription and no minimum to start; minimum top-up is $50.
Run your own numbers on the pricing page calculator.
- Is it GDPR/BIPA compliant?
Compliance with laws like GDPR and Illinois' BIPA is a shared responsibility. SightRadar is built to support lawful, consented use: you are the data controller, we act as your processor, data is isolated per tenant and encrypted in transit, you control retention, and we never train on or sell your data. Our Terms require a lawful basis and, where required, consent — and prohibit unlawful surveillance or covert tracking.
What we can't do for you: obtain consent from your end users or decide your lawful basis — that's the controller's job. This isn't legal advice; see the trust page, Terms, and Privacy Policy.
- Which AWS Rekognition operations are supported?
CreateCollection, IndexFaces, SearchFacesByImage, SearchFaces, CompareFaces, DetectFaces, ListFaces/DeleteFaces, and ListCollections/DeleteCollection. Each maps to a SightRadar endpoint with a deep-linkable anchor in the API reference (e.g.
/docs#search-faces).- Am I billed per face or per photo?
Per photo processed, never per face. A photo with five faces costs the same as a photo with one, and a photo with zero faces is still a valid, charged, successful result. Control-plane calls like creating a collection are free.
- What can I use SightRadar for?
Consented, lawful identity and recognition workflows — event and wedding photo-tagging, KYC and identity verification, access control, touchless attendance, marketplace and dating trust, and more. Law-enforcement and mass-surveillance use is out of scope and prohibited by our Terms.
See the full list on the use cases page.
Still have a question?
Reach the team, or just grab a key and try it against your own photos.