Security packet
This is the packet a security or finance reviewer can read before a contract. Everyone who uses the workspace accepts the current terms and privacy notice at sign-up. The data-processing agreement is executed when the workspace owner accepts it in Settings. The download from that page is the executed copy.
Where data runs
The application and its database run in Frankfurt. Repository source is cloned only for the duration of a scan and then deleted from the scan machine. DebtDetect does not move that processing to another region unless a customer asks for it in writing.
Subprocessors
| Processor | Role |
|---|---|
| Fly.io | Application hosting and the separate scan machine, Frankfurt. |
| GitHub | Sign-up and repository access the customer authorizes. |
| Stripe | Card payment, tax ID collection, and VAT when checkout is connected. |
| Resend | A report overview email, only when a person asks, processed in Ireland. |
| Slack | Optional messages. Each customer installs DebtDetect into that customer’s own Slack. |
| Spaceship Spacemail | The support mailbox hello@debtdetect.org. |
Retention
Scan history follows the plan: 90 days on Starter, 365 days on Pro, 1,095 days on Business, and 1,825 days on Enterprise. Removing a person revokes that person’s sessions and Slack link. The audit row remains.
Offboarding
An owner or admin removes a member from the workspace. DebtDetect detaches that person’s repository credentials, deletes their sessions, removes their Slack identity link, and writes a member.removed audit event. The owner cannot be removed by another member.
Audit API and scan capacity
An Enterprise owner can create a token in the workspace. A security system calls the audit feed with that token and receives the same events shown on screen. The token is shown once and can be revoked. Scans run on the separate scan machine. A scan that stops sending a heartbeat is put back on the queue.