Data and privacy
This page describes what the code running at the base URL does with data today.
What Compute Gateway stores
Compute Gateway has no database of its own. What it keeps, it writes to Drive, in a space reserved for Compute Gateway under the person’s id. Modules cannot read or write that space.
| Record | Contents | Kept under |
|---|---|---|
| Durable run | The module_ref, grant id, the spend:wallet grant id it pays under, the run’s state, the pending command and its result, status, exit code, step count, and the spend_grant_id if you sent one | The person and the module’s app |
| Nora interactive run | The module_ref, grant id, the spend:wallet grant id it pays under, the module’s state and step count | The person and the module’s app |
| Model Gateway link | The Granite request id and approved grant id, and the spend grant’s Granite request id, credential id and approved grant id from POST /v1/model/spend-grants | The person who signed in |
| Wallet grant | The Granite request id and approved grant id from POST /v1/spend/wallet-grant | The person who signed in |
| Connector | Name, base_url, auth style, the credential encrypted with a key Compute Gateway holds, and when it was created and updated | The person who signed in |
A one-shot call’s payload, stdout and output are not stored; they are
returned to the caller and dropped.
Logs. Operational logs are kept for 14 days.
Compute Gateway runs on AWS in the us-east-1 region (United States).
What it shares, and with whom
- Granite gets the person’s id, your app id, the grant id and the capabilities the module declares, on every call, tick and Nora message; and the person’s id, credential id and turn limit when they ask for a spend grant.
- Spend Gateway gets the person’s id, your app id and the fuel reserved and used.
- Drive gets the person’s id and your app id when Compute Gateway fetches your module, reads or writes the person’s app space, or saves a record.
- Model Gateway gets the person’s id and the module’s model requests when
a module uses
model.gateway.call, the spend grant id that pays for each, and the body you send toPOST /v1/model/credentials. - A connector’s API gets the request the module sends it, with the person’s credential attached.
- The caller gets back what the module printed and wrote, and a run’s final state.
How long
Compute Gateway deletes nothing on a schedule. Run, connector and link records stay in Drive after a run finishes or fails. Logs are the exception, at 14 days.
Deleting data
Not yet:
- No delete endpoint. Compute Gateway cannot delete a run record, a Nora run, a connector or a Model Gateway link. Registering a connector again under the same name replaces it.
- No export. There is no endpoint that lists a person’s records; reading one needs its run id or connector name.
- These docs do not cover what Drive’s own deletion does to these records.