Subprocessors
Last updated June 10, 2026
Rebase uses a small set of trusted third parties to help deliver our service. This page lists them and what each one processes. It supplements our Privacy Policy and DPA.
Infrastructure & platform
| Subprocessor | Purpose | Data processed |
|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting, database, and encrypted object storage (S3) for screenshots and uploads | All service data, including account, ticket, and feedback data |
| Stripe | Payment processing and subscription billing | Billing contact and payment data (card data is held by Stripe, not Rebase) |
| Amazon SES (AWS) | Transactional email and notifications (sign-in codes, invites, mentions, digests) | Recipient email address and message content |
| Cloudflare & Amazon CloudFront | CDN and edge delivery of the website and the widget loader (cdn.rebase.dev) | Request metadata (IP, user agent) |
| Google (Google Analytics) | Aggregate, anonymized website usage analytics | Website usage events and online identifiers (e.g. cookies, IP address) |
Integrations you connect
The following are activated only when a customer chooses to connect them. When connected, ticket data you select is shared with that provider under the provider’s own terms:
| Provider | Purpose | Data processed |
|---|---|---|
| GitHub | Creating and syncing issues from tickets | Ticket title, description, and attached context you choose to sync |
| Linear, Jira, Asana | Issue-tracker sync (where connected) | Ticket title, description, and attached context you choose to sync |
| AI agents via MCP (e.g. Claude, Cursor) | Customer-initiated agent workflows you authorize | Ticket context you expose to the agent — see our AI Policy |
Changes & notice
We keep this list current. To be notified of additions or changes to our subprocessors before they take effect, email support@rebase.dev and ask to be added to our subprocessor-change notification list. Customers may object to a new subprocessor as described in the Data Processing Addendum.