# Provider accounts

<h2 align="center"><sub>This page means</sub></h2>

<table><thead><tr><th width="320">You own</th><th>ARIA owns</th></tr></thead><tbody><tr><td><sub>Billing disputes, refunds, and account recovery with each vendor</sub></td><td><sub>The product behavior described in this repo’s docs and UI</sub></td></tr><tr><td><sub>Key rotation, scope choices, and admin seats at each console</sub></td><td><sub>Storing the secrets you paste, when your deployment is configured correctly</sub></td></tr></tbody></table>

<h2 align="center">Three habits</h2>

{% stepper %}
{% step %} <sub>**First**</sub>

Name a **primary billing owner** and a **backup** for every vendor that can charge you.
{% endstep %}

{% step %} <sub>**Second**</sub>

Keep provider logins out of shared inboxes. Shared inboxes rot.
{% endstep %}

{% step %} <sub>**Third**</sub>

Revoke **Provider** access the same day you do not use them.
{% endstep %}
{% endstepper %}

***

<h2 align="center"><sub>Ask a question</sub></h2>

<p align="center"><sub><strong>Which vendor account still uses a founder’s personal email?</strong></sub> <br><sub>Fix that before your next fundraise diligence question.</sub></p>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ariaagi.com/ownership-and-responsibility/provider-accounts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.