Firstweek, Inc. uses the third-party services listed below to provide the Firstweek platform. Each subprocessor has been evaluated for the data it processes and is bound by appropriate data processing terms.
Services marked conditional only process data if your workspace has enabled that specific integration. All other services are used across all workspaces.
| Subprocessor | Purpose | Data Processed | Location |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting, databases, and file storage | All application data | United States |
| Anthropic | AI inference for onboarding letter generation | New-hire onboarding content submitted by workspace administrators | United States |
| Stripe | Payment processing and subscription billing | Billing contact information and payment card data | United States |
| Resend | Transactional email delivery | Recipient email addresses and email body content | United States |
| Google Analytics | Website usage analytics | Browser identifiers, IP addresses, and behavioral data Marketing site only — not active inside the authenticated application. | United States |
| Slack conditional | Workspace communication integration | Channel messages and workspace metadata | United States |
| GitHub conditional | Source code repository integration | Repository content and organization metadata | United States |
| Atlassian conditional | Jira and Confluence integration | Project tickets and documentation content | United States / European Union |
| Google (Workspace / Drive) conditional | Google Drive document integration | Document content and Drive metadata | United States |
| Notion conditional | Workspace documentation integration | Page content and workspace metadata | United States |
| Jina AI | URL content extraction for onboarding link summarization | URLs of manually-added links submitted by workspace administrators Used to fetch readable content from URLs added to onboarding records. Only the URL is transmitted — no user PII. | United States |
| Bugsnag | Application error monitoring and crash reporting | Exception stack traces and request context, which may include user identifiers Receives unhandled exceptions only. Sensitive request parameters are not explicitly scrubbed — review before sending custom metadata. | United States |
We update this page when we add or remove a subprocessor. Material changes — adding a subprocessor that processes new categories of data — will be communicated to workspace administrators via email or in-app notice before the change takes effect.
For questions about our subprocessor relationships or to request a Data Processing Agreement, contact [email protected].