Subprocessors
Last updated: May 15, 2026
This page is being adapted for English-speaking jurisdictions. The current content reflects French law. For questions, contact legal@scalenvia.com.
In accordance with Article 28 of the General Data Protection Regulation (GDPR), BravUp publishes the exhaustive list of its subprocessors. Each third party is selected for its level of compliance, its contractual guarantees (DPA — Data Processing Addendum), and the security of its infrastructure.
See also the Privacy Policy and cookies.
- Purpose
- PostgreSQL database, authentication, user file storage.
- Location
- European Union (primary region) — exact region visible in the Supabase dashboard.
- Data
- Identifiers (Google OAuth email)
- Interactions, sessions, contacts, journal, missions
- AI data (analyses, AI conversations, consents)
- Avatars and attachments (Supabase Storage)
- Legal basis
- Article 6.1.b GDPR (performance of the contract)
- Retention
- Lifetime of the account. Deletion within 30 days of request.
- Purpose
- Next.js hosting, edge functions, CDN, anonymised analytics.
- Location
- United States (free / pro tier US by default). Transfers governed by Standard Contractual Clauses Article 46 GDPR signed by Vercel.
- Data
- HTTP request metadata (truncated IP, user-agent, route)
- Server logs (30-day retention)
- Legal basis
- Article 6.1.b GDPR (performance) + Article 6.1.f (legitimate interest for observability)
- Retention
- Runtime logs: 30 days. Build logs: 90 days.
- Note
- Migration to an EU-region deployment is planned once the Vercel Pro EU threshold is met. In the meantime, the SCCs provided by Vercel guarantee Article 46 compliance.
- Purpose
- Payment processing for BravUp Pro, subscription management, billing, anti-fraud.
- Location
- Ireland (EU) + United States. SCCs signed and published.
- Data
- Email, Stripe customer identifier
- Payment method (never stored by us, tokenised at Stripe)
- Invoice history and webhook events
- Legal basis
- Article 6.1.b GDPR (performance of the paid service contract)
- Retention
- As long as the subscription is active + 10 years (legal accounting obligation). Payments stored at Stripe remain accessible via the customer portal.
- Purpose
- SSO authentication via the user's Google account (NextAuth).
- Location
- United States. SCCs signed under the Google Cloud DPA.
- Data
- Google email (only used as a unique identifier)
- Google name and profile picture (if the user grants them at the consent screen)
- Legal basis
- Article 6.1.b GDPR (performance — without Google OAuth, no authentication)
- Retention
- No local persistent copy beyond the NextAuth session. Refresh tokens stored encrypted in the database, deleted on sign-out.
- Purpose
- AI analyses via the Claude model (weekly coaching reports, session debriefs, recommendations). Analysis content is retained to allow history on BravUp side (`ai_reports` table).
- Location
- United States. Transfers governed by Anthropic's Data Processing Addendum, incorporated into the Commercial Terms of Service (SCCs included).
- Data
- Condensed user profile (goals, level, declared blockers)
- Weekly aggregated statistics (interaction totals, close rate, average mood)
- Excerpts from field reports and journal IF the user has granted the corresponding scope
- No email, no third-party name (contacts are hashed)
- Legal basis
- Article 6.1.a GDPR (explicit consent via /welcome) — revocable at any time from /settings.
- Retention
- Prompts sent to Anthropic are not logged at Anthropic beyond the ephemeral cache (~5 min). Responses are stored in `ai_reports` on BravUp side and purged after 6 months (see retention policy).
- Note
- The Anthropic DPA is automatically incorporated into Anthropic's Commercial Terms of Service; by using the Claude API, BravUp accepts the DPA and the Standard Contractual Clauses for non-EU transfers. No separate signature required.
- Purpose
- Pattern detection (daily and weekly cron) via gpt-4o-mini: adaptive mission generation, insights, public feed moderation.
- Location
- United States. OpenAI DPA signed and published.
- Data
- Aggregated statistics per user (30-day volume, close rate)
- Pseudonymisation: the transmitted identifier is the SHA-256 hashed email, never the email in clear
- Legal basis
- Article 6.1.a GDPR (consent) for personal mission generation. Article 6.1.f (legitimate interest) for automated public feed moderation.
- Retention
- OpenAI retains API requests for 30 days for audit purposes (zero-retention option available on request, to be enabled once the DPA is upgraded). Outputs are stored on BravUp side and purged after 6 months.
- Purpose
- Distributed rate limiting to protect API endpoints against abuse.
- Location
- EU region (eu-west-1 by default).
- Data
- Request counters per IP and per route (TTL ≤ 60 seconds)
- No persistent personal data: keys expire automatically.
- Legal basis
- Article 6.1.f GDPR (legitimate interest — security)
- Retention
- ≤ 60 seconds (Redis TTL).
- Purpose
- Server and client error tracking to improve app reliability.
- Location
- Multiple regions (US + DE depending on configuration). The BravUp project uses the EU region when available.
- Data
- JavaScript and Node.js stack traces (sensitive values are masked before sending)
- Error page URL, user-agent, hashed user identifier (never the email in clear)
- Legal basis
- Article 6.1.f GDPR (legitimate interest — service reliability)
- Retention
- 90 days.
All DPAs are in place
All our subprocessors above operate under an active DPA (signed separately or automatically incorporated in their commercial terms). BravUp also bases the activation of AI analyses on the user's explicit consent (Article 6.1.a GDPR), collected during onboarding (/welcome) and revocable at any time from settings.
Updates to this list
Any change (addition, removal, change of purpose of a subprocessor) is published here with the update date. If a change is likely to significantly affect your rights, you will be notified directly in the app.
Contact
For any question about our subprocessors or to exercise your rights (access, rectification, deletion, objection, portability), contact legal@scalenvia.com.
This page is public and accessible without authentication, in line with the transparency requirement of Article 12 GDPR.