Stripe

Stripe still processes transaction, identity, fraud, and business data at very large scale.

Where permitted by law, Stripe may use personal and transaction data to assess eligibility for or promote other end-user services.

Stripe documents roles as controller, processor, and service provider depending on the activity.

Stripe says many automated and machine-learning uses avoid decisions with legal or similarly significant effects in many contexts.

Business users still decide what inputs, identity documents, and transaction data are sent into Stripe workflows.

Stripe provides privacy-center documentation and role-specific explanations for different types of users.

Stripe shares personal data with business users, financial partners, service providers, and entities involved in a transaction.

Link partners, BNPL providers, crypto-wallet services, identity-verification services, and fraud systems widen the sharing surface further.

Stripe clearly documents when it acts as controller, processor, or service provider.

Stripe maintains a privacy center and role-specific explanations for end users, end customers, and business users.

Business users manage their own privacy notices, consent collection, and many downstream disclosure choices.

Link and some partner services are user-initiated rather than universally applied to all Stripe users.

Stripe still collects online activity, engagement data, cookies, and device information across its services.

Stripe may use personal and transaction data for advertising, co-marketing, and end-user-service promotion where permitted by law.

Stripe provides privacy-rights and settings paths for end users and business users.

End-user services such as Link let users manage some settings and stored preferences.

Stripe is primarily a financial infrastructure platform rather than a public-feed advertising product.

Stripe may retain data after account closure or after transactions for legal, fraud, tax, accounting, and financial obligations.

Business users and financial ecosystem partners can keep their own copies of transaction and identity data outside a single user's direct control.

Stripe documents privacy-request paths for different user roles.

Account settings and Link management let users control some of their stored data directly.

Stripe is explicit that its retention is driven by financial, fraud, tax, accounting, and legal obligations.

Users and businesses can manage account settings, Link, and role-based access controls.

Stripe provides privacy-center and rights-request paths for multiple user roles.

Businesses are expected to obtain consents and manage their own end-customer privacy duties.

The controller, processor, and service-provider distinctions give customers a clearer model for who controls what.

End customers often must contact the merchant or business user that originally collected the transaction data.

Financial and compliance obligations can block immediate full deletion even when users want it.