Stripe Privacy Center (supplemental privacy notices)

Stripe · Official agreement

Read the agreement

52 of 266 cards in Sharing & Disclosure

Sharing & Disclosure · Company practice

BNPL prequalification can share limited data before you select a provider

When a Business User displays BNPL options, limited data such as name, email and proposed transaction amount may go to participating providers to assess a prequalified offer. The recipient is an independent controller under its own policy; an offer does not necessarily mean financing approval. Link lets users choose BNPL or supported crypto payments.

Supporting quotations

When using Link you can choose to pay for purchases using Buy Now, Pay Later (“BNPL”) services or crypto wallets.
When a Business User displays BNPL options through a Stripe payment interface, Stripe may share limited Personal Data—such as your name, email address, and the proposed transaction amount—with participating BNPL providers. This enables those providers to assess whether to display a pre-qualified offer to you.
A BNPL provider that receives this information acts as an independent data controller and processes the information in accordance with its own privacy policy. Displaying a pre-qualified offer does not necessarily mean that you will be approved for financing.

Qualifications & exceptions

  • Displaying a pre-qualified offer does not necessarily mean that you will be approved for financing.

Sharing & Disclosure · Company practice

Selecting BNPL permits application data exchange and discrepancy retention

After selection, necessary data goes to and from the provider for application and transaction completion, with checkout notice of data/recipient. This may include name, address, email, IP, phone, birth date, transaction data and SSN only if required by chosen financing; similar information is received and retained for discrepancies. Data supplied to Link follows its terms/policy, while directed sharing follows the provider’s. The saved notice names Affirm/Klarna merchant options and Link–Klarna account connection.

Supporting quotations

If you select a BNPL provider (e.g., Klarna), Stripe will send information to and receive information from that provider as necessary to enable you to apply for and complete the transaction.
social security number (we will only collect and share this data if required by your choice of financing)
Stripe will also receive and retain similar information from your choice of BNPL provider for any discrepancies.
Any data we share at your direction, with a BNPL provider of your choice, will be subject to their terms of use and privacy policy.
While merchants can enable Affirm or Klarna as a payment method, Link users can connect their Link and Klarna accounts.

Qualifications & exceptions

  • social security number (we will only collect and share this data if required by your choice of financing)

Sharing & Disclosure · Company practice

Crypto wallet payments share identity data, with explicit consent for Phantom onward KYC sharing

Using a supported crypto wallet such as Phantom requires sharing certain personal data, potentially name, address, birth date, government ID and KYC information. Phantom-directed onward KYC sharing to approved partners requires explicit consent first. Link data follows its own terms/policy; wallet and onward sharing follows the relevant provider’s terms/policy. The saved notice identifies Phantom as currently supported without guaranteeing future availability.

Supporting quotations

This may include your name, address, date of birth, government-issued ID, and other KYC-related information. At Phantom’s direction, this KYC data may be forwarded to their approved third-party partners. Phantom will only forward your data to these partners after obtaining your explicit consent, ensuring you are informed and agree to this onward sharing.
Data you provide to Link is governed by our Terms of Service and Privacy Policy, while any data shared onward at Phantom’s direction will be subject to their terms and privacy policy.
Currently, Link supports the Phantom crypto wallet.

Qualifications & exceptions

  • Phantom will only forward your data to these partners after obtaining your explicit consent, ensuring you are informed and agree to this onward sharing.

Sharing & Disclosure · Company practice

Stablecoin transfers may carry identity data for compliance

The publisher says FATF Travel Rule and applicable law may require originator/beneficiary identity data in transfer instructions shared with the counterparty VASP. Blockchain analytics used for fraud or sanctions compliance may process transaction data associated with a wallet address. This describes the notice’s stated legal condition without supplying or interpreting the external rule.

Supporting quotations

In connection with stablecoin transfers, Stripe may be required by the FATF Travel Rule and applicable law to include originator and beneficiary identity data in transfer instructions, which are shared with the counterparty virtual asset service provider (VASP). Where Stripe uses blockchain analytics tools to detect fraud and comply with sanctions obligations, those tools may process Transaction Data associated with your wallet address.

Qualifications & exceptions

  • Stripe may be required by the FATF Travel Rule and applicable law to include originator and beneficiary identity data in transfer instructions
Also annotated in the same passage (2)

Sharing & Disclosure · Company practice

Capital exchanges data with lenders, credit sources and relevant platforms

Business and Representative data may go to financial partners for requested eligibility, applications and completing/servicing transactions, including partners that buy repayment rights. Data may also be exchanged with service providers, credit agencies, banking partners and information bureaus. Connected Account information may be exchanged with its platform under their agreement.

Supporting quotations

Stripe may share your and your Representative’s Personal Data with its financial partners in order to determine your eligibility for financing you have requested, or to enable you to apply for financing or as necessary complete and/or service transactions with financial partners who in some cases may purchase the right to receive repayment on your financing.
Stripe may also share and obtain information about you, your business and your Representatives from Stripe’s service providers and other third parties, including credit reporting agencies, banking partners and information bureaus. If you’re a Connected Account, we may also share and receive information about you with your Platform, in accordance with your agreement with them.

Qualifications & exceptions

  • If you’re a Connected Account, we may also share and receive information about you with your Platform, in accordance with your agreement with them.

Sharing & Disclosure · Company practice

International processing extends to providers and payment partners’ countries

The notice permits transfers/processing wherever the publisher or its service providers operate, or where a chosen international payment method/financial partner operates, including the US. It describes safeguards for transfers out of UK/EEA/Switzerland and says this information is not legal advice; Business Users should consult counsel for their situations.

Supporting quotations

The detail below is provided for informational purposes. It is not intended to provide legal advice.
As a global business, Personal Data may be transferred to, and processed, in any country where we do business, where our service providers do business or if you use an international payment method or financial partner service, the countries in which that payment method or financial partner operates.
We may transfer your Personal Data to countries other than your own country, including to the United States.
Stripe continues to have appropriate safeguards and compliance measures to ensure an adequate level of protection of Personal Data transferred outside the UK, EEA and Switzerland.

Qualifications & exceptions

  • if you use an international payment method or financial partner service

Sharing & Disclosure · Company practice

Visitor advertising uses APIs and server-side pixels with an advertising-toggle opt-out

To show Stripe.com Visitors ads on other sites, the publisher shares/makes available identifiers, network activity, IP and device characteristics through advertising APIs/server-side pixels. It says potentially personally identifying details are SHA-256 hashed; hashing is not stated to erase the advertising relationship. Users can disable advertising in cookie settings at any time.

