Sign up

Privacy Policy

Last updated: October 15, 2026

1. Who we are

Apigami is operated by Apigami SAS, a French société par actions simplifiée (“Apigami”, “we”, “us”). We provide the Apigami software that runs in your browser, the website apigami.com and a relay service that together let services and community-built applications you explicitly authorize work through your own browser, on the sites you approve.

You can reach us at contact@apigami.com for any privacy question or request.

2. What this policy covers

This policy covers your Apigami account and its dashboard atapp.apigami.com, Apigami running in your browser, the apigami.com website and the Apigami relay service that connects your browser with authorized services. It does not cover the sites you use through Apigami, nor the services you choose to authorize — each has its own privacy policy.

3. Data we collect

Your Apigami account

Using a service through Apigami, or building one, requires an Apigami account, identified by your email address. An account has no password: you sign in with a 6-digit code or a sign-in link that we send to that address. A code is valid for one hour and can be used once. We record whether you have confirmed your address, the language of the emails we send you, and the sessions that keep you signed in, which expire after 30 days without use. Each account belongs to a team; a team created for you is named after your email address, and a teammate can invite you to theirs by entering your email address.

A service you connect to may give us your email address to fill in the sign-in form for you. If Apigami has approved that service to vouch for the addresses it sends, your account is created or signed in without a code.

Browsers attached to your account

Setting up Apigami in your browser does not ask for your name or email. At first launch, Apigami generates a random installation identifier in your browser, plus a per-installation secret used to authenticate your browser to our service (we store only a hash of that secret, never the secret itself). We also record basic installation metadata: creation date, last-seen date, whether it is online, its version and platform, and, from version 0.15.0 of Apigami in your browser, the sites your browser currently lets Apigami access, so that a request is only sent to a browser that can run it.

From version 0.15.0 of Apigami in your browser, a browser is attached to your account only by a click in that browser. When a page of Apigami asks to use it — the connect page of a service, your account page, or the page where you let your AI tools use Apigami — Apigami in your browser opens its own window showing the email address of the account and, where there is one, the service and the sites it asks for. Clicking to accept, then accepting your browser's own permission prompt for those sites, attaches the browser to that account and, in the same click, connects the service and approves those sites; if you refuse that prompt, nothing changes. Closing the window attaches nothing. We record each of these requests: the account, the browser, the service and sites it named, and your answer. A request expires after 15 minutes if nobody answers it. An older version of Apigami in your browser has no such window: it is attached by the page of Apigami itself, when you complete that page in that browser signed in to your account, and it updates automatically.

A browser can be attached to several accounts, for example on a shared computer, and each account only reaches it through its own attachment. If your account already has a browser, the window asks you to name the new one, such as “Work laptop”; that name belongs to your attachment and nobody else's.

From version 0.15.0, to show who it is acting for, Apigami in your browser receives from us theemail address of each account attached to it. It shows that address in its attachment and authorization windows, and partly masked in its settings. On a shared computer, anyone using the same browser profile can see there which accounts that browser is attached to.

You can detach a browser from your account at any time, from your account page at app.apigami.com or, from version 0.15.0, from Apigami's settings in that browser. Detaching only removes your account: the other accounts attached to that browser keep everything, their authorizations and the site access your browser gives Apigami included, and your own authorizations stay with your account for your other browsers.

Services you connect to

When you connect your account to a service, we record that connection and its date. A service reaches your browsers only while it is connected to your account.

If a service can email you, its connect page shows two boxes, both unticked. The first lets it send you emails about your use of it: you tick it to use that service, and being connected is then what lets it write to you. The second, optional, asks for the news of that service, named with the team that publishes it; we record the date you ticked it. Apigami's own news have a box of their own, unticked, on a connect page and when you create your account, until you answer it: ticking it subscribes you, and once you unsubscribe we never ask again.

Authorizations

For every service-and-site pair you decide on, we record the authorization decision for your account: which service asked, which site domain it concerns, whether you approved or refused, and the dates of those decisions (including revocations). Since a browser can be attached to several accounts, from version 0.15.0 of Apigami in your browser every decision names the account it is made for: each authorization window names it, and asks you to choose when several accounts of that browser are connected to the service, and each line of Apigami's settings acts for the account it is listed under. The decision applies to that account only. An older version decides for every account attached to the browser. A decision applies to every browser attached to your account: approving a site in one browser approves it in the others, and a revocation in one browser revokes it everywhere. We need this record to enforce your choices — no service request is relayed without a live authorization — and to show you what is authorized so you can revoke it.

