This policy lists the data Paidwen keeps, for how long, and your rights.

The controller of your data is the seller below.

Seller

Paidwen

Email

[email protected]

Paidwen keeps the data of your account and of your organization.

• For each person who signs in: the email address, the name, and the identifier that Google or GitHub gives when you sign in with them.
• For each session: a hash of its token, its dates and a summary of the browser.
• For each organization: its name, its plan, its members and their roles, its invitations, its incident contacts, and its approval groups with the email addresses of their members.
• For each agent: its name, owner, team, description, model provider, environment, risk level, labels and budget, with a hash and a masked form of each of its keys.
• The rules and the permissions that you write.
• The Slack workspace connected to your organization, with its bot token encrypted.
• The plan, the events counted per day, and the identifiers of your subscription at Paddle. Paddle keeps your card details, and Paidwen never receives them.

The journal keeps what your agents do.

• Each decision: the agent, the tool, the parameters, the estimated cost, the verdict, the rule and the time.
• Each tool call and each model call that the SDK reports, with the model, the token counts, the cost and the duration.
• By default, the content too: the instructions given to the model, the messages in and out, and the tool parameters. You turn it off agent by agent, and the content then never reaches the journal.
• Each answer of an approver, with the person, the channel and the comment, and each incident with its author and its reason.

Your agents decide what they send. The parameters and the content can hold personal data of your own customers. For that data, you are the controller, and Paidwen processes it on your behalf.

Paidwen keeps each kind of data for a fixed time.

• The journal keeps each line 7 days on Free, 30 days on Starter, 90 days on Scale and 365 days on Business, then deletes it within a few hours. The audit comes from the journal and keeps the same time.
• The journal cannot yet delete the data of one person on its own: each line leaves at the deadline of its plan.
• The data of your account and of your organization stays while the account exists. After a deletion request, Paidwen deletes it within 30 days, except the billing records that the law requires to keep.
• Encrypted backups keep a copy of the databases for up to 6 months: the last 7 daily backups, 4 weekly backups and 6 monthly backups.
• A session lasts 30 days at most. A sign-in link lives 10 minutes, an invitation 7 days, and an approval link until the deadline of its request.

Paidwen uses the data to run the service and to bill it.

Paidwen uses the data to answer your agents, show the dashboard, send the approval requests and the incident alerts, count the events of your plan, bill your subscription and keep the service secure.

The legal basis is the performance of the contract with you. The security of the service relies on Paidwen's legitimate interest.

The website sets no cookie.

paidwen.com sets no cookie and uses no analytics or advertising tool. The dashboard, app.paidwen.com, sets one session cookie when you sign in, and one cookie that lives 10 minutes during a sign-in with Google or GitHub or a connection to Slack.

The dashboard also keeps the chosen organization and the state of its Live switch in the storage of your browser.

Seven providers process data for Paidwen.

Each provider receives only the data its purpose needs, and some of them process it in the United States. The subprocessors page lists them with their purpose and their country.

You can access, correct, delete or export your data.

You can ask to access, correct, delete or export your data, to restrict its processing, or to object to it. Write to the seller's email above. You can also file a complaint with your data protection authority.

Paidwen publishes each new version of this policy on this page.

The date at the top of the page is the date of the current version.