Supporting quotations

To enable Visitors of Stripe.com to see Stripe ads on other sites, we use advertising APIs and server-side pixels. The data that Stripe shares or makes available to enable this advertising include identifiers, internet or other similar network activity, IP addresses, and device characteristics. Any potentially personally identifying details are hashed through cryptographic SHA-256 hashing.
You can disable the toggle in the “advertising” section of our cookie settings page at any time.

Qualifications & exceptions

  • To enable Visitors of Stripe.com to see Stripe ads on other sites

Cross-references

Also annotated in the same passage (5)

Sharing & Disclosure · Company practice

Meta and LinkedIn may receive visitor and conversion information for advertising

The table lists sign-up/product interactions, website activity, IP, device/browser characteristics, visit times and hashed identifying details including email/name for Meta and LinkedIn. Meta’s API connects marketing data for targeting/performance/outcome measurement; LinkedIn’s connects online/offline data to measure website actions, phone sales and event leads. These are possible disclosures under the Visitor advertising feature, whose cookie-settings advertising toggle can be disabled.

Supporting quotations

Meta
Sign-up information and interactions with Stripe and our products, website activity, IP address, device and browser characteristics, timestamps of visits, cryptographically hashed (SHA-256) email, first name, last name.
The Meta Conversions API is a Meta business tool that creates a direct connection between your
marketing data and the Meta technologies that optimize ad performance. This helps you to
use your own marketing data to optimize ad targeting, decrease cost per action and see a
more complete picture of campaign outcomes while respecting people’s privacy.
Linkedin
Sign-up information and interactions with Stripe and our products, website activity, IP address, device and browser characteristics, timestamps of visits, cryptographically hashed (SHA-256) email, first name,) last name.
With the Linkedin Conversions API, you can connect both your online and offline data to LinkedIn so you can see how your campaigns influenced actions taken on your website, sales completed over the phone, or leads collected in-person at an event.
You can disable the toggle in the “advertising” section of our cookie settings page at any time.