Data from the sites you approve

This is the sensitive part, so here it is precisely. After you explicitly authorize a service for a specific site — through Apigami's authorization window and your browser's own permission prompt — Apigami can, when that service asks and on that site only, read the following in your browser:

  • Session data: the site's cookies, including authentication cookies, and its site storage (localStorage and sessionStorage). Either a list of the stored entries, giving for each its name, the type and length of its value, and a preview: the first 40 characters of the value, or for a structured value the names of its first fields or its number of items. Or the value, up to 50,000 characters, of one entry the service names. When an entry's name suggests a credential (such as “token”, “session” or “password”), its value is withheld, from the preview too.
  • Page content: the text, the HTML or an outline of the structure of a page of that site open in your browser. Password, one-time-code and payment-card fields are removed inside the page, before anything is read.
  • Your open tabs on that site: their address and title, so the service can tell which one to work on. At the service's request, Apigami can also open a tab on that site, reload it, send it to another page of the same site, or close it.
  • Responses of the site: what the site answers to a request run with your session (see below).

Page content and responses are whatever the site shows you, so they can include personal information such as messages, contacts or account details on that site. They are sent only to the service you authorized for it; our relay passes them on in memory and does not store them, except the real-time stream events described in §7.

Session data is used in one of two ways:

  • Run in your browser (preferred): the request is executed inside your own browser using your session, and only the response is returned to the authorized service. Your session data never leaves your browser.
  • Session handoff: the cookies of that one site — the ones the service names, or all of them when it names none — are transmitted, over encrypted connections and through our relay, only to the service you authorized for it.

We do not store your session data on our servers: it passes through the relay transiently, in memory, for routing. We never use session data to profile you.

Network and console capture — Apigami Dev Assistant only

Apigami Dev Assistant is a separate, unlisted install for people who build applications on Apigami. In addition to everything above, it can record, for a site you have explicitly authorized and while you keep a tab of that site open, the network requests that tab makes (URLs, methods, headers, request and response bodies) and its console messages, and stream them to our relay so that your own AI tools can read them. Cookie, Set-Cookie and Authorization header values are removed in your browser before anything is sent; only their length is transmitted. The recording is kept in the relay's memory only, for at most 30 minutes after the last time your tools read it and never after your browser disconnects, and is never written to disk. It is available only to the accounts that browser is attached to. You can stop a recording at any time from Apigami's settings in your browser. The standard Apigami install does not have this capability.

At the request of your own tools, and on a site you approved, Apigami Dev Assistant can also take a picture of a tab of that site, and click, type, scroll or pick an option in it. The text it types is never sent back. To do this, your browser gives Apigami Dev Assistant access to every site when you install it, and keeps that access when you refuse a site or detach the browser from your account; our service refuses every request for a site you have not approved in Apigami's authorization window. Before it clicks, types, scrolls or picks an option, it sends us the host name of the page it is about to act on (such asapp.example.com), to check that it is not a site Apigami refuses to act on.

AI agents you let into your account

An AI agent that runs without a browser, in a terminal or on a server for example, can ask to sign in to your account. It gives you a link to open atapp.apigami.com, where you approve or refuse it. We record the name the agent gave itself, the IP address and theUser-Agent header of its request, your decision, its date and the IP address you decided from. If you approve, the agent receives an access token valid for 90 days, which we store only as a hash, with the date it was last used. Your account page lists these accesses, with their IP address and User-Agent, and lets you revoke any of them.

Terms you accept

When you accept our Terms of Use, we record the version you accepted, the date, the page you accepted them on and the IP address you accepted them from.

Server logs

Our relay and website keep operational server logs: timestamps, account and installation identifiers, service identifier, site domain, request type, status and errors, and standard web-server data such as IP address. Logs never include the content of your session data. We use them for security, debugging and reliability.

Emails we send

We email you what the service needs: sign-in codes and links, the confirmation of your address, the invitations a teammate asks us to send you, and an alert each time you let an AI agent into your account. We send Apigami's own news only if you asked for them, by ticking their box on a connect page or when creating your account, or by subscribing; each carries the link that stops them.

Emails a service sends you through Apigami. A service that declares it may email its users can ask us to write to you, and only to you while you are connected to it; its news need you to have ticked its news box too. We look up your address when sending and never give it to the service, and nobody can reply to these emails, so a reply cannot reveal it either. They leave in the service's name, from an address of apigami.tech. For each one we record the service, your account, whether it is about your use or news, the date and what became of it: sent, not delivered, or marked by you as spam, never its content. We send you at most 5 such emails a day, all services together, and stop a service's emails when too many people report them as spam.

