Privacy

SegmentationAPI processes account data and customer media so the API can run SAM 3 jobs. This page describes what that means in practice. It is not legal advice.

Accounts. Sign-in uses Amazon Cognito with Google as an identity provider. We store the account identifier, verified email, and API key metadata needed to authorize https://api.segmentationapi.com. Key secrets are shown once at creation. We do not use account email as a public mailing list.

Media and jobs. Files uploaded through presigned URLs are stored in S3 so the GPU worker can read them. Job records include task IDs, prompts, status, timestamps, and pointers to output artifacts. Result URLs are short-lived. Download archives are built on demand and are not kept indefinitely. Treat prompts and source media as customer content. Do not upload data you are not allowed to process.

Billing. Paid accounts use Stripe. SegmentationAPI stores the Stripe customer and usage counters needed to meter $0.02 tokens. Card details stay with Stripe.

Agents and logs. The marketing site may use Cloudflare Web Analytics in production. API logs include request metadata used to debug auth and job failures. We do not sell personal information.

Requests. There is no postal address or privacy email on this hostname. Use the dashboard at https://app.segmentationapi.com for account changes, and GitHub at https://github.com/segmentationAPI for public documentation issues.