Qualifications & exceptions

  • You can disable the toggle in the “advertising” section of our [cookie settings](https://stripe.com/cookie-settings) page at any time.
Also annotated in the same passage (5)

Sharing & Disclosure · Company practice

Reddit, X and Line may receive conversion data through server-to-server connections

Each listed recipient may receive sign-up/product interactions, website activity, IP, device/browser characteristics, visit times and hashed identifying details including email/name. Their APIs send conversion data directly for measurement, targeting and optimization; the descriptions say the connections resist signal loss. The publisher’s advertising toggle can be disabled, and the table does not state that these recipients receive payment-card data.

Supporting quotations

Reddit
Sign-up information and interactions with Stripe and our products, website activity, IP address, device and browser characteristics, timestamps of visits, cryptographically hashed (SHA-256) email, first name, last name.
The Reddit Conversions API is a server-to-server solution that shares your conversion data directly to Reddit’s platform without needing website code.
X
Sign-up information and interactions with Stripe and our products, website activity, IP address, device and browser characteristics, timestamps of visits, cryptographically hashed (SHA-256) email, first name, last name.
The X Conversions API is a server-to-server solution that shares your conversion data directly to X’s platform.
Line
Sign-up information and interactions with Stripe and our products, website activity, IP address, device and browser characteristics, timestamps of visits, cryptographically hashed (SHA-256) email, first name, last name.
Line Conversions API is a server-to-server solution that shares your conversion data directly to Line’s platform.
You can disable the toggle in the “advertising” section of our cookie settings page at any time.

Qualifications & exceptions

  • You can disable the toggle in the “advertising” section of our [cookie settings](https://stripe.com/cookie-settings) page at any time.
Also annotated in the same passage (5)

Sharing & Disclosure · Company practice

Google advertising tools may receive visitor activity and hashed email

The Google row lists possible sign-up/product interactions, site activity, IP, device/browser characteristics, visit times and SHA-256-hashed email disclosures. Its tag/API description covers personalized advertising and combining online conversion data with offline interactions for measurement, targeting and optimization. The publisher’s advertising toggle may be disabled; first/last name are not listed in this row.

Supporting quotations

Google
Sign-up information and interactions with Stripe and our products, website activity, IP address, device and browser characteristics, timestamps of visits, cryptographically hashed (SHA-256) email.
Combined with Google’s API solutions, advertisers can share conversion data to enhance on-site activity with offline customer interactions to improve measurement, targeting, and optimization.
You can disable the toggle in the “advertising” section of our cookie settings page at any time.

Qualifications & exceptions

  • You can disable the toggle in the “advertising” section of our [cookie settings](https://stripe.com/cookie-settings) page at any time.
Also annotated in the same passage (5)

Sharing & Disclosure · Company practice

OpenAI may receive conversion identifiers and events for ChatGPT ad measurement

The OpenAI row lists hashed email/browser ID, optional IP/user agent/country/city, event type/time and deduplication ID. Its server-to-server Conversions API measures ChatGPT advertising effectiveness and event matching against website actions. This is the saved publisher disclosure; it does not describe unrelated model training or chat-content sharing. The advertising toggle can be disabled.

Supporting quotations

OpenAI
Hashed email and browser ID; optional IP, user agent, country, city; event type/time; deduplication ID.
The OpenAI Conversions API is a server-to-server solution that shares conversion data directly with OpenAI to help measure the effectiveness of ads on ChatGPT. This integration improves conversion measurement and event matching, helping advertisers understand how their campaigns lead to actions on their websites.
You can disable the toggle in the “advertising” section of our cookie settings page at any time.

Qualifications & exceptions

  • optional IP, user agent, country, city
  • You can disable the toggle in the “advertising” section of our [cookie settings](https://stripe.com/cookie-settings) page at any time.
Also annotated in the same passage (5)

Sharing & Disclosure · Company practice

Some sites use Google reCAPTCHA under Google’s terms and policy

Some Stripe sites may use reCAPTCHA Enterprise against fraud/abuse. The notice says Google uses collected information to provide/improve reCAPTCHA Enterprise and for general security, subject to Google’s Privacy Policy and Terms. The linked documents are not supplied, so this card does not infer their wider permissions or retention.

Supporting quotations

some of the Stripe Sites may implement Google reCAPTCHA Enterprise to help prevent fraud and abuse. Information collected by Google is used to provide and improve reCAPTCHA Enterprise and for general security purposes. Use of reCAPTCHA Enterprise is subject to Google’s Privacy Policy and Terms of Use.

Qualifications & exceptions

  • some of the Stripe Sites may implement

Not stated here

  • The linked Google Privacy Policy and Terms of Use are not supplied; their further permissions and retention are not inferred.

Sharing & Disclosure · Company practice

hCAPTCHA may receive browser features and hashed identifiers as a service provider

When sites/services are protected by hCAPTCHA, the publisher may share browser features and certain hashed identifiers with Intuition Machines, Inc. to combat fraud/abuse, including bots. To the extent it is personal data, the provider processes it on the publisher’s behalf as processor/service provider.

Supporting quotations

When you access Stripe’s Sites and Services protected by hCAPTCHA, we may share data, including browser features and certain hashed identifiers with our hCAPTCHA provider Intuition Machines, Inc. To the extent that this data is Personal Data, Intuition Machines processes it on Stripe’s behalf as a Data Processor and/or a Service Provider.

Qualifications & exceptions

  • To the extent that this data is Personal Data

Sharing & Disclosure · Company practice

Additional affiliates and providers may process data in other locations

Depending on your location, customers’ locations and the services, the publisher may use additional affiliates, service providers and sub-processors locally or elsewhere. They act as processors for Stripe, LLC or STC depending on jurisdiction. The transfer explanation limits passing data to these parties to what is deemed strictly necessary for contractual obligations or processing, and says service-provider contracts limit processing to providing services to the publisher under its commitments and applicable law. The separate current provider list is linked, not supplied here.

Supporting quotations

Depending on your location, the location of your Customers, and the nature of the services Stripe is providing, (other than the entities set out above) we may use Stripe Affiliates in the same location or other locations, as well as Service Providers and Sub-processors to help provide the Services to you. These entities act as data processors on behalf of Stripe, LLC or STC depending on the jurisdiction.
Stripe will pass on Personal Data to affiliates and service providers or sub-processors, if deemed strictly necessary to carry out contractual obligations or for the data to be processed.
All of our service providers are subject to contract terms designed to ensure that these service providers process Personal Data only for the purposes of providing services to Stripe and in accordance with our commitments to Users and applicable data protection laws.

Qualifications & exceptions

  • if deemed strictly necessary to carry out contractual obligations or for the data to be processed.
  • only for the purposes of providing services to Stripe and in accordance with our commitments to Users and applicable data protection laws.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

Network analytics use aggregation or de-identification where appropriate

When giving Business Users network-level analytics or benchmarks, the publisher says it uses aggregated or de-identified information where appropriate so recipients cannot identify another Business User’s individual customers. This is a statement about information provided to recipients, not a claim that the underlying signals are always anonymous.

Supporting quotations

When Stripe provides Business Users with network-level analytics or benchmarks, Stripe uses aggregated or de-identified information where appropriate so that the recipient cannot identify another Business User’s individual customers from the information provided.

Qualifications & exceptions

  • where appropriate so that the recipient cannot identify another Business User’s individual customers from the information provided.

Sharing & Disclosure · Company practice

Third-party fraud databases may receive feedback from queried representative data

The publisher receives outside security/fraud information, such as compromised IP addresses. It may query third-party fraud and risk databases using Representatives’ onboarding personal data. Those providers may use the publisher’s experience with the queried data to inform their own risk and fraud signals.

Supporting quotations

Stripe also receives information from third parties to prevent and respond to security incidents, and for protecting against other fraudulent activity.
Stripe may use Representatives' Personal Data provided at onboarding to query third party databases regarding fraud and risk signals associated with that data. The third party providers operating these databases may use Stripe’s experience with the Personal Data queried to inform their fraud and risk signals.

Qualifications & exceptions

  • Representatives' Personal Data provided at onboarding

Sharing & Disclosure · Company practice

Card authentication may share identity, transaction and device details

When paying a Business User by debit or credit card, data may go to the card issuer, bank and payment-method provider to verify identity and authenticate the payment method. It can include name, email, phone, billing/shipping addresses, device ID and prior transaction history. Authentication during checkout can redirect you to a bank page asking for a code or password. Card issuers process received data as independent controllers under their own notices and applicable law.

Supporting quotations

To help prevent fraudulent transactions when you use your debit or credit card to pay a Business User, we may share data related to you and your transaction with your card issuer, bank, and payment method provider so that they can verify your identity and authenticate your payment method. The data we share to enable this process may include Personal Data such as your name, email address and phone number, and payment-specific data like your billing and shipping address.
Additionally, we may share contextual data, such as your device ID and previous transaction history. The process may take place as part of the checkout flow, which may involve you being redirected to another page where your bank asks you for a code or password to approve the purchase.
Card issuers act as independent data controllers for the information they receive and process that information in accordance with their own privacy notices and applicable law.

Qualifications & exceptions

  • so that they can verify your identity and authenticate your payment method.
  • Card issuers act as independent data controllers for the information they receive and process that information in accordance with their own privacy notices and applicable law.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

Issuers may receive fraud assessments during authorization

To help card issuers approve genuine transactions and reduce unnecessary failures, the publisher may share fraud-risk signals during authorization. Depending on the transaction, those can include its risk assessment and IP, email, phone and shipping-address data. Issuers act as independent controllers under their own notices and applicable law.

Supporting quotations

During payment authorization, Stripe may also share fraud-risk signals with your card-issuing bank to help the issuer approve genuine transactions and reduce unnecessary payment failures. Depending on the transaction, these signals may include Stripe’s fraud-risk assessment and information such as your IP address, email address, phone number, and shipping address.
Card issuers act as independent data controllers for the information they receive and process that information in accordance with their own privacy notices and applicable law.

Qualifications & exceptions

  • Depending on the transaction
  • Card issuers act as independent data controllers for the information they receive and process that information in accordance with their own privacy notices and applicable law.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

Disputes may send identifying and transaction evidence to payment networks

On a dispute or chargeback, the publisher may submit evidence to a network or payment-method provider on the Business User’s behalf for responding to and evaluating the claim. Examples include name, email, IP and other contacts, payment/account activity and billing, shipping, delivery or confirmation records; these are not an exhaustive list. Required information depends on dispute type and network/payment rules. Recipients generally act as independent controllers, and the publisher may be unable to alter or delete evidence already sent where law or network rules require retention.

Supporting quotations

When a payment dispute or chargeback is filed, Stripe may submit information to the relevant card network or other payment-method provider on behalf of the Business User involved in the transaction. This allows the Business User to respond to the dispute and allows the card network, card issuer, or payment-method provider to evaluate the claim.
The evidence submitted may include:
your name, email address, IP address, and other contact information;
payment and account activity;
billing, shipping, delivery, or transaction-confirmation records;
The information required depends on the nature of the dispute and the rules of the applicable card network or payment method.
Card networks and other payment-method providers generally act as independent data controllers for the evidence they receive.
Stripe may not be able to alter or delete information that has already been provided to a card network or issuer where retention is required under applicable law or network rules.

Qualifications & exceptions

  • When a payment dispute or chargeback is filed
  • The information required depends on the nature of the dispute and the rules of the applicable card network or payment method.
  • where retention is required under applicable law or network rules.
Also annotated in the same passage (2)

Sharing & Disclosure · Company practice

Dispute evidence can include communications and information supplied by either side

The dispute-evidence list includes billing, shipping, delivery or confirmation records; transaction-related communications or support requests; information submitted by the Business User; and other information you gave the publisher or Business User in connection with the transaction or dispute. What is required depends on the dispute and applicable network or payment-method rules.

Supporting quotations

billing, shipping, delivery, or transaction-confirmation records;
communications or support requests relating to the transaction;
information submitted by the Business User; and
other information that you provided to Stripe or the Business User in
connection with the transaction or dispute.
The information required depends on the nature of the dispute and the rules of the applicable card network or payment method.

Qualifications & exceptions

  • The information required depends on the nature of the dispute and the rules of the applicable card network or payment method.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

Business partners may receive onboarding and payment-instrument data when needed for services

When necessary to provide services to Business Users, onboarding and payment-instrument information may go to business partners, for example for payment processing or settlement. Recipients include banks, payment providers, BNPL providers, wallets and processors and their affiliates. Named examples are American Express Payment Services Limited and American Express Payments Europe S.L.; Banking Circle; Barclays; Citibank Europe; Credit Mutuel Arkea and Arkea Banking Services; Currence iDEAL; Klarna; Affirm; Mastercard Europe; Polski Standard Płatności; Swisscard; Visa Europe; and TrueLayer. The list is not exhaustive, and data shared depends on enabled payment methods.

Supporting quotations

In addition to Stripe’s Sub-processors, we may also share Business Users’ onboarding data and payment instrument information with third party business partners when this is necessary to provide our Services to our Business Users.
Third parties to whom we may disclose Personal Data for this purpose are banks, payment method (service) providers, BNPL providers, digital wallets and payment processors, including, but not limited to, the following entities and their affiliates:
American Express Payment Services Limited and American Express Payments Europe S.L.
Banking Circle S.A.
Barclays Bank PLC
Citibank Europe plc
Credit Mutuel Arkea and Arkea Banking Services
Currence iDEAL B.V.
Klarna AB
Affirm, Inc.
Mastercard Europe S.A.
Polski Standard Płatności
Swisscard AECS GmbH
Visa Europe Limited
TrueLayer Ltd.
The data shared with payment method providers will depend on the payment method(s) enabled on the Business User’s account.

Qualifications & exceptions

  • The data shared with payment method providers will depend on the payment method(s) enabled on the Business User’s account.

Sharing & Disclosure · Company practice

Data may be shared to protect services, rights, privacy, safety and property

The publisher shares personal data as it believes necessary for purposes including protecting its services and its or others’ rights, privacy, safety and property. One example is receiving or disclosing compromised IP-address information to protect services.

Supporting quotations

In addition, Stripe shares Personal Data as we believe necessary to, among other things, protect Stripe’s Services, rights, privacy, safety and property of Stripe, our users or others. For example, to protect our Services, Stripe may receive or disclose information about IP addresses that malicious actors have compromised.

Qualifications & exceptions

  • as we believe necessary

Sharing & Disclosure · Company commitment

Transfers to providers have necessity and contractual purpose limits

The transfer passage says personal data goes to affiliates, providers or sub-processors if deemed strictly necessary for contractual obligations or processing. Enabled payment methods may cause transfer to their jurisdictions. Before engaging third parties, the publisher performs due diligence including security assessment. Provider contracts are designed to restrict processing to providing services consistently with commitments and law; a security program includes third-party risk, and staff, agents and contractors acknowledge their responsibilities.

Supporting quotations

Stripe will pass on Personal Data to affiliates and service providers or sub-processors, if deemed strictly necessary to carry out contractual obligations or for the data to be processed. Depending on the enabled payment method(s), data may be transferred to the jurisdiction(s) of the respective payment method(s). Before we engage any third party, we perform due diligence, including a vendor security assessment.
All of our service providers are subject to contract terms designed to ensure that these service providers process Personal Data only for the purposes of providing services to Stripe and in accordance with our commitments to Users and applicable data protection laws.
Moreover, Stripe maintains and enforces a security program that addresses the management of security and the security controls employed by Stripe, which includes third party risk management. In addition, Stripe employees, agents, and contractors acknowledge their data security and privacy responsibilities under Stripe’s policies.

Qualifications & exceptions

  • if deemed strictly necessary to carry out contractual obligations or for the data to be processed.
  • only for the purposes of providing services to Stripe and in accordance with our commitments to Users and applicable data protection laws.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

Payment-method providers may receive business and representative details

When a method is enabled or transactions use it, the provider may receive Business User and Representative data for KYC/AML and other compliance, fraud prevention, transactions, services and platform support. Examples are business name/type, merchant codes/ID, transaction history, bank information, product type/tax amount, and Representative names, addresses, contact details, birth dates and tax or government IDs. Data comes from the merchant or is derived from merchant-supplied data. Some methods are enabled by default; the dashboard permits enabling or disabling them.

Supporting quotations

Stripe may share information regarding a Business User and the Business User’s Representative with a payment method provider when a payment method is enabled and when Stripe processes transactions involving the payment method.
The payment method provider may require Business Users’ and their Representatives' Personal Data for a number of purposes, including complying with know your customer (KYC), anti-money laundering, and other legal and compliance requirements, preventing fraud, facilitating transactions, providing Services to Business Users, and servicing the payment method’s platform.
For these purposes, Stripe may provide payment method providers with Business User data, including but not limited to business name, business type, merchant category codes, merchant ID, transaction history, bank account information, and other transaction specific information such as product type and tax amount that Stripe ascertains from that data. Stripe may also provide payment methods with Business Users’ Representatives’ Personal Data, including name, address, contact information, date of birth, tax identification number, and other government issued ID information. The information Stripe shares with payment method providers is data that Stripe has collected from the merchant or ascertained from data provided by the merchant.
Certain payment methods are enabled by default when you onboard with Stripe.
Your Stripe dashboard allows you to enable or disable payment methods at any time.

Qualifications & exceptions

  • when a payment method is enabled and when Stripe processes transactions involving the payment method.
  • Your Stripe dashboard allows you to enable or disable payment methods at any time.
Also annotated in the same passage (1)

Sharing & Disclosure · User right or choice

Business profiles are optional and can expose contact details

A Representative may create a profile to make the business discoverable to other businesses on the platform. Profiles can include display name, username, logo, website, description and contacts, with suggestions from onboarding or account data. The Representative or Business User controls activation and can review, edit, delete or disable it in the dashboard. Enabled information may be visible to other Business Users or intended recipients.

Supporting quotations

Stripe may also allow a Representative to create a Stripe Profile that makes their business discoverable to other businesses on Stripe. A Stripe Profile may include a business display name, username, logo, website address, business description, and contact details. Stripe may suggest profile information based on information previously provided during onboarding or otherwise associated with the business’s Stripe account.
The Representative or Business User controls whether to enable the profile and may review, edit, delete, or disable the profile through the Stripe Dashboard. Information included in an enabled profile may be visible to other Stripe Business Users or other intended recipients of the profile.

Qualifications & exceptions

  • The Representative or Business User controls whether to enable the profile and may review, edit, delete, or disable the profile through the Stripe Dashboard.

Sharing & Disclosure · Company practice

Merchants may receive and export Radar fraud information where law permits

The publisher may share and allow lawful export of fraud-relevant information: fraudulent-chargeback likelihood scores, transaction risk insights, the End Customer’s related payments to that Business User, other data about that transaction such as cardholder/card and amount/date, device/browser information for that transaction, and aggregated benchmarks. The related-payment and transaction examples are scoped to the recipient Business User, not all merchants’ raw customer records.

Supporting quotations

Stripe may share with the Business User and allow them to export (where allowed by Law) certain information relevant to fraud detection, including:
a transaction score that assesses the likelihood of the transaction becoming a fraudulent charge-back,
risk insights
related payments made by the End-Customer to the Business User,
other Transaction Data related to that End-Customer’s transaction with that Business User (e.g., cardholder name, card information, and the payment amount and date),
device and browser information for the device used to make the transaction with that Business User, and
aggregated benchmarks

Qualifications & exceptions

  • (where allowed by Law)

Not stated here

  • The linked Radar documentation is not supplied here; detailed risk-insight, review and benchmark specifications remain unknown.

Sharing & Disclosure · Company practice

Third-party-sourced personal data may be shared with Salesloft

For people notified of third-party data collection, the section names Salesloft, Inc. as an additional processor recipient beyond those in the linked Privacy Policy. It does not provide that policy’s full recipient list.

Supporting quotations

In addition to the recipients mentioned in the Stripe Privacy Policy, Personal Data may be shared with Salesloft, Inc. as a processor of Stripe;

Qualifications & exceptions

  • as a processor of Stripe;

Not stated here

  • The linked Privacy Policy recipient list is not supplied here.

Sharing & Disclosure · Company practice

CCPA identifiers may support verification, security, services and advertising

The twelve-month CCPA table lists identifiers such as device IDs for identity checks, fraud/security, providing/advertising services and legal compliance. Possible lawful recipients include providers and financial partners, advertising partners, your merchant, business-transfer/merger participants, law enforcement, courts, government and regulators.

Supporting quotations

Identifiers (e.g., a device identifier)
Identity verification, fraud prevention and security, to provide and advertise our Services, and to comply with law.
We may disclose the data, pursuant to applicable law, to: service enablers (including service providers, Financial Partners servicing the financial product), third parties like ad partners that help us advertise our products and Services, the merchant that you do business with (a.k.a. our Business User), an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.

Qualifications & exceptions

  • pursuant to applicable law
  • within the preceding 12 months.

Sharing & Disclosure · Company practice

CCPA protected-class characteristics are listed for verification and service purposes

The twelve-month CCPA table includes protected-class characteristics, such as gender/age in identity documents submitted for merchant verification. Listed purposes are identity verification, fraud/security, services and legal compliance. Possible lawful recipients are providers and financial partners, your merchant, transfer/merger entities and public authorities/courts/regulators. This row does not list ad partners; that local omission is not a document-wide prohibition.

Supporting quotations

Characteristics of protected classifications under California or federal law (e.g., gender and age noted in ID documents that you submit so that Stripe can verify your identity on behalf of your merchant - a.k.a. our Business User)
Identity verification, fraud prevention and security, to provide our Services, and to comply with law.
We may disclose the data, pursuant to applicable law, to: service enablers (including service providers and Financial Partners servicing the financial product), the merchant that you do business with (a.k.a. our Business User), an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.

Qualifications & exceptions

  • pursuant to applicable law
  • within the preceding 12 months.

Sharing & Disclosure · Company practice

CCPA commercial information is used for services, compliance and permitted purposes

The twelve-month CCPA commercial-information row includes transaction data your merchant may receive. Purposes include fraud/security, services, law compliance, enforcing terms and other purposes consistent with consent and law. Possible lawful recipients include providers/financial partners, your merchant, transfer/merger participants and public authorities/courts/regulators.

Supporting quotations

Commercial information (e.g., the merchant that you choose to do business with - a.k.a. our Business User may receive your Transaction Data)
Fraud prevention and security, to provide our Services, to comply with law, enforce our terms of services, and for other purposes consistent with your consent and applicable law.
We may disclose the data, pursuant to applicable law, to: service enablers (including service providers and Financial Partners servicing the financial product), the merchant that you do business with (a.k.a. our Business User), an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.

Qualifications & exceptions

  • for other purposes consistent with your consent and applicable law.
  • pursuant to applicable law
  • within the preceding 12 months.

Sharing & Disclosure · Company practice

CCPA biometric information has specific purposes and recipient categories

For the twelve-month table, biometric identifiers from photo IDs support identity checks, fraud/security and other purposes consistent with consent and law, such as verification-system improvement. The biometric row lists possible lawful disclosures to AWS as service provider, transfer/merger entities and law enforcement, courts, governments and regulators. It does not say every category in other rows also receives biometrics.

Supporting quotations

Biometric information (e.g., biometric identifiers from photo IDs used to confirm your identity)
Identity verification, fraud prevention and security, and for other purposes consistent with your consent and applicable law, such as to improve our verification systems.
We may disclose the data, pursuant to applicable law, to: a service provider - i.e., Amazon Web Services ("AWS"), an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.

Qualifications & exceptions

  • for other purposes consistent with your consent and applicable law
  • pursuant to applicable law
  • within the preceding 12 months.

Sharing & Disclosure · Company practice

CCPA online activity includes device and browser information across some merchant sites

The twelve-month table covers device/browser data across certain Business User sites, associated IPs and usage data. Listed uses are fraud/security, law compliance and providing/advertising services. Possible lawful recipients include providers/financial partners, ad partners, your merchant, transfer/merger entities and public authorities/courts/regulators.

Supporting quotations

Online activity information (e.g., information about devices and browsers across certain Business User sites that use Stripe and IP addresses associated with those devices and browsers, and usage data)
Fraud detection and security, to comply with law, and to provide and advertise our Services.
We may disclose the data, pursuant to applicable law, to: service enablers (including service providers, Financial Partners servicing the financial product), third parties like ad partners that help us advertise our products and Services, the merchant that you do business with (a.k.a. our Business User), an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.

Qualifications & exceptions

  • across certain Business User sites that use Stripe
  • pursuant to applicable law
  • within the preceding 12 months.

Sharing & Disclosure · Company practice

CCPA location information may be used for security, services and advertising

In the twelve-month CCPA table, location data supports fraud/security, legal compliance and providing/advertising services. Possible lawful recipients include providers/financial partners, ad partners, your merchant, transfer/merger entities and public authorities/courts/regulators. This category label does not establish GPS collection; the separate location explanation says the publisher does not collect device/browser GPS data.

Supporting quotations

Location Data
Fraud detection and security, in furtherance of compliance with legal obligations, and to provide and advertise our Services.
We may disclose the data, pursuant to applicable law, to: service enablers (including service providers, Financial Partners servicing the financial product), third parties like ad partners that help us advertise our products and Services, the merchant that you do business with (a.k.a. our Business User), an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.
Stripe does not collect GPS data from devices and browsers.

Qualifications & exceptions

  • pursuant to applicable law
  • within the preceding 12 months.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

CCPA audiovisual data is listed for verification, security and services

The twelve-month CCPA table includes visual/audio information, such as identity-verification photos. Uses are identity checks, fraud/security, services and legal obligations. Possible lawful recipients are providers, your merchant, transfer/merger entities and law enforcement, courts, governments and regulators.

Supporting quotations

Audiovisual (e.g., visual, audio, or similar information, like photos you submit so that Stripe can verify your identity on behalf of your merchant – a.k.a. our Business User)
Identity verification, fraud prevention and security, to provide our Services, and to comply with legal obligations.
We may disclose the data, pursuant to applicable law, to: service providers, the merchant that you do business with (a.k.a. our Business User), an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.

Qualifications & exceptions

  • pursuant to applicable law
  • within the preceding 12 months.

Sharing & Disclosure · Company practice

CCPA professional information is listed for recruiting and employment

The twelve-month CCPA row lists professional or employment-related data for recruiting, employment and legal compliance. Possible lawful recipients include providers, transfer/merger entities, law enforcement, courts, governments and regulators.

Supporting quotations

Professional or Employment-Related Information
Recruiting and employment, and to comply with legal obligations.
We may disclose the data, pursuant to applicable law, to: service providers, an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.

Qualifications & exceptions

  • pursuant to applicable law
  • within the preceding 12 months.

Sharing & Disclosure · Company practice

California statutory personal-information examples include contact and card details

The twelve-month table also lists California Civil Code 1798.80(e) categories, with examples of name, address, phone and credit/debit-card numbers. Purposes include identity checks, fraud/security, providing/advertising services and legal obligations. Possible lawful recipients are providers/financial partners, your merchant, transfer/merger entities and public authorities/courts/regulators. The statute itself is not supplied or interpreted here.

Supporting quotations

Categories of personal information described in Cal. Civ. Code 1798.80(e)(such as name, address, telephone number, credit card or debit card number)
See above. Identity verification, fraud prevention and security, to provide and advertise our Services, and to comply with legal obligations.
We may disclose the data, pursuant to applicable law, to: service enablers (including service providers and Financial Partners servicing the financial product), the merchant that you do business with (a.k.a. our Business User), an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.

Qualifications & exceptions

  • pursuant to applicable law
  • within the preceding 12 months.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

The California statutory-data row lists service and legal disclosures

For the preceding-twelve-month CCPA table’s statutory category, examples include names, addresses, phone and card numbers. Uses include identity verification, fraud/security, providing/advertising services and legal compliance. Possible lawful recipients are providers/financial partners, your merchant, transfer/merger entities and public authorities/courts/regulators.

Supporting quotations

Categories of personal information described in Cal. Civ. Code 1798.80(e)(such as name, address, telephone number, credit card or debit card number)
See above. Identity verification, fraud prevention and security, to provide and advertise our Services, and to comply with legal obligations.
We may disclose the data, pursuant to applicable law, to: service enablers (including service providers and Financial Partners servicing the financial product), the merchant that you do business with (a.k.a. our Business User), an entity engaged in a business transfer/merger, law enforcement, courts, governments and regulatory agencies.

Qualifications & exceptions

  • pursuant to applicable law
  • within the preceding 12 months.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

Advertising disclosures can count as legal sales or sharing without payment

The publisher says it does not sell personal data for payment, but may give it to advertising partners, analytics providers and social networks assisting its advertising. Because recipients may use it for their own purposes, this may be a “sale” or “sharing” under CCPA and other applicable US privacy laws. To its knowledge, it does not sell information of minors under 16. The payment statement therefore is not a blanket promise of no legally defined sales.

Supporting quotations

We do not sell your Personal Data to third parties in exchange for payment. However, as noted above, we may provide your Personal Data to third party partners, such as advertising partners, analytics providers, and social networks, who assist us in advertising our products and Services to you. Because these third parties may use the data Stripe provides for their own purposes (such as to improve their ad delivery), Stripe's provision of data to these parties may be considered a data “sale” or “sharing” as those terms are defined under the CCPA and other applicable US privacy laws. To our knowledge, Stripe does not sell personal information of minors under 16 years of age.

Qualifications & exceptions

  • To our knowledge, Stripe does not sell personal information of minors under 16 years of age.

Cross-references

Sharing & Disclosure · User right or choice

Identifiers, online activity and location were sold or shared for advertising, with an opt-out

The page reports that in the past twelve months identifiers, online activity across certain Business User sites, device/browser/IP and usage information, and geolocation such as IP addresses were “sold” or “shared” in the CCPA sense with third parties assisting service advertising. It offers an opt-out of targeted advertising and related sales/sharing through the linked cookie settings.

Supporting quotations

Within the past 12 months, the following categories of Personal Information described in section 1798.80(e) of the California Civil Code have been “sold” or “shared” (as defined under the CCPA) to third parties (including advertising partners) who assist us in advertising our Services:
Identifiers (e.g., a device identifier)
Online activity information (e.g., information about devices and browsers across certain Business User sites that use Stripe and IP addresses associated with those devices and browsers, and usage data)
Geolocation Data (e.g., IP addresses)
You can opt out of targeted advertising and any related data “sales” or “sharing”

Qualifications & exceptions

  • Within the past 12 months
  • (as defined under the CCPA)
  • You can opt out of targeted advertising and any related data “sales” or “sharing”

Sharing & Disclosure · Company practice

BNPL pre-qualification and selected applications have different bases

The table says limited data may go to participating BNPL providers to decide whether to display a pre-qualified offer, and, after selection, to enable an application and transaction. Examples include name, email, proposed amount and checkout data, with additional required application/transaction information after selection. Bases are legitimate interests in relevant payment options where permitted, consent where required for pre-qualification/disclosure, and contractual necessity when the service is selected. The source’s duplicated wording does not establish a guaranteed offer or approval.

Supporting quotations

We may also share limited Personal Data with participating buy now, pay later (“BNPL”) providers to determine whether to display a pre-qualified offer and, if you select a provider, to enable your application and transaction.
For BNPL, this may include your name, email address, proposed transaction amount and checkout information and, if you select the provider, information required for your application and transaction.
For BNPL processing, we rely on our legitimate interests in displaying relevant payment options where permitted, consent where required for pre-qualification or disclosure, and contractual necessity when you select the BNPL Service.

Qualifications & exceptions

  • where permitted, consent where required for pre-qualification or disclosure, and contractual necessity when you select the BNPL Service.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

Connect data exchanges support payments, platform ledgers and risk checks

Usual data includes first/last name, address, ID number, email, IP, phone and other payment-processing data. Platforms or Business Users transmit it for payments, ledger management and fraud prevention. Exchanged data may go to verification agencies, and Business User data may go to platforms for ledger management and the publisher’s identity/risk checks. Affiliates/providers/sub-processors may receive data deemed necessary for contractual obligations or processing. Full details are referred to the separate Privacy Policy.

Supporting quotations

The Personal Data transmitted to Stripe usually involves first name, last name, address, identification number, e-mail address, IP address, telephone number, and other data necessary for payment processing.
The transmission of the data is aimed at payment processing, ledger management, and fraud prevention. The Business User / Platform will transfer Personal Data to Stripe. The Personal Data exchanged between Stripe and the Business User / Platform may be transmitted to verification agencies, and Business User data may be shared with Platforms. This transmission is intended for the Platform to manage its ledger and for Stripe to conduct identity and risk checks.
Stripe will pass on Personal Data to affiliates and service providers or sub-processors, if deemed necessary to carry out contractual obligations or for the data to be processed.
For full details please see the applicable Privacy Policy of Stripe.

Qualifications & exceptions

  • if deemed necessary to carry out contractual obligations or for the data to be processed.

Not stated here

  • The linked Privacy Policy is not supplied; its full Connect terms and safeguards are not described.

Sharing & Disclosure · Company practice

Updated business details may appear on customers’ bank statements

Updated business address, phone or email fields may appear in a statement descriptor. The card network or cardholder’s bank ultimately determines what appears. Custom account users should correct inaccurate information through the platform receiving their charges.

Supporting quotations

If Stripe updates your account’s business address, phone number, or email address, these fields may be displayed on the statement descriptor within the cardholder’s bank statement. However, the exact information displayed is ultimately up to the card network or the cardholder’s bank. If any information is incorrect, please reach out to the platform through which you receive charges to ensure you have provided them with the most accurate information about you and your business.

Qualifications & exceptions

  • the exact information displayed is ultimately up to the card network or the cardholder’s bank.

Sharing & Disclosure · Company practice

Permission can let a merchant receive abandoned-checkout contact and cart data

If a prospective customer indicates permission through the checkout opt-in/opt-out checkbox, the merchant receives the supplied email and cart items, if any, for cart reminders, news and personalized offers. Offers may use cart items or sometimes prior purchases. Opting out of personalized offers does not prevent necessary purchase, delivery, billing or support contact.

Supporting quotations

If you, prospective End Customer, indicate permission to receive news and personalized offers by virtue of the opt-in/opt-out checkbox on your Business User’s checkout form, the following Personal Data is provided to your Business User so that your Business User can contact you to remind you of the items you left in the checkout or to provide you news and personalized offers:
Email (if provided by you).
Items in your cart with that merchant (if any).
Even if you opt-out of personalized offers by a Business User, if you do business with that Business User, they may still need to contact you in order to enable a purchase (e.g., for delivery or billing purposes) or in connection with customer support.

Qualifications & exceptions

  • Email (if provided by you).
  • Items in your cart with that merchant (if any).
  • Even if you opt-out of personalized offers by a Business User, if you do business with that Business User, they may still need to contact you in order to enable a purchase (e.g., for delivery or billing purposes) or in connection with customer support.
Also annotated in the same passage (1)

Sharing & Disclosure · Company practice

Completed checkouts share contact details and promotional preferences with that merchant

For a completed transaction the publisher shares contact information with the merchant, which uses it under its own privacy policy. With Promotional Emails it also shares checkbox preferences alongside contact, billing and transaction details.

Supporting quotations

Whenever you complete a transaction on a Business User’s website that uses Stripe services, as a service provider to that Business User, Stripe will share your contact information with that Business User.
Stripe will also share with your Business User your personalized offers and news preferences as determined by the opt-in/opt-out checkbox from your checkout form.

Qualifications & exceptions

  • as determined by the opt-in/opt-out checkbox from your checkout form.

Sharing & Disclosure · Restriction or exception

An abandoned checkout shares promotional data only with the checkbox enabled

For a prospective customer who starts but does not complete a purchase, no personal data is shared through this feature if none was entered or the news/offers checkbox is disabled on leaving. If enabled, the merchant receives the email supplied and cart items, if any. The prospective-customer definition additionally requires entering contact information without deleting it before session end.

Supporting quotations

the Personal Data that we share with your Business User depends on the following:
If you have not inputted any Personal Data into your Business User’s checkout form, then we will not share any Personal Data with that Business User.
If you have inputted Personal Data into your Business User’s checkout form:
If the checkbox for receiving news and personalized offers is not enabled when you leave your Business User’s checkout session, we will not share any of that Personal Data.
If the checkbox for receiving news and personalized offers is enabled when you leave your Business User’s checkout session, we will share the following information with that Business User:
Email (if provided by you).
Items in your cart with that merchant (if any).
To be a “prospective End Customer” for the promotional email feature, you also need to have started to input your contact information into the checkout form, and then not delete that information prior to the end of the session.

Qualifications & exceptions

  • If you have not inputted any Personal Data into your Business User’s checkout form, then we will not share any Personal Data with that Business User.
  • you also need to have started to input your contact information into the checkout form, and then not delete that information prior to the end of the session.
  • Email (if provided by you).
  • Items in your cart with that merchant (if any).
Also annotated in the same passage (1)

Sharing & Disclosure · Company commitment

Promotional Emails does not track across merchants or share checkout data with other merchants

The feature does not use cookies or cross-merchant tracking; checkout information transfers only to that merchant by API/webhook and is encrypted in transit using HTTPS/TLS. Purchase or attempted-purchase data from one merchant’s checkout is not shared with another merchant. These are feature-specific statements.

Supporting quotations

Stripe does not share Personal Data collected in connection with purchases (or attempted purchases) from one Business User’s checkout with another Business User.
The Promotional Email feature does not use cookies or track you across Business Users. Information collected from the Business User’s checkout page is transferred only to the Business User via API calls or webhooks.
Your information provided at checkout is encrypted in transit using HTTPS and TLS.

Qualifications & exceptions

  • Information collected from the Business User’s checkout page is transferred only to the Business User via API calls or webhooks.

Sharing & Disclosure · Company practice

Agentic-payment credentials and transaction data may reach transaction participants

The tokenized credential and relevant transaction data may be shared with the operator, merchant, payment networks, financial institutions and other parties authenticating, processing, settling, supporting or protecting the transaction. Uses include service delivery, fraud prevention, legal/network compliance, refunds and disputes. Operators and merchants may use received data under their own privacy policies, which users should review before authorization.

Supporting quotations

Stripe may share the tokenized payment credential and relevant Transaction Data with the agent operator, the Business User from which you are purchasing, payment networks, financial institutions, and other parties involved in authenticating, processing, settling, supporting, or protecting the transaction.
We use this information to provide the service, prevent fraud, comply with legal and payment-network requirements, and handle refunds, disputes, and other transaction-related requests.
Agent operators and Business Users may process Personal Data they receive in accordance with their own privacy policies.

Qualifications & exceptions

  • Agent operators and Business Users may process Personal Data they receive in accordance with their own privacy policies.

Sharing & Disclosure · Company practice

Sold through Link shares order data with the merchant for fulfillment and customer management

On completing an order, the publisher shares order information with the Business User for fulfillment and managing its relationship with you. This may include contact/payment information, tax ID, billing/shipping addresses and order details. The merchant may retain and use it under its own privacy policy; no merchant retention period is specified here.

Supporting quotations

When you complete a “Sold through Link” order, Stripe shares your order information with the Business User so they can fulfill your order and manage their relationship with you. This may include your contact information, payment information, tax identification number, billing and shipping address, and order details.
The Business User may retain this information and use it according to their own privacy policy.

Qualifications & exceptions

  • When you complete a “Sold through Link” order
  • The Business User may retain this information and use it according to their own privacy policy.

Sharing & Disclosure · Procedure

Capital applications require confirmation and disclose business details to the regional partner

Meeting criteria leads to an email/dashboard invitation for potential financing. The application is prefilled from the account and the Business User must confirm accuracy. Submission shares information with the regional partner, potentially company/display names, revenue, company number, business contacts/address/URL or product description, industry/MCC, applicable 25%-plus owners’ names/emails and names of directors/executives/senior managers with significant responsibility.

Supporting quotations

Where Stripe is satisfied that a Business User meets particular criteria established by Stripe and our financial partners (as applicable), we, or the Platform, will send the Business User an email and dashboard notification notifying them of their business’s eligibility for potential financing from a financial partner and invite them to apply.
When a Business User initiates the application process, Stripe pre-populates the application form with information from the Business User’s Stripe account and requires the Business User to confirm that it is correct. When you submit an application, your information will be shared with our financial partner in your region.
This information may include:
Company name
Business display name
Annual revenue
Company number
Company phone number and address
Business URL (or Product Description)
MCC (or Industry)
Business address
Business phone number
Business email
If applicable, the names and email addresses for any individuals who own 25% or more of the business
The names of each company director, executive or senior manager who has significant management responsibility for the business.

Qualifications & exceptions

  • If applicable, the names and email addresses for any individuals who own 25% or more of the business

Sharing & Disclosure · Company practice

Frontier data may be transferred internationally and disclosed on lawful official requests

Data may be stored/processed wherever the publisher operates, including the US, under potentially different protection rules. The publisher says it takes measures to comply with transfer laws; certain lawful requests from officials may require disclosure. This is not a promise of domestic-only processing or identical foreign protections.

Supporting quotations

We may transfer your Personal Data to countries other than your own country, including to the United States. These countries may have data protection rules that are different from your country. When transferring data across borders, we take measures to comply with applicable data protection laws related to such transfer. In certain situations, we may be required to disclose Personal Data in response to lawful requests from Officials (such as law enforcement or security authorities).

Qualifications & exceptions

  • In certain situations, we may be required to disclose Personal Data in response to lawful requests from Officials (such as law enforcement or security authorities).

Sharing & Disclosure · Company practice

Canadian and Quebec data may be processed abroad under local access laws

Information about people in Canada, including Quebec, may be transferred outside Quebec, particularly to the US. Processing outside Canada may be subject to the destination’s laws, including lawful access requirements.

Supporting quotations

When Stripe collects Personal Data relating to individuals in Canada, including Quebec, that information may be transferred to and processed outside of Quebec, in particular in the United States. Personal Data processed outside Canada may be subject to the laws of the jurisdiction in which it is processed, including lawful access requirements applicable in that jurisdiction.

Sharing & Disclosure · Company practice

Law-enforcement requests are reviewed with a minimum-disclosure goal

The publisher reviews each request with the goal of providing the minimum required information in response to legitimate legally mandated requests. It offers a contact route for questions; this is a stated review/minimization goal, not a promise never to disclose data.

Supporting quotations

We get requests for access to data from law enforcement, and we review each request with the goal of responding with the minimum amount of required information in response to legitimate, legally mandated requests.
If you have any questions, please contact us.

Qualifications & exceptions

  • with the goal of responding with the minimum amount of required information in response to legitimate, legally mandated requests.

Not stated here

  • The alternate linked contact page is not independently supplied; no extra terms beyond this saved document’s Contact Us section are inferred.