Who operates this service
This service is operated by Atlas API.
Support email: ora202503@gmail.com
Data the workspace needs
When configured, account services process the name and email address supplied by Google, your account identifiers and session metadata. Legacy accounts created before Google-only sign-in may still hold a password hash or email-verification records until the operator removes them; no new password or email-verification records are created. API-key records contain a protected verifier, prefix, scopes and lifecycle metadata—not a recoverable plaintext key. The key creation screen shows the secret once.
Request and payment records
Gateway accounting records request identities, project and action, outcome, timing and credit changes. Replay-safe responses may be encrypted and retained to support idempotency and reconciliation. Order records hold payment references and amounts. Card details are entered on the configured payment page, not in an API-key form.
What a simulation does not do
Public playground fixtures run locally. Their JSON input never leaves your browser, and they do not create wallet charges. A live playground request is different: it uses your signed-in session and the server-side gateway ledger.
Cookies and secrets
Authentication uses session cookies and Google’s OAuth service with the openid, email and profile scopes only; no Google API data is requested and no sign-in email is sent by this site. The configured database, hosting platform and payment service may process the information necessary for their function. Do not send unnecessary personal data in API inputs. This interface does not store permanent API keys in local storage.
Access and deletion requests
Contact the operator to request account-data access, correction or deletion. Some payment and security records may need to remain for applicable legal obligations or dispute handling. The operator is named on this page, which also describes how your data is processed. No registered company, jurisdiction or tax details have been supplied, and this page does not invent them.
How your data is processed
The hosting and database infrastructure this site runs on processes every page and API request and stores accounts, sessions, API-key verifiers, the credit ledger, request records and encrypted replay responses. If you sign in with Google, Google returns your name and email address to this site. The input you send with an API request (every value in it) is sent from this site’s servers to external data-processing infrastructure that executes the operation. Your account email, account identifiers, API key and IP address are not sent. Personal data that you put into the input is processed there as well, so do not send personal data that the operation does not need. Payments are not enabled, so no card payment is processed.
How long replay responses are kept
So that a retry with the same Idempotency-Key is safe, the gateway stores each settled response encrypted for 24 hours. After that it can no longer be replayed, and a daily cleanup job deletes the encrypted copy. Request accounting records (request identifiers, project and action, outcome, timing and credit changes) stay in the account ledger; no automatic deletion schedule is published for them yet.