The AI agent alert is sent to your account's email address as soon as you approve an agent's sign-in request. It gives the name the agent gave itself, the date and time of your approval, the IP address the agent's request came from and whether that is a different network from the one you approved from, the sites it can use in your browsers and how many browsers, the fact that it can create, change, deploy and publish your team's applications, and a link that revokes this access. It is sent so that you notice an approval you did not intend, for example one someone tricked you into, and can revoke it at once.

4. How we use data

Apigami has a single purpose: letting the services and applications you authorize work through your browser on the sites you approve. We collect and use the data above solely to:

  • run the requests of services you authorized, on the sites you approved;
  • enforce your authorizations and revocations before anything is relayed;
  • sign you in, and send the emails listed above;
  • keep a record of the terms you accepted, as proof of that acceptance;
  • secure, debug and maintain the service.

Nothing else. No profiling, no advertising, no unrelated analysis.

5. Sharing

Apigami's use of the data described above adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Concretely:

  • The data from the sites you approve — session data, page content, tab addresses and titles — is transferred only to the service you authorized for the site in question, and only to provide Apigami's user-facing feature — or where necessary for security (e.g. investigating abuse) or to comply with applicable law.
  • We never sell your data. To anyone.
  • We never use or transfer your data for advertising — including personalized, re-targeted or interest-based ads — nor for creditworthiness or lending purposes.
  • We never allow humans to read the data from the sites you approve, unless you gave explicit consent for a specific case, it is necessary for security purposes, it is required to comply with applicable law, or the data is aggregated and anonymized for internal operations.

What a service you connect to receives about you. A service identifies you by areference that is specific to the team that publishes it: two teams never see the same reference for you, so they cannot link you through Apigami. For each browser attached to your account, it receives a separate reference, the name you gave that browser, whether it is online, when it was last seen, and, among the sites that browser lets Apigami access, those you have approved for that service, and it is told when a browser is attached to or detached from your account. When a service shows one of its own pages in your browser's side panel, beside a site you approved, that page receives the address of the tab you are viewing on that site, for as long as it is shown. Itnever receives your email address from us, unless the service gave it to us itself when sending you to Apigami, or you choose to share it. When it emails you through Apigami, it is told whether the email left or why not, such as that you have not accepted its news or that your address cannot receive, and its team can see for 30 days when it wrote to you, the kind of email and whether you marked it as spam, by your reference only. The browser reference replaces your browser's installation identifier; a service your browser was already connected to before September 27, 2026 keeps the identifier it had received then as that reference.

The following providers process data on our behalf, under contract and on our instructions only:

  • Nhost — application backend and database hosting, running on Amazon Web Services infrastructure in Frankfurt, Germany (eu-central-1).
  • Netlify — hosting and delivery of the apigami.com website.
  • Postmark, operated by ActiveCampaign, LLC in theUnited States — delivery of our emails: sign-in codes and links, address confirmations, team invitations, AI agent alerts, our news, and the emails services send you through Apigami. It receives the recipient's email address and the content of the email, and tells us when an address bounces or reports an email as spam.

Applications hosted by Apigami. Some services you connect to are written by a team and run on Apigami: their code, their database and their logs. For those, Apigami acts as aprocessor on behalf of the team that publishes the application, which decides what its application does with your data and answers for it; Apigami processes that data only to run the application, and never for its own purposes. The same holds for the emails a service sends you through Apigami: we send them on behalf of the team that publishes it, without ever handing it your address. Three more providers take part, on our instructions only:

  • Cloudflare, Inc., in the United States — runs the application's code, serves its files, stores its SQLite database and carries its logs to us: the database stored in the European Union, execution placed near Frankfurt, the code and files on Cloudflare's global network.
  • A managed PostgreSQL provider — the database of an application that chooses PostgreSQL, in Paris, France.
  • Google Cloud EMEA Limited — the AI model an application may use, which the connect page lists among what the application may do: it processes what the application entrusts to it within the European Union, stores none of it and never uses it for training. A request flagged by its abuse filters may be kept up to 90 days, in the European Union, for review.

The record of each run of a hosted application is kept for 7 days, then deleted. What the application keeps in its own database is the publishing team's to decide.

