On this page
Data and privacy
What router.africa stores about your requests, what it doesn't store by default, who can read saved content, and how to turn content storage on or off.
What router.africa stores
| Data | Stored? |
|---|---|
| Request details: the key used, time, model, token counts, response time, cost, status and request id | Yes. They run your dashboard and billing. |
| Prompts and responses (the message content) | No by default. Only if the workspace has switched saving on. |
| Request headers | Never. |
| API keys | Never in full. Only a hash is kept. |
router.africa doesn’t remove personal data from stored content. If you switch saving on and send personal data of your own users, you are responsible for having a lawful basis and for telling them.
Turn storage on or off
Saving is a setting for each workspace. It is off when a workspace is created. A workspace admin can switch it on in the dashboard. When it is on, router.africa keeps the content only to provide that feature to you. Switching it off stops future saving. Each change is recorded with a time.
Who can read stored content
Content that is saved can be read only by admins: router.africa staff admins and the admins of your organization. Members of your organization can’t. Every read is logged.
Limits
When saving is on, very large requests are saved only in part: the stored copy is cut at 1 MiB per request and marked as cut. If your connection closes in the middle of a stream, what had been received is saved and marked partial. A failure to save never fails your request.
Model providers
Your request is passed to the company that runs the model. That company follows its own data rules, which can differ from ours. router.africa doesn’t train its own models on your content and doesn’t sell it.
Read the full Privacy Policy and Terms.