Privacy Policy — IngevoraMirage

Privacy PolicyEffective 2 October 2026Who we areIngevoraMirage is run by Ingevora, Amman, Jordan — "Ingevora", "we" and "us" on this page. We make a studio where teams design face lenses and screen effects, and an API that delivers them to the teams' own apps.This policy covers the website and studio at ingevoramirage.ingevora.com and the delivery API at mirage-api.ingevora.com.What we collectOnly what the service needs to work.

What

What it is

Why we keep it

Your account

Your name, your email address, a hash of your password — never the password itself — and when you accepted the Terms.

To sign you in and send your account emails.

Workspaces

Each workspace's name, its members and their roles, and open invitations with the email address invited.

So your team works together with the right permissions.

Your content

The face lenses, screen effects and images your team uploads or makes, and every version you publish.

To show them in the studio and deliver them to your apps.

API keys

Each key's name and first few characters, who made it and when it was last used, and a hash of the key — never the key itself. The full key is shown once, when it is made, and never again.

To check the key your app sends, and so you can tell your keys apart.

Delivery counts

How many delivery calls each API key makes, per day.

To count usage against your plan, and to email a workspace's Owners as it nears the plan's limit.

Workspace activity

What happened in a workspace and who did it: an item made, published or archived, someone invited, joining or leaving, a role or key changed.

So your team can see recent changes on the workspace's home page.

Email choices

Which optional emails you want: usage alerts, payment notices, publish notices, someone joining.

To send only the emails you chose.

IP addresses

The network address each request to our servers comes from — from your browser, or from your app on a phone.

To limit how many requests one address can make. Our host, Fly.io, keeps server logs for about 7 days.

What we don't do

No advertising

No analytics

No tracking cookies

We don't sell your information or use it for advertising, and the site and the studio load no third-party trackers.Three small things are kept in your own browser, and none is a tracking cookie: your sign-in session, which lives in the browser tab you signed in from; the last workspace you opened, so the studio opens there next time; and the studio's theme and panel sizes, so it looks the way you left it.Who processes itFour companies handle data for us, only so the service can run:

For

Company

What it does

Resend

Sends account emails: sign-up links, password resets and invitations. Gets your name and email address.

Hosting

Fly.io

Runs our servers and the database that holds everything in the table above.

File storage

Tigris

Stores the files of your lenses and effects, and serves them to your apps.

Payments

Stripe

Takes card payments for paid plans on its own pages, and keeps the card. Gets the workspace's name, the paying Owner's email and the card details; we keep only the card's brand and last four digits.

Where the data is stored: in the United States. Our servers and database run in Fly.io's San Jose, California region; Tigris stores the files and keeps copies near the apps that fetch them.Your contentYou keep every right you have to the lenses, screen effects and images you upload. You let Ingevora store them, host them and deliver them to the apps that use your workspace's API keys — only to run the service for you.A published version never changes, so an app that asks for it keeps getting exactly what you tested.Your rightsYou can ask for a copy of the personal information we hold about you, ask us to correct it, or ask us to delete it. Write to admin@ingevora.com from the email address on your account. We answer within 30 days.You can change your name and your password yourself, on your Account page.You can also complain to the data protection authority where you live.ChangesIf we change this policy, we post the new version here with a new effective date. When a change affects how your information is used, we email account holders before it takes effect.Effective dateThis policy takes effect on 2 October 2026.