Your data stays in Europe, except the emails we send and what Cloudflare processes for hosted applications. Nhost and Netlify host and process data within the European Economic Area. To deliver an email, Postmark processes the recipient's address and the email's content in the United States; that transfer is covered by the European Commission's Standard Contractual Clauses in our data processing agreement with ActiveCampaign. Cloudflare stores a hosted application's SQLite database in the European Union and runs its code near Frankfurt, but that code may run anywhere on Cloudflare's global network, which therefore holds the application's code, files and secrets. The traffic statistics of the addresses where hosted applications are served are stored by Cloudflare in the United States and Europe. Transfers to Cloudflare rely on its certification under the EU-U.S. Data Privacy Framework and, failing that, on the Standard Contractual Clauses of its data processing addendum. No other data leaves the European Economic Area.

6. Security

  • Encryption in transit: all traffic between your browser, our relay and authorized services uses encrypted connections (HTTPS / WSS — TLS).
  • Encryption at rest: the data we store (accounts, installation records, authorizations, real-time stream events, logs) is stored encrypted.
  • Credential hygiene: per-installation secrets, invitation links and the access tokens of AI agents are stored only as hashes; a database dump cannot be used to impersonate an installation or an agent, or to join a team. Accounts have no password to leak.

7. Revocation and retention

You can revoke any authorization at any time from Apigami in your browser. Revocation removes Apigami's browser permission for that site in the browser where you revoke it, and immediately stops the relay from routing anything for that service-and-site pair to any of your browsers. From version 0.15.0 of Apigami in your browser, it applies to your account only; an older version revokes for every account attached to that browser. Detaching a browser from your account cuts it off from the services connected to your account: what they were running in that browser for your account stops. The other accounts attached to that browser keep everything, the site access your browser gives Apigami included. Your authorizations stay with your account and keep applying in your other browsers. Removing Apigami from a browser stops everything in that browser.

The news of a service stop with the link at the bottom of each news email, in one click and without signing in: that link, run by our email provider, stops the news of every service at once, and the services keep working. Apigami's own news stop with the link at the bottom of their own emails. A service's emails about your use of it stop when you stop using it, from the link at the bottom of those emails or from your account page: it then reaches neither your browsers nor your inbox.

  • Session data, page content, tab addresses and titles, responses: not stored by us — they transit in memory only, for routing.
  • Requests to attach a browser: unanswered ones expire after 15 minutes; the record of each request and of your answer is kept for 30 days, then deleted.
  • Account: your email address and account records are kept while your account exists; deleted on request, together with its attachments, connections and authorizations.
  • Installation and authorization records: kept while your installation and your account exist, so your decisions (including refusals) keep being enforced; deleted on request.
  • AI agent sign-ins: a request that was refused, never answered, or whose agent never collected its token is deleted one day after it expired, 15 minutes after it was made or approved. An approved one, with the IP address and User-Agent of the agent's request and the IP address you approved it from, is kept while its token is valid, at most 90 days, and for 30 days after the token expires or you revoke it, then deleted.
  • Acceptances of our Terms of Use: the version, date, page and IP address of each acceptance are kept while your account exists, as proof of your acceptance, and deleted with it.
  • Sign-in codes and links: valid for one hour and usable once.Invitations: valid for 14 days.
  • Your acceptance of a service's news: kept while you stay connected to that service. Stopping the news clears it at once, for every service; leaving the service clears it too.
  • Record of the emails a service sent you: kept for 30 days, then deleted. It never holds their content or your address.
  • Record of a service's calls to the AI: the service, the date, the size in tokens and the outcome, never what was sent or answered, kept for 13 months, then deleted.
  • Real-time stream events: when an authorized service subscribes, on your behalf, to a site's real-time event stream, each event is journaled on our servers so the service can read it after the fact. The journal holds the event's content, and is kept for 30 days, then deleted.
  • Server logs: kept for 90 days, then deleted.
  • Emails sent: Postmark keeps a record of each email, including its content and those services send you through Apigami, for at most 45 days, then deletes it. Only Apigami can see it there, never the service.

8. Your rights

Depending on where you live, you may have rights to access, correct, delete, or receive a copy of your data, and to object to or restrict some processing. To exercise any of these — including deletion of your account or of your installation's records — email contact@apigami.com from the address of your account (or include your installation identifier, shown in Apigami in your browser). If you are in the EU/EEA, you may also lodge a complaint with your data-protection authority.

9. Children

Apigami is not directed at children under 13, and we do not knowingly collect their data.

10. Changes to this policy

We will post any change here and update the “Last updated” date above. Material changes will be announced in Apigami or by email where we can.

11. Contact

Questions, requests, complaints: contact@apigami.com.