Stripe Privacy Center (supplemental privacy notices)

Pika · Official agreement

Read the agreement

266 of 266 cards

Use & Processing · Context

Singapore’s DPA entity is SPEL; other activities list STC

In the Singapore group, the DPA contracting entity is SPEL in Ireland. All other activities list STC in Ireland. The services-entry continuation also places STC in Ireland; the separate local services entity remains as listed in the preceding row. The linked DPA is not supplied here.

Supporting quotations

Ireland
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland
STC
Provision of services and regulated activities in accordance with
Also annotated in the same passage (1)

Use & Processing · Context

Switzerland’s table names a UK regulated-services entity and Irish entities

For authorised payment services and other regulated activities in Switzerland, the table lists Stripe Payments UK, Ltd. in the UK. In the Switzerland group, SPEL in Ireland is the services-agreement and DPA contracting entity; STC in Ireland is listed for all other activities. The links point to UK agreements, whose terms are not supplied in this table.

Supporting quotations

Switzerland
Provision of authorised payment services and other regulated activities in Switzerland.
Stripe Payments UK, Ltd.
United Kingdom
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland

Use & Processing · Context

Thailand’s entity entries distinguish local services, the DPA and other activities

For services and regulated activities under the linked Thai agreement, the Thailand group lists Stripe Payments (Thailand) Ltd. in Thailand, followed by STC in Ireland. SPEL in Ireland is the DPA contracting entity; STC in Ireland is listed for all other activities. These entries do not supply the linked agreements.

Supporting quotations

Thailand
Provision of services and regulated activities in accordance with
Stripe Payments (Thailand) Ltd.
Thailand
STC
Ireland
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland

Retention & Deletion · User right or choice

Deleting a Link account cancels Sold through Link subscriptions

Request deletion through the linked Link support instructions to remove Sold through Link order information. Account deletion also cancels active subscriptions sold this way. Merchants may hold independent checkout copies under their own policies, so contact them separately for deletion. This does not promise to delete independent merchant records or permanent blockchain entries.

Supporting quotations

You can request that your information be deleted from Link in connection with your “Sold through Link” orders by requesting the deletion of your Link account.
Deleting your Link account will also result in:
any active subscriptions Sold through Link being canceled; and
all information provided for a Sold through Link order will be deleted.
Please note that the Business User may have stored the information provided during checkout (such as your contact and billing details) independently of Link in accordance with their own privacy policy. We recommend reaching out to them directly if you would like them to delete your information as well.

Qualifications & exceptions

  • The Business User may have stored the information provided during checkout (such as your contact and billing details) independently of Link in accordance with their own privacy policy.

Cross-references

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.

Retention & Deletion · Restriction or exception

Blockchain payment records remain public and cannot be deleted

Stablecoin/digital-asset payments leave permanent public blockchain records, potentially wallet addresses, amounts and timestamps. Identity is decoupled where possible, but the ledger record remains and wallet addresses may be linked to individuals through other information. This limits what deletion can achieve for on-chain records.

Supporting quotations

Payments in stablecoin or other digital assets are recorded on a public blockchain, which is permanent and cannot be altered or deleted.
Although wallet addresses typically do not directly display a person’s name, they may be linked to an individual through other information.

Cross-references

Also annotated in the same passage (2)

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)

Use & Processing · Company practice

Capital uses data for eligibility, financing agreements and models

In addition to the preceding legitimate-interest purposes, Capital assesses eligibility/offers and improves models to tailor financing and reduce risk. Processing also occurs where necessary for an existing financing agreement or an application and eligibility for an agreement with the publisher or financial partners.

Supporting quotations

Enhance our machine learning models to allow us to better tailor financing to, and decrease the risk to, you and other Business Users.
Assess your eligibility for, and offer you, Stripe Capital and Capital for Platforms Services.
We will also process your data where it is necessary for a financing agreement that you have entered into or because you have submitted an application to receive funding and to determine eligibility to enter into a financing agreement with us or with our financial partners.

Qualifications & exceptions

  • where it is necessary for a financing agreement that you have entered into or because you have submitted an application to receive funding
Also annotated in the same passage (1)

Account & Service Control · User right or choice

Capital marketing must meet consent requirements and offers can be stopped

The publisher or platform may email Capital offers in accordance with law, including applicable consent requirements. Business Users can use email unsubscribe links and dashboard notification settings. Connected Accounts using Capital for Platforms should contact the platform owner to opt out.

Supporting quotations

We, or the Platform, may send you email marketing communications about Stripe Capital offers, provided we, or the Platform, do so in accordance with applicable law, including any consent requirements.
Business Users have the option to unsubscribe or opt-out of receiving Capital offers via the link included in Stripe Capital emails. Business Users may also opt-out of dashboard notifications via the settings page of the Stripe Dashboard. If you’re a Connected Account using Capital for Platforms, please contact your platform owner to unsubscribe or opt-out of receiving Capital offers.

Qualifications & exceptions

  • provided we, or the Platform, do so in accordance with applicable law, including any consent requirements.

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.

Legal Rights & Agreement Rules · Context

Capital’s controller depends on business location

For Capital data the responsible controller is Stripe, LLC for US businesses, and Stripe Payments Europe, Limited for businesses outside the US. This is the specific Capital rule rather than a universal entity assignment for all services.

Supporting quotations

The Stripe entity responsible for your data will depend on the location of your business.
If your business is based in the U.S., Stripe, LLC is the data controller responsible for Personal Data collected and processed in relation to the financing that business receives through Stripe Capital.
If your business is based anywhere outside of the U.S., Stripe Payments Europe, Limited, is the data controller responsible for Personal Data collected and processed in relation to Stripe Capital.

Data Access & Collection · Company practice

Non-Stripe transaction history may be imported or obtained with financial-account consent

Business Users can import external data in the dashboard to consolidate revenue. Separately, the publisher may obtain financial-account transactions with consent. The linked pages are referrals; they do not supply further collection or storage terms here.

Supporting quotations

Stripe enables the Business User to import non-Stripe data through the Stripe Dashboard to consolidate their revenue data in one place.
Separately, Stripe may also obtain your account transactions from your financial account with your consent.

Qualifications & exceptions

  • with your consent.

Legal Rights & Agreement Rules · Procedure

Bank-account refund privacy details are in separate help pages

End Customers asked for bank-account information for a merchant refund and Business Users processing refunds are directed to separate privacy guidance. This section does not itself specify retention, data recipients or the detailed refund procedure.

Supporting quotations

If you have been asked to provide your bank account and other information to process a refund on behalf of your merchant (i.e., our Business User), please visit the webpage here to learn more about our privacy practices for End Customer bank account refunds.
If you are a Business User that is using or intends to use Stripe to process refunds, please visit the webpage here for additional guidance on privacy considerations for your business.

Not stated here

  • Linked refund privacy pages are not supplied; their detailed terms are unknown.

Data Access & Collection · Company practice

Frontier collects supplied communications and engagement data

Frontier facilitates carbon-removal purchases through an advance market commitment. Its collection includes information voluntarily supplied through tickets, email, social media, surveys and calls, including email/name, calling number and chosen message contents. It also collects event registration, attendance/viewing and interactions with personnel. The separate Privacy Policy may add details not supplied here.

Supporting quotations

It facilitates purchases from high-potential carbon removal companies on behalf of buyers.
We will collect any information you choose to provide to us, for example, through support tickets, emails or social media.
We will also collect your engagement data such as your registration for, attendance of, or viewing of Stripe events and other interaction with Stripe personnel.

Not stated here

  • The linked Privacy Policy is not supplied; additional Frontier practices are not inferred.

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

Legal Rights & Agreement Rules · Company practice

The notice lists adequacy decisions and DPF certification as transfer mechanisms

Transfers may use countries/recipients deemed adequate by relevant authorities. The notice states Stripe, LLC is certified under EU-US DPF, the UK Extension and Swiss-US DPF for respective transfers to the US. When multiple mechanisms apply DPF takes precedence, with alternatives if DPF becomes unavailable. These are the saved notice’s claims, not a current independent certification check.

Supporting quotations

Transferring Personal Data from the originating to a country or recipient that has been deemed to have an adequate level of data protection by relevant privacy authorities, including the European Commission.
Stripe’s parent entity, Stripe, LLC is certified under the EU-U.S DPF, Swiss-U.S. DPF and the UK Extension. Stripe relies on the Data Privacy Framework to transfer personal data from respectively the EEA, the UK and Switzerland to the U.S.
In case the DPF is invalidated or Stripe is otherwise prevented from relying on the DPF, we incorporate multiple transfer mechanisms to ensure that data transfers can continue. If more than one data transfer mechanism applies, the DPF takes precedence.

Qualifications & exceptions

  • If more than one data transfer mechanism applies, the DPF takes precedence.
Also annotated in the same passage (2)

Legal Rights & Agreement Rules · Company practice

EU SCCs and the UK Addendum are incorporated transfer safeguards

The notice identifies European Commission SCCs as contractual mechanisms for EU personal-data transfers outside EEA/UK, and the ICO’s UK Addendum for UK transfers, incorporated into agreements. The repeated UK Addendum bullet does not create an additional distinct mechanism. No external clause text is supplied here.

Supporting quotations

The Standard Contractual Clauses (“SCCs”) approved by the European Commission.
These are required under EU data protection law (known as the GDPR) and are incorporated into our agreements.
The UK International Data Transfer Addendum (“UK Addendum”) issued by the UK’s Information Commissioner’s Office to provide a legal mechanism to transfer personal data from the UK. This mechanism is required under UK data protection law (known as UK GDPR) and is incorporated into our agreements.
The UK International Data Transfer Addendum (“UK Addendum”) issued by the UK’s Information Commissioner’s Office to provide a legal mechanism to transfer personal data from the UK.

Legal Rights & Agreement Rules · Company practice

Thailand, Brazil and UAE transfers use their stated regional safeguards

Thailand transfers use amended EU SCCs approved by the Thai regulator under the named Act. Brazil transfers may use Brazilian SCCs or other permitted mechanisms. UAE transfers may use recognized adequate jurisdictions, approved clauses or other safeguards under the named federal law; applicable financial-free-zone law determines required safeguards when such processing applies. Other authority-approved transfer mechanisms may also be used. The card preserves the notice’s legal references without deriving rules from external laws.

Supporting quotations

For transfers of Personal Data from Thailand, the amended EU SCCs as approved by the Thai privacy regulator for transfers of personal data outside of Thailand under the Thai Personal Data Protection Act B.E. 2562.
For transfers of Personal Data from Brazil, Stripe may use the Brazilian Standard Contractual Clauses and other transfer mechanisms permitted under applicable Brazilian data-protection law.
For transfers of Personal Data from the United Arab Emirates, Stripe may transfer Personal Data to jurisdictions recognized as providing an adequate level of protection or use approved standard contractual clauses or other appropriate safeguards, in accordance with the UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data.
Where processing is subject to the laws of a UAE financial free zone, Stripe will implement transfer safeguards required by the applicable free-zone law, such as the DIFC Data Protection Law or ADGM Data Protection Regulations.
Other alternative data transfer mechanisms approved by relevant privacy authorities to enable the transfer of Personal Data to a third country.

Qualifications & exceptions

  • Where processing is subject to the laws of a UAE financial free zone, Stripe will implement transfer safeguards required by the applicable free-zone law, such as the DIFC Data Protection Law or ADGM Data Protection Regulations.

Security & Safeguards · Company commitment

Supplementary transfer protections include security and asset-management programs

The publisher states a commitment to transparency and points to separate privacy/security resources. Its supplementary protection measures include enforced security and asset-management programs, risk assessment/monitoring/correction, and employee/agent/contractor acknowledgment of security/privacy responsibilities. These processes do not promise elimination of unauthorized-access risk.

Supporting quotations

we are committed to being transparent about our privacy processes and policies.
We also want to highlight some of our supplementary measures to protect our Business Users’ data from unauthorized access.
Stripe employs security controls and maintains and enforces a security program that addresses the management of security. We also perform risk assessments and implement and maintain controls for risk identification, analysis, monitoring, reporting, and corrective action.
Stripe maintains and enforces an asset management program that appropriately classifies and controls hardware and software assets throughout their life cycle. In addition, Stripe employees, agents, and contractors acknowledge their data security and privacy responsibilities under Stripe’s policies.
Also annotated in the same passage (1)

Legal Rights & Agreement Rules · Company practice

CBPR and PRP certification support transfers only where recognized by law

The notice describes CBPR for controllers and PRP for processors and states the publisher obtained both certifications. Transfers rely on them where applicable law recognizes them as valid mechanisms. It separately gives DPF priority if multiple mechanisms apply. This is a description of the saved notice, not independent verification of current certification.

Supporting quotations

CBPR is aimed at organizations handling personal data as a data controller
PRP, on the other hand, is tailored for data processors
Stripe’s privacy practices comply with CBPR and PRP systems as evidenced by the CBPR and PRP certifications Stripe has obtained.
Where CBPR and/or PRP are recognized as a valid transfer mechanism under applicable law, Stripe will transfer Personal Data in accordance with the CBPR and PRP certifications Stripe has obtained.
If more than one data transfer mechanism applies, the DPF takes precedence.

Qualifications & exceptions

  • If more than one data transfer mechanism applies, the DPF takes precedence.
Also annotated in the same passage (2)

Retention & Deletion · Company practice

Global authentication storage covers Representative security data, excluding End Customer transactions

Authentication/authorization/identity infrastructure spans multiple regions, specifically US and India, for speed and reliability. This storage strategy is strictly limited to authentication/security: Representative identifiers, login/MFA, devices/challenges, sessions, roles/permissions, team management/invitations and SSO configuration. It expressly excludes transactional information and other End Customer data; this does not negate other international-transfer provisions for different processing.

Supporting quotations

This infrastructure spans multiple geographic regions, specifically including our data centers located in the United States and India.
Our focus on global data storage centers around particular categories of Personal Data, strictly limited to aspects of user authentication and security.
The specific types of data stored globally include Representative identifying information such as name, location, email address, phone number, date of birth, IP address, and device ID.
Additionally, session management data, user roles and permissions, team invitations and management, and Single Sign-On (SSO) configurations fall under this umbrella of globally stored data.
this global storage strategy does not extend to any transactional information or other data related to End Customers.

Qualifications & exceptions

  • this global storage strategy does not extend to any transactional information or other data related to End Customers.

Legal Rights & Agreement Rules · User right or choice

The state table lists deletion, sale opt-out and non-discrimination for nineteen states

The saved table lists these rights for California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia. Availability remains subject to applicable state law and exceptions; the list is the notice’s mapping rather than a new legal determination.

Supporting quotations

Right to deletion
California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia
Right to opt-out from a sale of personal data
California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia
Right to non-discrimination for exercising your rights
California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia
Depending on your location and subject to applicable law, you may have the following rights:

Qualifications & exceptions

  • Depending on your location and subject to applicable law, you may have the following rights:
Also annotated in the same passage (5)

Legal Rights & Agreement Rules · User right or choice

Targeted-advertising and significant-effect profiling opt-outs have different state lists

The targeted-advertising row names Colorado, Connecticut, Delaware, Indiana, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia. The profiling row concerns certain decisions with legal or similarly significant effects and names the same states except Utah. These are conditional state-law rights in the saved table.

Supporting quotations

Right to opt-out of processing for targeted advertising
Colorado, Connecticut, Delaware, Indiana, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia
Right to opt-out from profiling for certain decisions with legal or similarly significant effects
Colorado, Connecticut, Delaware, Indiana, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Virginia
Depending on your location and subject to applicable law, you may have the following rights:

Qualifications & exceptions

  • Depending on your location and subject to applicable law, you may have the following rights:
Also annotated in the same passage (5)

Legal Rights & Agreement Rules · User right or choice

The state table maps appeals and recipient confirmation separately

The refusal-appeal row names Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Virginia. Recipient/category confirmation names Delaware, Maryland, Minnesota and Oregon. These rights remain subject to applicable law; absence from a row is not a general denial of every other available route.

Supporting quotations

Right to appeal the refusal of a request to exercise your rights
Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Virginia
Right to confirm the third parties or categories of third parties to which personal data has been disclosed
Delaware, Maryland, Minnesota, Oregon
Depending on your location and subject to applicable law, you may have the following rights:

Qualifications & exceptions

  • Depending on your location and subject to applicable law, you may have the following rights:
Also annotated in the same passage (5)

Legal Rights & Agreement Rules · User right or choice

The state table identifies California sensitive-data limits and cross-context sharing opt-out

California is listed for limiting sensitive personal-data use/disclosure and opting out of sharing for cross-context behavioral advertising. These are subject to applicable law and the processing at issue, rather than unconditional prohibitions on all sensitive-data use or sharing.

Supporting quotations

Right to limit the use and disclosure of sensitive personal data
California
Right to opt-out from sharing for cross-context behavioral advertising
California
Depending on your location and subject to applicable law, you may have the following rights:

Qualifications & exceptions

  • Depending on your location and subject to applicable law, you may have the following rights:
Also annotated in the same passage (5)

Account & Service Control · Procedure

Access requests use different routes for direct users and merchant customers

Subject to location/law, confirmation and a personal-data copy may be requested. Direct users, including merchants, Link users and Identity users verified solely for the publisher’s own purposes, can use privacy.stripe.com/access; Business Users/Representatives can also view dashboard information. End Customers should address transaction-data access to the merchant. Email/form alternatives exist, and identity/relationship verification may be needed.

Supporting quotations

Depending on your location and subject to applicable law, you may have the right to request confirmation of whether Stripe processes Personal Data relating to you, and if so, to request a copy of that Personal Data.
you can use our self‑service tool that allows direct users to access their personal data directly: https://privacy.stripe.com/access.
If you are a Business User or Representative, you may also login in to the Stripe Dashboard to view personal information shared with Stripe.
If you are the End Customer of a Business User that uses Stripe Services, the Business User would be the correct party to respond to a data subject access request related to your transactional information.
Please note that we may need to verify your identity and your relationship with us before we can proceed with your request.

Qualifications & exceptions

  • Please note that we may need to verify your identity and your relationship with us before we can proceed with your request.

Account & Service Control · User right or choice

Marketing opt-out routes differ for Business Users, Visitors and Link users

Business Users/Visitors can use the linked marketing preference page and ask privacy@stripe.com for help. Link users can unsubscribe in marketing emails or toggle marketing emails in Link account settings; the notice says the address will be opted out as soon as possible, without a fixed deadline.

Supporting quotations

If you are a Business User or Visitor, you may unsubscribe from Stripe marketing emails here.
If you are a Link user, you may opt-out from marketing-related emails by using the unsubscribe link in any marketing email you receive, or by managing your subscription preferences in the Link website.
Turn “Marketing emails - Receive updates and deals from Link and its partners” on or off. Your email address will be opted out of email marketing communications as soon as possible.

Qualifications & exceptions

  • as soon as possible.

Account & Service Control · User right or choice

UK privacy complaints go to the controller responsible for the processing

UK individuals may complain to a controller about perceived data-protection infringement. Direct users can contact the publisher by privacy email/form. For an End Customer complaint about processing where Stripe acts as processor, the merchant is the appropriate respondent under UK GDPR and the Data Protection Act 2018.

Supporting quotations

Individuals in the UK have a right to complain to a data controller if they consider that the data controller has infringed data protection laws.
you can exercise your right to complain to Stripe by contacting us by email, or through our form.
Please note that if you are the End Customer of a Business User that uses Stripe Services and your complaint relates to processing where Stripe acts as a data processor, the Business User would be the correct party to respond to a complaint under UK GDPR and Data Protection Act 2018.

Qualifications & exceptions

  • where Stripe acts as a data processor

Retention & Deletion · Restriction or exception

Legal retention and compelling fraud grounds can limit deletion or objection

The publisher may continue processing after a deletion request or objection when law requires retention, such as Business User KYC/AML records. It may also rely on compelling legitimate grounds for fraud/financial-crime prevention, and may be unable to delete/stop processing data necessary to the integrity of fraud-detection and financial models. These are stated grounds and necessity conditions, not unlimited retention of every record.

Supporting quotations

In certain circumstances, Stripe may be required by law to retain and process your Personal Data even after a deletion request or objection to the processing.
Stripe may also rely on compelling legitimate grounds to continue processing your Personal Data.
When Personal Data is necessary to enable or maintain the integrity of Stripe’s fraud detection and financial models, Stripe may not be able to honor requests to delete or stop processing that data.

Qualifications & exceptions

  • When Personal Data is necessary to enable or maintain the integrity of Stripe’s fraud detection and financial models

Cross-references

  • exception to (model-proposed): Privacy rights depend on location and applicable law — The general deletion/objection rights remain subject to legal retention and compelling legitimate grounds, including data necessary for fraud-model integrity; this is not a blanket refusal of all requests.

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)

Inference & Profiling · Company practice

Demandbase may infer a visitor’s company from IP and cookie information

The table lists IP, visit times, referrer, page URL, cookie ID, sign-up data and device/browser characteristics as data made available to Demandbase. Its description says the tag sends IP/cookie information to an identification API to determine the visitor’s company and measure interest. This is the service’s described inference, not a guarantee of correct employment identification. The advertising toggle can be disabled.

Supporting quotations

Demandbase
IP address, timestamps of visit, referrer, page URL, cookie ID, Sign-up information, device and browser characteristics
The Demandbase tag reads the IP address and cookie of each visitor and passes that information to our identification API, which determines which company the visitor works for.
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)

Account & Service Control · User right or choice

Detected GPC signals opt out of covered advertising sale or sharing for that browser and device

Enabling GPC automatically opts out of sharing when interacting with the site. The clarified scope is sale/sharing for cross-context behavioral advertising subject to applicable US privacy law. The preference applies to the transmitting browser/device, and clearing or expiry of cookies may require retransmitting the signal or resetting preferences.

Supporting quotations

If you have enabled GPC on your browser, you will automatically be opted out of any “sharing” when you interact with our site.
Stripe treats a detected GPC signal as a request to opt out of any “sale” or “sharing” for cross-context behavioral advertising that is subject to applicable U.S. privacy law. The preference applies to the browser and device transmitting the signal. If cookies are cleared or expire, you may need to transmit the signal again or reset your preference.

Qualifications & exceptions

  • The preference applies to the browser and device transmitting the signal.
  • If cookies are cleared or expire, you may need to transmit the signal again or reset your preference.

Cross-references

Data Access & Collection · Restriction or exception

Disabling cookies does not disable advanced fraud signals

Browsers may allow cookie deletion/disabling, which can impair site/service features. Advanced fraud-signal collection continues despite cookie disabling; the integrating Business User controls it and can consult the publisher’s linked disabling instructions. This is not an End Customer browser opt-out of all fraud collection.

Supporting quotations

If you choose to disable cookies, keep in mind that some features of our Site or Services may not operate as intended. Disabling cookies will not disable the collection of advanced fraud signals, which we use to prevent fraud on Stripe. The collection of this data is controlled by the Business User that integrated with Stripe.
You can learn more about how businesses can disable collection of advanced fraud signals in our documentation for disabling advanced fraud detection.

Qualifications & exceptions

  • The collection of this data is controlled by the Business User that integrated with Stripe.

Not stated here

  • The linked advanced-fraud disabling instructions are not supplied; implementation steps are not inferred.

Cross-references

Retention & Deletion · Restriction or exception

Closing a Stripe account deletes some information but can leave required transaction records

Accounts can be closed in dashboard Settings. Closure deletes some, not all, held information: anti-terrorism/AML and other regulations may require Business User transaction records for prescribed periods after the business relationship ends. No fixed universal period is stated in this passage.

Supporting quotations

You can close your Stripe account from the Settings page on the Dashboard.
Please be aware that we will delete some, but not all, of the information that we hold, for the reasons explained below.
These regulations and laws may require Stripe to retain transactional records associated with Business Users for a prescribed period of time after the close of the business relationship.

Qualifications & exceptions

  • for a prescribed period of time after the close of the business relationship.
Also annotated in the same passage (1)

Account & Service Control · Procedure

Custom and Express Connect deletion requests should go to the managing platform

Both account types are managed by a Platform/Business User, which is responsible for payments and responding to the query; the notice recommends contacting it for assistance. This route does not promise complete erasure: required transaction records may remain after the business relationship closes.

Supporting quotations

If you have a Custom Connect account, your account is managed by a Platform / Business User. They are the party responsible for managing payments for you and responding to your query; therefore we recommend reaching out to them for assistance.
If you have an Express Connect account, your account is managed by a Platform / Business User. They are the party responsible for managing payments for you and responding to your query; therefore we recommend reaching out to them for assistance.
These regulations and laws may require Stripe to retain transactional records associated with Business Users for a prescribed period of time after the close of the business relationship.

Qualifications & exceptions

  • for a prescribed period of time after the close of the business relationship.
Also annotated in the same passage (1)

Legal Rights & Agreement Rules · Context

Media Services has a separate privacy policy

The notice directs readers to the Media Privacy Policy for Stripe Press, Increment and Works in Progress data practices. It does not supply the separate policy’s collection, use or retention terms here.

Supporting quotations

The Privacy Policy for Stripe Media Services (Media Privacy Policy) describes how Stripe collects and processes Personal Data in order to provide the Stripe Media Services, including Stripe Press, Increment, and Works in Progress.

Not stated here

  • The linked Media Privacy Policy is not supplied; its substantive data practices are not inferred.

Retention & Deletion · Restriction or exception

Indian payment-system data is localized where required, while other permitted processing may occur abroad

Personal data may be processed in India or countries of operations/service providers to the extent Indian law permits. Where required by RBI localization requirements, payment-system data will be stored only on servers in India. This conditional rule does not say every category of Indian personal data always stays in India.

Supporting quotations

Personal Data may be processed either locally in India or in any other country where we have operations or where we engage service providers, to the extent permitted under applicable laws of India. Where required payment system data will be stored only on servers in India in accordance with the RBI data localization requirements.

Qualifications & exceptions

  • Where required payment system data will be stored only on servers in India in accordance with the RBI data localization requirements.

Account & Service Control · Procedure

India complaints can go to the named grievance officer and unresolved matters can be escalated

The saved notice names Yogender Singh as Nodal/Grievance Officer, complaints-in@stripe.com, and Prestige Tech Pacific Park, 10th Floor, Building 2, Kadubeesanahalli Village, Varthur Hobli, Bangalore East Taluk, Bangalore-560103 Karnataka, India. It refers to separate complaint guidance; if the publisher cannot address the grievance, the notice states a right to escalate to India’s Data Protection Board. Law-enforcement requests use LERequests@stripe.com separately.

Supporting quotations

If you have any questions or complaints regarding the treatment of your Personal Data in India, you may contact our Nodal Officer and Grievance Officer:
Name - Yogender Singh
Email Address - complaints-in@stripe.com
Address - Prestige Tech Pacific Park, 10th Floor, Building 2, Kadubeesanahalli Village, Varthur Hobli, Bangalore East Taluk, Bangalore-560103 Karnataka, India
For more information about complaint handling, please visit here.
Separately, for law enforcement requests, please contact LERequests@stripe.com.
If we are unable to address your complaint or grievance, you have the right to escalate the matter to the Data Protection Board of India.

Qualifications & exceptions

  • If we are unable to address your complaint or grievance

Not stated here

  • The linked India complaint-handling guidance is not supplied; further procedures are not inferred.

Account & Service Control · User right or choice

The India section offers processing summaries and nomination for death or incapacity

Privacy concerns can also go to the DPO at dpo@stripe.com. The India section says you may request a summary of data and related processing or nominate another person to exercise rights on death or incapacity. It does not specify a nomination form or further eligibility requirements here.

Supporting quotations

For privacy related questions or concerns, you may also contact Stripe’s Data Protection Officer (“DPO”) via dpo@stripe.com. In particular, you may contact Stripe to request a summary of the Personal Data being processed about you and the related processing activities, or to nominate another individual who may exercise your rights in the event of your death or incapacity.

Qualifications & exceptions

  • in the event of your death or incapacity.
Also annotated in the same passage (1)

Account & Service Control · Permission or license

The India IT Rules notice reserves immediate access termination or content removal for noncompliance

Under the Notification IT Rules 2021 heading, the publisher says noncompliance with rules/regulations, its Privacy Policy or user agreement can lead to immediate termination of access/usage rights, removal of noncompliant information, or both as appropriate. This states a right to act, not an automatic outcome for every case.

Supporting quotations

We are required to inform you that in case of non-compliance with rules and regulations, our Privacy Policy or user agreement, we have the right to terminate your access or usage rights immediately or remove non-compliant information or both, as the case may be.

Qualifications & exceptions

  • in case of non-compliance with rules and regulations, our Privacy Policy or user agreement

Data Access & Collection · Company practice

Cookie purposes and placement vary by service, relationship and domain

Cookies/similar technology support functioning, fraud/terms enforcement, Visitor engagement analysis, advertising where allowed, and service/site improvement and personalization. Different cookies apply on public Stripe/Link sites, dashboards/settings and payment pages; cookies change as services develop. Full details are referred to a separate Cookie Policy.

Supporting quotations

We use cookies and similar technologies to (1) ensure that our Services function properly, (2) prevent and detect fraud and violations of our terms of service, (3) understand how Visitors use and engage with our Site, (4) advertise our products and Services, where allowed
Depending on your relationship with Stripe and the domain you are visiting, different cookies apply.
Please be mindful that we change the cookies periodically as we improve or add to our Services.

Qualifications & exceptions

  • where allowed
  • Depending on your relationship with Stripe and the domain you are visiting, different cookies apply.

Not stated here

  • The linked Cookie Policy is not supplied; full cookie inventories and lifetimes are not inferred.

Security & Safeguards · Company practice

Stripe.js fraud cookies collect behavioral signals with restricted internal access

The payment integration library supports fraud prevention and Link. Fraud cookies including __stripe_mid, __stripe_sid and m collect signals such as page time to assess transaction fraud risk. The publisher commits not to share/sell Stripe.js fraud data to advertisers and says it works to keep this data in Stripe infrastructure, exchanged among js.stripe.com, m.stripe.network and m.stripe.com with access restricted to a small employee group whose permissions are reviewed.

Supporting quotations

Stripe uses Stripe.js to facilitate fraud prevention technologies and the use of its Link payment Services on the websites of Business Users.
For fraud detection, Stripe.js uses cookies, including `__stripe_mid`, `__stripe_sid`, and `m`, to collect signals differentiating legitimate behavior from fraudulent behavior.
Stripe doesn’t—and won’t—share or sell the fraud data it collects using Stripe.js to advertisers.
It is exchanged between the following Stripe-controlled hosts:js.stripe.com, m.stripe.network, and m.stripe.com, and access to this data within the Stripe infrastructure is tightly restricted to a small number of Stripe employees whose security permissions are regularly reviewed.

Qualifications & exceptions

  • Stripe doesn’t—and won’t—share or sell the fraud data it collects using Stripe.js to advertisers.

Data Access & Collection · Company practice

Stripe.js also supports remembered Link checkout and implementation analytics

Technology such as pay_sid, link.auth_session_client_secret and elements_session remembers users across merchant checkouts and collects Link implementation analytics. Merchants should review cookies/data and consult counsel on customer disclosure and banners. Product configuration determines cookies, and the notice says elements_session analytics is set only in some US states. The fraud-data advertising restriction should not be generalized to every cookie purpose.

Supporting quotations

Stripe also uses the Stripe.js library to implement cookies and similar technology such as `pay_sid`, `link.auth_session_client_secret`, and `elements_session` to enable Link to remember users’ information for faster checkout across Stripe merchant sites and to collect analytics related to Link’s implementation on checkout pages.
You should regularly review the Stripe cookies that are placed on your website and other data collected by Stripe.js. You should consult your counsel regarding how best to disclose this data collection to your customers, including by updating your cookie banner
for the avoidance of doubt, the elements_session analytics cookie is only set in some US states
The specific cookies used by stripe.js depend on your configuration with the related Stripe products.

Qualifications & exceptions

  • the elements_session analytics cookie is only set in some US states
  • The specific cookies used by stripe.js depend on your configuration with the related Stripe products.
Also annotated in the same passage (1)

Use & Processing · Company commitment

Advanced fraud signals protect accounts and payments and are not used for third-party ad targeting

Device characteristics/activity indicators power fraud systems such as Radar and are securely sent periodically to m.stripe.com. Protection covers the publisher, businesses, users/customers and Financial Partners against fraud, account takeover, bots, unauthorized transactions and multi-account abuse; depending on service it covers registration/login as well as payments. The publisher says it neither uses these signals for third-party ad targeting nor shares/sells them to third-party advertisers for their own advertising.

Supporting quotations

Stripe’s advanced fraud detection looks at signals about device characteristics and user activity indicators that help distinguish between legitimate and fraudulent transactions.
The signals are securely transmitted to Stripe’s backend by periodically making requests to the m.stripe.com endpoint.
You can learn more in our documentation for advanced fraud detection.
Stripe uses advanced fraud signals to protect Stripe, Business Users, End Users, End Customers, and Financial Partners from fraud, account takeover, bots, unauthorized transactions, multi-account abuse, and other harmful activity.
Depending on the Stripe service implemented, this may include protecting account registration and login processes as well as payment transactions.
Stripe does not use advanced fraud signals to target third-party advertising to individuals, and does not share or sell these signals to third-party advertisers for their own advertising purposes.

Qualifications & exceptions

  • Depending on the Stripe service implemented, this may include protecting account registration and login processes as well as payment transactions.
  • does not share or sell these signals to third-party advertisers for their own advertising purposes.

Not stated here

  • Linked advanced-fraud documentation is not supplied; additional implementation detail is not inferred.

Cross-references

Legal Rights & Agreement Rules · Procedure

Merchants should review cookies and present disclosures before collection where practicable

Cookie obligations vary with business/customer location. Merchants should review deployed cookies, update disclosures/banners, and where cookies collect immediately, present disclosures/consent before Stripe.js starts where reasonably practicable. If consent is collected at transaction completion, the policy should be conspicuous at or before that point. Customer consent to the merchant’s policy is expected as applicable law requires. Radar fraud cookies help reduce chargebacks/losses; this purpose does not eliminate local compliance obligations.

Supporting quotations

Radar uses cookies to help businesses reduce chargebacks and losses from fraudulent transactions.
Please note that the use of cookies may have legal implications depending on the geographical location of your business and customers.
If cookies begin collecting data as soon as they load, your privacy disclosures and any consent mechanisms should be presented to end users before the Stripe.js library is initiated where reasonably practicable.
If your implementation obtains an end user’s consent when the user completes a transaction, the relevant privacy policy should be clearly and conspicuously presented at or before that point.
Stripe expects that any merchant using Stripe Services that involve the collection of end user data has obtained consent to its privacy policy from its customers as required by applicable law.

Qualifications & exceptions

  • where reasonably practicable.
  • as required by applicable law.
Also annotated in the same passage (2)

Legal Rights & Agreement Rules · Context

The suggested merchant notice describes several data categories and uses

The illustrative disclosure mentions identifiers, transactions, online activity, location and browser/device information for operating/improving services, fraud/loss prevention, authentication, analytics and customization. It is suggested text to adapt if information is missing, not a guarantee of legal sufficiency. The separate location passage describes approximate location derived from End Customer IP for fraud; the example does not itself authorize GPS tracking.

Supporting quotations

Here is a paragraph you could add to your privacy disclosures if they do not already include such information:
The personal data Stripe collects may include identifiers, transactional data, online activity information, location data, and identifying information about devices and browsers that connect to its services.
Stripe uses this information to operate and improve the services it provides to us, including for fraud and loss prevention and detection, authentication, analytics related to the performance of its services, and to enhance and customize the user experience.
Stripe may use location information, including approximate latitude and longitude, derived from End Customers IP addresses to detect potentially fraudulent transactions.

Qualifications & exceptions

  • derived from End Customers IP addresses to detect potentially fraudulent transactions.
Also annotated in the same passage (3)

Data Access & Collection · Company practice

The cookie table maps three fraud cookies to Radar

The product overview identifies m, __stripe_mid and __stripe_sid as Fraud Prevention cookies used with Radar to assess attempted-transaction risk. These categories describe function rather than a legal exemption from cookie requirements.

Supporting quotations

Below is an overview of the specific cookies associated with each product and their respective functions for Embeddable Checkout, Elements, Radar, and Link.
m
Fraud Prevention
Set for fraud prevention purposes and helps us assess the risk associated with an attempted transaction.
Radar
__stripe_mid
Fraud Prevention
Set for fraud prevention purposes and helps us assess the risk associated with an attempted transaction.
Radar
__stripe_sid
Fraud Prevention
Set for fraud prevention purposes and helps us assess the risk associated with an attempted transaction.
Radar

Data Access & Collection · Company practice

Authentication cookie functions differ by product

pay_sid provides logged-in Link purchasing on merchant sites and is listed for Link, Embeddable Checkout, Checkout and Elements. __Host-LinkSession stores consumer credentials for one-click checkout with Link/Elements. link.auth_session_client_secret provides logged-in Stripe-hosted payment and Crypto Onramp experiences and is listed for Link. The table does not state their lifetimes.

Supporting quotations

pay_sid
Authentication
Provide a logged-in experience when a consumer uses link.com to make purchases on a merchant site.
Link, Embeddable Checkout, Checkout & Elements
__Host-LinkSession
Authentication
Stores consumer credentials to provide a one-click payment experience at checkout.
Link & Elements
link.auth_session_client_secret
Authentication
Provide a logged-in experience when a consumer uses Stripe-hosted payment UIs to make purchases and Crypto Onramp to purchase crypto.
Link

Data Access & Collection · Restriction or exception

elements_session analytics measures product changes only in some US states

The table lists elements_session for analytics in Embeddable Checkout, Elements and Link, measuring product-change results and performance. Although the row says US-only, the surrounding text narrows it to some US states; product configuration also determines which cookies are used.

Supporting quotations

elements_session
Analytics
The `elements_session` US-only cookie allows us to measure the result of changes we make to the Stripe Elements product and ensure that the performance of the product continues to improve over time.
Embeddable Checkout, Elements & Link
the elements_session analytics cookie is only set in some US states
The specific cookies used by stripe.js depend on your configuration with the related Stripe products.

Qualifications & exceptions

  • the elements_session analytics cookie is only set in some US states
  • The specific cookies used by stripe.js depend on your configuration with the related Stripe products.
Also annotated in the same passage (1)

Legal Rights & Agreement Rules · Procedure

Sites integrating Link should assess cookie duties and update disclosures

Integration choice, such as Link in Elements, may bring legal responsibilities for fraud/authentication technologies. The notice recommends legal advice, regular review and banner/disclosure updates. Stripe.js sets cookies on the merchant’s domain, including fraud cookies and pay_sid/__Host-LinkSession authentication cookies; the integration choice matters rather than a universal single cookie set.

Supporting quotations

Based on your integration choice (e.g., for Link in Elements), you may have legal responsibilities associated with cookies and similar technology that Stripe uses for fraud detection and/or authentication purposes.
You should always check with your legal counsel to understand how you should comply with applicable legal obligations with setting cookies and similar technology.
Stripe cookies or similar technology are set on your domain (e.g. on your checkout flow) from the Stripe.js library.
You should regularly review the Stripe cookies that are placed on your website to ensure that your own privacy disclosures tell your End Users about this type of data collection, and also update your cookie banner accordingly after reviewing the cookies placed on your website.

Qualifications & exceptions

  • Based on your integration choice (e.g., for Link in Elements)
Also annotated in the same passage (1)

Legal Rights & Agreement Rules · Procedure

Link integrators should keep cookie notices and banners aligned with actual collection

The notice recommends regularly reviewing cookies and updating privacy disclosures/banners. Its suggested paragraph describes identifiers, transactions, online activity and browser/device data for services, fraud/loss prevention, authentication and analytics. It is optional sample wording if a disclosure is absent; applicable consent requirements and pre-load disclosure where reasonably practicable still apply.

Supporting quotations

You should regularly review the Stripe cookies that are placed on your website to ensure that your own privacy disclosures tell your End Users about this type of data collection, and also update your cookie banner accordingly after reviewing the cookies placed on your website.
The personal data Stripe collects may include identifiers, transactional data, online activity information, and identifying information about browsers and devices that connect to its services. Stripe uses this information to operate and improve the services it provides to us, including for fraud detection, loss prevention, authentication, and analytics related to the performance of its services.
If cookies begin collecting data as soon as they load, your privacy disclosures and any consent mechanisms should be presented to end users before the Stripe.js library is initiated where reasonably practicable.
Stripe expects that any merchant using Stripe Services that involve the collection of end user data has obtained consent to its privacy policy from its customers as required by applicable law.

Qualifications & exceptions

  • where reasonably practicable.
  • as required by applicable law.
Also annotated in the same passage (3)

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

Account & Service Control · Procedure

Privacy questions can use the request form or listed US and Irish postal contacts

After reviewing the policy, readers can contact the privacy team by email or the linked form. Physical mail is directed to Stripe Legal at Stripe, LLC, 354 Oyster Point Boulevard, South San Francisco, California 94080, USA; or Stripe Technology Company Limited, One Wilton Park, Wilton Place, Dublin 2, D02 FX04, Ireland. These are contact addresses in the saved notice, not a reassignment of every processing activity to either entity.

Supporting quotations

If you have any outstanding privacy questions after reviewing the privacy policy, please don’t hesitate to reach out to us by email, or through our form.
If you’d like to send us physical mail, please send to:
Stripe, LLC
354 Oyster Point Boulevard
South San Francisco, California, 94080, USA
Attention: Stripe Legal
Stripe Technology Company Limited
One Wilton Park, Wilton Place, Dublin 2, D02 FX04, Ireland
Attention: Stripe Legal

Security & Safeguards · Procedure

Report known unauthorized use or security breaches immediately

The notice directs users to contact support immediately upon learning of unauthorized use or another security breach involving the services. A separate security page is provided for further practices; its additional promises are not supplied here.

Supporting quotations

Visit our security page to learn more about Stripe’s security practices. You should contact us immediately if you become aware of any unauthorized use or any other breach of security regarding the Stripe services.

Qualifications & exceptions

  • if you become aware of any unauthorized use or any other breach of security regarding the Stripe services.

Not stated here

  • The linked security page is not supplied; further safeguards are not inferred.

Use & Processing · Context

The Privacy Center explains data practices and individual rights

The Privacy Center describes the publisher’s collection and use of personal data, individuals’ rights, and international data-protection compliance. The platform collects and processes personal data to provide services to Business Users and End Users.

Supporting quotations

in order to provide our services to our Business Users and End Users, we collect and process personal data.
The Stripe Privacy Center contains the answers to frequently asked questions about how we collect and use personal data, the rights that individuals have in relation to personal data held by Stripe, and how Stripe complies with international data protection laws.

Qualifications & exceptions

  • in order to provide our services to our Business Users and End Users

Legal Rights & Agreement Rules · Restriction or exception

Privacy Center information may change without notice

The materials are general information, not legal advice to act on. The publisher warns that the information may not be current and may change without notice.

Supporting quotations

All materials have been prepared for general information purposes only. The information presented is not legal advice, is not to be acted on as such, may not be current and is subject to change without notice.

Qualifications & exceptions

  • The information presented is not legal advice, is not to be acted on as such, may not be current and is subject to change without notice.

Account & Service Control · Context

Business Users supply data in connection with their own activities

Business Users are entities receiving the publisher’s services that directly or indirectly provide End Customer personal data for their own business activities. Examples include merchants, platform users and Connect accounts.

Supporting quotations

Stripe provides services to entities (“Business Users”) who directly and indirectly provide us with “End Customer” Personal Data in connection with those Business Users’ own business and activities.
Stripe user or merchant Platform User Connect Accounts

Account & Service Control · Context

End Customers transact with a Business User

An End Customer does business or transacts with a Business User without directly doing business with the publisher. The table gives individuals using Identity and cardholders using Checkout as examples. This differs from using a consumer product directly.

Supporting quotations

When you do business with, or otherwise transact with, a Business User (typically a merchant using Stripe Checkout, e.g. when you buy a pair of shoes from a merchant that uses Stripe for payment processing) but are not directly doing business with Stripe, we refer to you as an “End Customer.”
Individual using Identity Cardholder using Checkout

Qualifications & exceptions

  • but are not directly doing business with Stripe

Account & Service Control · Context

End Users use consumer products for personal use

An End User uses one or more of the publisher’s consumer products or services for personal use. Examples include saving bank details with Financial Connections and personally contributing to Climate.

Supporting quotations

When you use one or more of the Stripe consumer products and services we offer for your personal use, we refer to you as an “End User.”
Saving your bank account information with Financial Connections; Personal contributor to Stripe Climate

Account & Service Control · Context

Representatives act for an existing or potential Business User

A Representative acts on behalf of an existing or potential Business User, such as a founder or merchant-account administrator. The table includes beneficial owners, shareholders, officers, directors and account representatives.

Supporting quotations

When you are acting on behalf of an existing or potential Business User (e.g., you are a founder of a company, or administering an account for a merchant who is a Business User), we refer to you as a “Representative.”
Beneficial owner Shareholder, officer, director Account representative

Account & Service Control · Context

Visitors browse without logging in or otherwise contact the publisher

Visitors include people visiting a site without logging into an account and people otherwise communicating with the publisher, including prospective users asking for information. The table lists Sessions attendees and site visitors.

Supporting quotations

When you visit a Site without being logged into a Stripe account or otherwise communicate with Stripe, we refer to you as a “Visitor.”
Stripe Sessions attendee Stripe Site visitor

Use & Processing · Context

Controller and processor roles depend on the processing activity

The publisher may act as controller for some activities and processor for others, including within one customer relationship or transaction. A controller determines processing purposes and means; a processor acts on a controller’s behalf and instructions.

Supporting quotations

Stripe may act as a data controller for some activities and as a data processor for other activities, including within the same customer relationship or transaction.
The “data controller” is the entity which determines the purposes and means of the data processing taking place. The “data processor” is an entity acting on behalf and under the instructions of a controller in processing Personal Data.
Stripe is a data controller when it determines the purposes and means of the processing taking place.

Qualifications & exceptions

  • including within the same customer relationship or transaction.

Use & Processing · Company practice

Some payment processing and Business User support are processor activities

When processing personal data on a Business User’s behalf and direction for particular services, the publisher acts as processor. Examples include certain instructed payment-processing activities and servicing the platform, such as answering a Business User’s support request. This does not mean all activity in the relationship is processor activity.

Supporting quotations

Stripe is a data processor where it processes Personal Data on behalf of and at the direction of a Business User in providing particular Stripe services.
Stripe is also considered a data processor when servicing the Stripe platform (e.g. when Stripe responds to a request for customer support from a Business User).

Qualifications & exceptions

  • on behalf of and at the direction of a Business User

Legal Rights & Agreement Rules · Context

Business User contracts use consistent platform commitments

The publisher says it contracts with all Business Users on the basis of consistent commitments about how its platform operates, including its largest business customers. This statement does not supply the terms of any individual contract.

Supporting quotations

As a platform provider, we need to ensure consistency across our platform, and that includes consistency with respect to the commitments that we give about how we operate our platform. We contract with all of our Business Users (including some of the world’s largest companies) on this basis.

Use & Processing · Context

The responsible entity depends on location, product and processing context

For most services the primary controller is the US parent, Stripe, LLC, or Ireland’s Stripe Technology Company, Limited (STC). The particular responsible entity depends on your location, product or service, and whether the activity involves a controller or processor role. The jurisdiction table gives further distinctions.

Supporting quotations

For most of our services, the primary data controller is either Stripe, LLC. the U.S. parent company operating under US law or Stripe Technology Company, Limited (“STC”), an Irish company operating under Irish law.
The Stripe entities responsible for your data will depend on your location, the product or service you use with us and the specific context of the data processing which determines whether Stripe is acting as a data controller and/or data processor.
Please see our table below for more information on which Stripe entity is your data controller in these jurisdictions:

Qualifications & exceptions

  • For most of our services

Use & Processing · Context

Outside the Americas, Irish and local entities may be joint controllers

Outside the Americas, including the EEA, Switzerland, UK, Middle East, Africa and APAC, the listed entities may be controllers individually or jointly depending on the service. STC is the main European establishment and has primary responsibility outside the Americas. Stripe Payment Europe, Limited (SPEL) primarily contracts with users in certain non-Americas jurisdictions. Where an authorised provider or electronic-money institution is required, or otherwise specified, the local regulated entity provides the services and is a joint controller with STC and SPEL.

Supporting quotations

If you are located outside of the Americas [e.g., European Economic Area (“EEA”), Switzerland, the United Kingdom, the Middle East and Africa, or Asia Pacific (“APAC”)], the following entities may act as data controllers, either individually or jointly depending on the product or service you use:
STC has primary responsibility for processing your Personal Data outside of the Americas.
Stripe Payment Europe, Limited (“SPEL”): An Irish company with principal responsibility for contracting with Stripe Users in certain jurisdictions outside of the Americas (see table below).
When payment processing services offered by Stripe require an authorised provider or electronic money institution or where otherwise specified, the Stripe local regulated entity will provide those services. In such instances STC, SPEL and the relevant Stripe local regulated entity are joint data controllers of your Personal Data.

Qualifications & exceptions

  • When payment processing services offered by Stripe require an authorised provider or electronic money institution or where otherwise specified

Legal Rights & Agreement Rules · Context

The DPA contracting entity differs inside and outside the Americas

The Data Processing Agreement is with Stripe, LLC for people located in the Americas and SPEL for people located outside the Americas. This identifies the contracting entity without supplying the separate DPA’s terms.

Supporting quotations

If you are located in the Americas, your Data Processing Agreement (“DPA”) will be with Stripe, LLC and if you are located outside of the Americas, your DPA will be with SPEL.

Use & Processing · Context

Australia’s entity table separates regulated services, the DPA and other activity

For Australia, the table lists Stripe Payments Australia Pty Ltd (A.C.N. 160 180 343), located in Australia, for services and regulated activities under the linked Australian services agreement, followed by STC in Ireland. It lists SPEL in Ireland as the DPA contracting entity and STC in Ireland for all other activities. The continuation rows leave the location cell blank; they appear within the Australia group. Separate linked agreement terms are not supplied here.

Supporting quotations

Australia
Provision of services and regulated activities in accordance with
Stripe Payments Australia Pty Ltd A.C.N. 160 180 343
Australia
STC
Ireland
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland

Use & Processing · Context

Brazil’s entity table lists local and US entities

For Brazil, the table lists Stripe Brasil Soluções de Pagamento - Instituição de Pagamento Ltda, located in Brazil, for services and regulated activities under the linked Brazilian agreement, followed by Stripe, LLC in the USA. It lists Stripe, LLC in the USA for all other activities. Continuation rows have blank location cells within the Brazil group; the linked agreement is not supplied.

Supporting quotations

Brazil
Provision of services and regulated activities in accordance with
Stripe Brasil Soluções de Pagamento - Instituição de Pagamento Ltda
Brazil
Stripe, LLC
USA
All other activities
Stripe, LLC
USA

Use & Processing · Context

Canada’s entity table lists Canadian and US entities

For Canada, the table lists Stripe Payments Canada, Ltd, located in Canada, for services and regulated activities under the linked Canadian agreement, followed by Stripe, LLC in the USA. It lists Stripe, LLC in the USA for all other activities. Continuation rows have blank location cells within the Canada group; the linked agreement is not supplied.

Supporting quotations

Canada
Provision of services and regulated activities in accordance with
Stripe Payments Canada, Ltd
Canada
Stripe, LLC
USA
All other activities
Stripe, LLC
USA

Use & Processing · Context

The EEA regulated-services row names Stripe Technology Europe, Limited

For certain authorised payment services and other regulated activities in the EEA, the table names Stripe Technology Europe, Limited, located in Ireland, and points to the Irish services agreement. This is the regulated-services row, not a claim that this entity alone controls all EEA processing.

Supporting quotations

EEA
Provision of certain authorised payment services and other regulated activities in the EEA.
Stripe Technology Europe, Limited
Ireland
Also annotated in the same passage (1)

Use & Processing · Context

EEA contracting and other activities use different Irish entities

Within the EEA group, SPEL in Ireland is listed as the contracting entity under the services agreement and DPA. STC in Ireland is listed for all other activities. This supplements the separate regulated-services row and does not supply the linked contracts.

Supporting quotations

Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland
Provision of certain authorised payment services and other regulated activities in the EEA.
Also annotated in the same passage (1)

Use & Processing · Context

India’s table separates local services from Irish contracting and other activities

For India, the table names Stripe India Private Limited in India for services and regulated activities under the linked Indian agreement, followed by STC in Ireland. SPEL in Ireland is the DPA contracting entity, and STC in Ireland is listed for all other activities. The continuation rows sit within the India group; linked contract terms are not supplied.

Supporting quotations

India
Provision of services and regulated activities in accordance with
Stripe India Private Limited
India
STC
Ireland
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland

Use & Processing · Context

Indonesia’s table names local and Irish entities by activity

Within the Indonesia group, PT Stripe Payments Indonesia in Indonesia is listed for services and regulated activities under the linked agreement, followed by STC in Ireland. The DPA contracting entity is SPEL in Ireland, and all other activities list STC in Ireland. These entries identify entities without supplying the linked agreements.

Supporting quotations

Indonesia
Provision of services and regulated activities in accordance with
PT Stripe Payments Indonesia
Indonesia
STC
Ireland
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland

Use & Processing · Context

Japan’s services row names Stripe Japan and STC

For services under the linked Japanese agreement, the Japan row lists Stripe Japan, Inc. and STC, with Japan and Ireland as entity locations. Within that group, SPEL in Ireland is the DPA contracting entity, and STC in Ireland covers all other activities. The table does not supply the linked contracts.

Supporting quotations

Japan
Provision of services in accordance with
Stripe Japan, Inc.
STC
Japan
Ireland
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland

Use & Processing · Context

Malaysia distinguishes local regulated services, DPA contracting and other activity

For Malaysia, Stripe Payments Malaysia Sdn. Bhd. in Malaysia is listed for services and regulated activities under the linked agreement, followed by STC in Ireland. SPEL in Ireland is the DPA contracting entity and STC in Ireland is listed for all other activities. Continuation rows belong to the Malaysia group; the linked contracts are not supplied.

Supporting quotations

Malaysia
Provision of services and regulated activities in accordance with
Stripe Payments Malaysia Sdn. Bhd.
Malaysia
STC
Ireland
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland

Use & Processing · Context

Mexico’s table lists Mexican and US entities

For services under the linked Mexican agreement, the Mexico group lists Stripe Payments Mexico, S. de R.L. de C.V. in Mexico, followed by Stripe, LLC in the USA. All other activities list Stripe, LLC in the USA. The linked agreement’s terms are not included by this entity identification.

Supporting quotations

Mexico
Provision of services in accordance with
Stripe Payments Mexico, S. de R.L. de C.V.
Mexico
Stripe, LLC
USA
All other activities
Stripe, LLC
USA

Use & Processing · Context

UK regulated services and contracting have separate listed entities

For authorised payment services and other regulated activities in the UK, the table lists Stripe Payments UK, Ltd., located in the UK. SPEL in Ireland is the contracting entity under the linked services agreement and DPA; STC in Ireland is listed for all other activities within the UK group. This does not supply those linked contracts.

Supporting quotations

United Kingdom
Provision of authorised payment services and other regulated activities in the UK.
Stripe Payments UK, Ltd.
United Kingdom
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland

Use & Processing · Context

The US table names a general entity and entities for specific regulated services

For the United States, the table lists Stripe, LLC in the USA for “All activities.” It also names Stripe Brokering, Inc. in the USA for facilitating bank-partner lending connected with Capital loans, and Stripe Payments Company in the USA for certain money-transmission or other services regulated under US law. The general row does not erase these specific entries.

Supporting quotations

United States
All activities
Stripe, LLC
USA
Provision of lending facilitation services to bank partners in connection with Stripe Capital loans in the United States
Stripe Brokering, Inc.
USA
Provision of certain Stripe Services which involve money transmission or other regulated services under U.S. Law.
Stripe Payments Company
USA

Qualifications & exceptions

  • Provision of lending facilitation services to bank partners in connection with Stripe Capital loans in the United States
  • Provision of certain Stripe Services which involve money transmission or other regulated services under U.S. Law.

Use & Processing · Context

New Zealand’s services row lists local and Irish entities

The New Zealand services and regulated-activities row lists Stripe New Zealand Limited and STC, with New Zealand and Ireland as entity locations. Within that group, SPEL in Ireland is the DPA contracting entity, and STC in Ireland is listed for all other activities. The table links to the relevant agreements without supplying their terms.

Supporting quotations

New Zealand
Provision of services and regulated activities in accordance with
Stripe New Zealand Limited
STC
New Zealand
Ireland
Your contracting entity under our
SPEL
Ireland
All other activities
STC
Ireland

Use & Processing · Context

Singapore’s services entries name local and Irish entities

For services and regulated activities under the linked Singapore agreement, the Singapore table group lists Stripe Payments Singapore Pte. Ltd. in Singapore, followed by STC in Ireland. This card concerns those services entries; later rows separately address contracting and other activities.

Supporting quotations

Singapore
Provision of services and regulated activities in accordance with
Stripe Payments Singapore Pte. Ltd.
Singapore
STC
Ireland
Also annotated in the same passage (1)

Use & Processing · Context

Thailand’s other-activities entity is located in Ireland

The final location cell for Thailand’s STC entry identifies Ireland. It completes the preceding other-activities row in the entity table.

Supporting quotations

Ireland
STC

Use & Processing · Context

Other Americas jurisdictions use Stripe, LLC for the listed activities and contracts

For any other jurisdiction in the Americas, the table identifies Stripe, LLC in the USA for all other activities and as the DPA and services-agreement contracting entity. This residual row does not replace the earlier country-specific rows.

Supporting quotations

Any other jurisdiction in the Americas
All other activities and your contracting entity under our DPA and SSA.
Stripe, LLC
USA

Use & Processing · Context

Other EMEA jurisdictions distinguish contracting, stablecoin services and other activity

In the residual EMEA group, SPEL in Ireland is the DPA and services-agreement contracting entity. Stripe, LLC in the USA is listed for Stablecoin Financial Account UX Services under the linked terms, and STC in Ireland for all other activities. Those linked service terms are not supplied here.

Supporting quotations

Any other jurisdictions in EMEA
Your contracting entity under our DPA and SSA
SPEL
Ireland
Provision of Stablecoin Financial Account UX Services in accordance with
Stripe, LLC
USA
All other activities
STC
Ireland

Use & Processing · Context

The residual APAC entity group excludes Hong Kong

For other APAC jurisdictions except Hong Kong (SAR), the table names Stripe, LLC in the USA for Stablecoin Financial Account UX Services under linked terms, SPEL in Ireland as DPA and services-agreement contracting entity, and STC in Ireland for all other activities. This row does not identify an entity for Hong Kong.

Supporting quotations

Any other jurisdictions in APAC, except for Hong Kong (SAR)
Provision of Stablecoin Financial Account UX Services in accordance with
Stripe, LLC
USA
Your contracting entity under our DPA and SSA
SPEL
Ireland
All other activities
STC
Ireland

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)

Use & Processing · Company practice

Controller activities include choosing partners and running business operations

The controller-activity list includes determining and using third parties such as banks, payment-method providers and other financial partners. It also includes internal processes supporting products and services, such as relationship management, billing and invoicing.

Supporting quotations

Determine and utilize third parties (e.g., banks, payment method providers and other Financial Partners);
Implement, maintain and perform internal processes that enable Stripe to provide its products and Services, including relationship management, billing and invoicing;

Security & Safeguards · Company practice

Fraud prevention, risk mitigation and legal compliance are controller activities

Listed controller activities include monitoring, preventing and detecting fraudulent transactions or activity; monitoring, preventing and mitigating financial loss, security risk and other harm; and compliance with law, including AML screening and KYC obligations, plus financial-partner and governmental requirements and requests.

Supporting quotations

Monitor, prevent and detect fraudulent transactions and other fraudulent activity on the Stripe platform;
Monitor, prevent and mitigate financial loss, security risks, and other harm;
Comply with Law, including applicable anti-money laundering screening and know-your-customer obligations, and Financial Partner and Governmental Authority requirements and requests;

Use & Processing · Company practice

Controller activities also include subscriptions, BNPL and product development

The list includes managing subscription and Buy Now Pay Later transactions, as well as analyzing and developing products and services, including training AI technology. This identifies controller activities; later sections describe particular uses and limits.

Supporting quotations

Manage subscription and Buy Now Pay Later transactions; and Analyze and develop Stripe’s products and Services, including training AI technology.

Inference & Profiling · Company practice

Personal data trains fraud and loss-prevention models

Some data collected in providing services, including personal data, is used to improve products, train fraud and loss-prevention models, and analyze product performance as permitted by applicable law and agreements. Radar and Identity models use personal data, including comparisons between transaction data and past data, to recognize potential fraud, impersonation or transactions unlikely to complete. This describes model training, not a claim that all personal data is always used or that scores measure a person’s creditworthiness.

Supporting quotations

Stripe uses some of the data it collects to improve its products and Services, including by training the models it employs for fraud and loss prevention and to analyze the performance of Stripe’s products as permitted by applicable law and agreements.
Personal Data is required to train Stripe’s fraud and loss prevention models, including those employed by Stripe Radar and Stripe Identity.
For example, they compare Personal Data presented in a specific transaction to Personal Data collected in the past to identify when a fraudster is attempting to perpetrate fraud, including to impersonate a Stripe User or their End Customers.

Qualifications & exceptions

  • as permitted by applicable law and agreements.

Use & Processing · Company practice

Checkout and authorization data support product-performance analysis

Transaction data helps assess current products and proposed improvements. Examples include stripe.js data about checkout surfaces, payment-authorization data about authorization rates, and IP addresses to identify pages or features used in a checkout session. Pseudonymized or aggregated transaction data is used in some circumstances. When performance results are communicated to Business Users or for advertising, they are only aggregated or de-identified so outsiders cannot associate them with particular End Customers.

Supporting quotations

In addition to using Personal Data to train its fraud and loss prevention models, Stripe also uses Transaction Data to assess the functioning of its current products and proposed product improvements.
Stripe uses Personal Data, such as IP address, to identify which pages and features a user interacted with during a checkout session, so that it can assess the effect different features have on the outcome of a checkout session.
Stripe uses pseudonymized or aggregated Transaction Data for these purposes in certain circumstances. When Stripe communicates the results of its product performance analytics to Business Users or for advertising purposes, it does so only in aggregated or de-identified form that does not permit third-parties outside of Stripe to associate that data with any particular End Customers.

Qualifications & exceptions

  • When Stripe communicates the results of its product performance analytics to Business Users or for advertising purposes, it does so only in aggregated or de-identified form that does not permit third-parties outside of Stripe to associate that data with any particular End Customers.

Legal Rights & Agreement Rules · Procedure

Merchants are directed to counsel and a suggested disclosure paragraph

The Privacy Center advises consulting legal counsel about disclosing the publisher’s data use to customers. It points to a suggested paragraph in the merchant-cookie section; that is guidance to consider, not a promise that using the example satisfies every legal requirement.

Supporting quotations

You should consult your legal counsel regarding how best to disclose Stripe’s data usage to your customers.
But we have included a suggested paragraph you could add to your privacy policy under ‘What obligations should merchants keep in mind relating to cookie technology on their sites?’

Qualifications & exceptions

  • a suggested paragraph you could add to your privacy policy

Linking & Identification · Company practice

Transaction patterns across merchants may improve payment handling

Processing transactions for many Business Users lets the publisher identify patterns for submitting authorization requests. It may analyze signals pooled across its global merchant network to improve authentication and authorization, reduce failures, prevent fraud and disputes, and optimize routing. Patterns involving one Business User may therefore inform authorization submission or routing for another.

Supporting quotations

Stripe processes transactions for many Business Users. This allows Stripe to identify patterns that can help determine how payment authorization requests are most effectively submitted to banks and payment networks.
Stripe may analyze transaction signals pooled across its global merchant network to improve authentication and authorization rates, reduce payment failures, prevent fraud and disputes, and optimize payment routing. This means that patterns observed from transactions involving one Business User may help Stripe determine how to submit or route authorization requests involving another Business User.

Qualifications & exceptions

  • to improve authentication and authorization rates, reduce payment failures, prevent fraud and disputes, and optimize payment routing.
Also annotated in the same passage (1)

Linking & Identification · Company practice

Pooled payment signals include transaction, device and fraud information

To improve authentication, authorization and routing, reduce failures, and prevent fraud or disputes, the publisher may pool global merchant-network signals. Examples include authorization outcomes and decline reasons; payment-method/card characteristics; amount and currency; merchant/industry characteristics; authentication results; device, browser and approximate-location signals; and fraud, dispute or chargeback indicators. Activity involving one Business User can inform handling of another’s transactions.

Supporting quotations

Stripe may analyze transaction signals pooled across its global merchant network to improve authentication and authorization rates, reduce payment failures, prevent fraud and disputes, and optimize payment routing.
The signals used for these purposes may include information such as:
whether previous authorization requests succeeded or failed;
the reason an authorization request was declined;
payment-method and card characteristics;
transaction amount and currency;
merchant and industry characteristics;
authentication results;
device, browser, and approximate location signals; and
fraud, dispute, or chargeback indicators.

Qualifications & exceptions

  • to improve authentication and authorization rates, reduce payment failures, prevent fraud and disputes, and optimize payment routing.
Also annotated in the same passage (1)

Inference & Profiling · Company practice

Payment predictions may select, recommend or retry a pathway

Signals are used to calculate how likely a routing, authentication or authorization approach is to succeed. Depending on the service, the prediction may select, recommend or retry a payment pathway. These models aim to improve performance and prevent fraud or loss, rather than produce a standalone assessment of character or creditworthiness. Where automated decisions have legal or similarly significant effects, or law otherwise requires, the publisher provides legally required notices, explanations and choices, subject to applicable legal exceptions.

Supporting quotations

Stripe uses these signals to identify patterns and calculate the likelihood that a particular payment-routing, authentication, or authorization approach will succeed. Depending on the Stripe Service, Stripe may use the resulting prediction to select, recommend, or retry a payment pathway.
These models are intended to improve payment performance and prevent fraud or financial loss. They are not intended to produce a standalone assessment of an individual’s character or creditworthiness.
Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
These rights may be subject to exceptions under applicable law.

Qualifications & exceptions

  • Depending on the Stripe Service
  • They are not intended to produce a standalone assessment of an individual’s character or creditworthiness.
  • Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
  • These rights may be subject to exceptions under applicable law.
Also annotated in the same passage (8)

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.

Inference & Profiling · Company practice

AI training supports fraud prevention, revenue, experience and service recommendations

The publisher trains AI models for purposes including preventing fraud and other harm, increasing Business Users’ authorization rates and revenue realization, improving service experiences, and identifying additional services that may benefit Business Users. Fraud-model training uses different data depending on the fraud being addressed.

Supporting quotations

We train artificial intelligence models that we deploy for a number of purposes, including to prevent fraud and other harm to Stripe, Users, and others, increase authorization rates and revenue realization for Business Users, provide and improve User experience on other Services, and identify when Business Users may benefit from services they are not currently using.
We train artificial intelligence models to prevent fraud in a number of ways, using different kinds of data appropriate to the kinds of fraud we are trying to prevent.

Inference & Profiling · Company practice

Radar training combines service activity with outside fraud signals

Transaction-fraud models powering Radar are trained to recognize fraud including card testing and card cashing. Training uses individual and business activity on the services plus third-party and public information about compromises and attacks. Data may include names, addresses, IP-derived location, payment methods, advanced fraud-detection data, Financial Connections data, and provider signals that transaction details or devices are compromised, fabricated or linked to fraud. The goal is to recognize fraud patterns at transaction time.

Supporting quotations

Our transaction fraud models which power Stripe Radar and are trained to recognize transaction fraud, including card testing and card cashing.
We train such models using data related to activity that individuals and businesses have conducted on our Services. We also use information from third party and publicly available sources including those related to data compromises and fraud attacks.
The training data may include payments Transaction Data, such as names, addresses, location based on IP addresses, and payment method information, advanced fraud detection data, Financial Connections data, and signals from third party providers regarding whether consumer transaction details and device information may have been compromised, fabricated, or associated with fraud.

Qualifications & exceptions

  • The training data may include

Inference & Profiling · Company practice

Issuing fraud models score risk of unauthorized card transactions

Authorization-fraud models for Issuing use activity on cards issued through that program. Training may include transaction, account-holder, authorized-user and merchant data, such as names, emails, card details, addresses and authorization, decline and dispute histories. The models score the risk of a transaction being attempted without authorization; Issuing users can use those scores to block or allow it. Where automated decisions have legal or similarly significant effects, or law otherwise requires, the publisher provides legally required notices, explanations and choices, subject to applicable legal exceptions.

Supporting quotations

We train these models using data related to activity conducted using cards issued through the Stripe Issuing program.
This training data may include Transaction Data, accountholder data, authorized user data, and merchant information, such as names, email addresses, card details, addresses, and histories of authorizations, declines, and disputes.
Based on these features, our models evaluate the circumstances surrounding a transaction presented for authorization on a Stripe Issuing card to score the risk that a given transaction is attempted without authorization. Issuing users can leverage these scores to determine whether to block or allow transactions attempted on cards issued for them.
Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
These rights may be subject to exceptions under applicable law.

Qualifications & exceptions

  • data related to activity conducted using cards issued through the Stripe Issuing program.
  • Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
  • These rights may be subject to exceptions under applicable law.
Also annotated in the same passage (8)

Inference & Profiling · Company practice

Business and representative details train models for fraud and loss risk

The training description covers Business User and Representative identifiers, birth dates, addresses, bank and device details, business industry and website content, service activity such as payments and disputes, past fraud actions, advanced fraud signals from site access, and signs that details are compromised, fabricated or associated with fraud. Data comes from the services, public sources and third parties to recognize business usage patterns associated with possible fraud or losses. The passage refers to “these models” without giving this bullet a distinct model name.

Supporting quotations

Users may pose a heightened risk of fraud and other losses to Stripe, Users, and other participants in the financial ecosystem.
We train these models using risk signals related to Business User and Representative details, such as names, email addresses, dates of birth, physical addresses, bank account information, and device details, business information, such as industry information and website content, patterns of activity on our Services, including payments, disputes, and past fraud actions, advanced fraud signals collected when a Business User or Representative accesses our sites, and signals indicating that Business User or Representative details may be compromised, fabricated, or associated with fraud.
We collect this data from our Services and publicly available and third-party sources. Training on such data allows our models to recognize usage patterns by Business Users that can be indicative of potential fraud and other behavior that may cause losses.

Inference & Profiling · Company practice

Smart Retries learns when to retry failed subscription payments

To increase authorization and revenue for payments Business Users, Smart Retries trains on past transactions associated with customer card details, names, emails, IP addresses and billing/shipping addresses. Features may include timing and outcomes, card address/BIN/type, device IP/user-agent, amount, subscription history/type and product description, plus third-party IP-derived location. It recommends when a failed subscription payment may best be retried.

Supporting quotations

We train artificial intelligence models to increase authorization rates and revenue realization for Business Users who use our payments products.
We train the Smart Retries models on data from past transactions on Stripe to identify the times at which transactions associated with a customer’s card details, name, email address, IP address, billing address, and shipping address have been successful.
This model may be trained on features indicating the time and outcome of past transactions, card features, such as address, bin, and card type, user device features, such as IP address and user agent, and transaction features, such as the amount, subscription type and history, and product description. We also use location based on IP address as calculated by third-party service providers.
Based on this information, Smart Retries recommends to users when may be the best time to make another attempt at processing a failed subscription payment.

Inference & Profiling · Company practice

Adaptive Acceptance predicts how to resubmit declined charges

Adaptive Acceptance decides whether to reattempt charges rejected by a network or issuer and automatically chooses protocol optimizations and authentication pathways. Training uses past card/customer/merchant authorizations and declines, merchant and charge amount, decline reason, and card BIN, issuer and expiry. Predictions estimate success at different times and under different protocols; the publisher uses them to decide submission methods that maximize its and its users’ profit. Where automated decisions have legal or similarly significant effects, or law otherwise requires, the publisher provides legally required notices, explanations and choices, subject to applicable legal exceptions.

Supporting quotations

We use these models to determine whether to reattempt charges that a card network or issuing bank rejected on the first attempt and to automatically select the optimal protocol optimization and authentication pathway for the transaction.
We train the models using data from past transactions on Stripe, including features related to the history of authorizations and declines we have observed for the card, customer, or merchant involved in the transaction, transaction features such as the merchant, amount of the charge, and the reason it was declined, and card features such as the bin, issuer, and expiry date.
Based on these features, the models calculate the probability that a charge will be successful if submitted at different times and according to different protocols. We use this probability of authorization to determine how to submit the charge to maximize profit for Stripe and its Users.
Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
These rights may be subject to exceptions under applicable law.

Qualifications & exceptions

  • Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
  • These rights may be subject to exceptions under applicable law.
Also annotated in the same passage (8)

Inference & Profiling · Company practice

EEA SEPA models predict failures and chargebacks, not standalone creditworthiness

For SEPA Direct Debit payments in the EEA, machine-learning models analyze transaction and payment signals to predict failure or chargeback likelihood, prevent financial loss and improve payment performance. They do not produce standalone creditworthiness assessments and are not the sole basis for lending decisions.

Supporting quotations

For SEPA Direct Debit payments in the European Economic Area, Stripe uses machine-learning models to predict the likelihood that a payment will fail or result in a chargeback. These models analyze transaction and payment signals to help Stripe and its Business Users prevent financial losses and improve payment performance. They do not produce a standalone assessment of an individual’s creditworthiness and are not used as the sole basis for a lending decision.

Qualifications & exceptions

  • are not used as the sole basis for a lending decision.

Inference & Profiling · Company practice

Identity models learn from verification images with improvement consent

Identity compares biometric features in selfies and photo IDs and looks for fraud indicators, such as obscured faces, modified documents or unfamiliar document formats. Its models are trained using images from verification subjects who consented to having their data used to improve Identity.

Supporting quotations

These models compare biometric features in the selfies with those in the documents and spot features common to fraudulent verification attempts, such as images where the subject’s face is obscured by a mask or the document has been modified or does not match a known format. We train Identity’s models using images from verification subjects who have consented to our using their data to improve Stripe Identity.

Qualifications & exceptions

  • verification subjects who have consented to our using their data to improve Stripe Identity.

Inference & Profiling · Company practice

Instant Bank Payments uses bank details for authorization and model training

Instant Bank Payments models evaluate risks of unauthorized bank-account use or insufficient funds. End Users who sign up agree to provide bank details such as ownership, transaction history and balances, both to decide authorization and to train models to recognize when banks are likely to reject future transactions through the service. Where automated decisions have legal or similarly significant effects, or law otherwise requires, the publisher provides legally required notices, explanations and choices, subject to applicable legal exceptions.

Supporting quotations

Instant Bank Payments, which uses artificial intelligence models to evaluate the risk that someone is attempting to misuse the service by conducting a transaction using a bank account they are not authorized to use or an account with insufficient funds.
End Users who sign up for Instant Bank Payments agree to provide us with details from their bank accounts, such as ownership information, transaction history, and balance details, to determine whether to authorize their transactions and train our models to recognize when banks are likely to reject future transactions attempted through the Instant Bank Payments Service.
Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
These rights may be subject to exceptions under applicable law.

Qualifications & exceptions

  • End Users who sign up for Instant Bank Payments agree to provide us with details from their bank accounts
  • Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
  • These rights may be subject to exceptions under applicable law.
Also annotated in the same passage (8)

Inference & Profiling · Company practice

Models identify Business Users who may benefit from additional services

Models may use platform activity and bank or financial information a Business User supplies to find similarities to users who benefited from products previously. The goal includes identifying candidates for additional services such as US Capital. Information can be personal data where the Business User is an individual; this passage does not promise qualification for a service.

Supporting quotations

We also train models to recognize Business Users that are good candidates to use additional Stripe services, such as Stripe Capital in the U.S.
We may train these models using information related to a Business User’s activity on the Stripe platform and, when the user provides them to us, bank account and other financial information.
The models are trained using such information so that they can recognize similarities between the current Business User and other Business Users who have benefitted from our products in the past. To the extent that Business Users are individuals, such data may constitute Personal Data.

Qualifications & exceptions

  • when the user provides them to us
  • To the extent that Business Users are individuals, such data may constitute Personal Data.

Legal Rights & Agreement Rules · Context

The Privacy Center places GDPR responsibilities on Business User controllers

The page says Business Users acting as controllers are responsible for End Customer data processed through the services. It states that businesses with EU or UK customers must comply with GDPR and/or its UK version regardless of business location, including ensuring a lawful processing basis and being transparent about data use. This reports the publisher’s guidance rather than independently determining a particular business’s legal obligations.

Supporting quotations

As a Stripe Business User and a data controller, the GDPR places responsibility on you in relation to the Personal Data that you process through Stripe services (i.e., your End Customers’ data). If you have customers anywhere in the EU / UK, you are required to comply with the GDPR (and/or the UK’s version of GDPR), no matter where your business is located. Fundamentally, you must ensure that you have a lawful basis for processing Personal Data and that you are transparent with your customers about how their data is used.

Qualifications & exceptions

  • If you have customers anywhere in the EU / UK
  • no matter where your business is located.

Legal Rights & Agreement Rules · Procedure

Business Users are directed to the separate DPA for processor terms

The page says controllers need certain contractual terms with processors and that Business Users enter into a DPA with the publisher to assist GDPR compliance. It encourages understanding both parties’ obligations and reading the linked DPA; those separate terms are not supplied by this passage.

Supporting quotations

Data controllers will need to have certain contractual terms in place with third parties who act as data processors on their behalf.
To assist Business Users with their compliance with the GDPR, Business Users enter into a Data Processing Agreement (“DPA”) with Stripe. Understanding both your obligations and Stripe’s role under the DPA is essential for operating within the GDPR framework. We encourage you to read our DPA to learn more.

Not stated here

  • The linked Data Processing Agreement is not supplied here; its detailed rights and obligations are not inferred.

Security & Safeguards · Company commitment

Sub-processors are contracted and vendors are security-reviewed before use

The publisher identifies and evaluates sub-processors through its vendor-management program. It contracts with each before sharing data, including monitoring and audit terms, and says all vendors pass security review and approval before their services are used. A separate page lists sub-processors, affiliates and common providers.

Supporting quotations

Stripe identifies, evaluates, and engages sub-processors through our vendor management program. We enter into a contract with each sub-processor prior to sharing data with the sub-processor, and each contract contains terms that provide for monitoring and audit. In addition, all vendors are vetted and approved through Stripe’s security review process before we begin using their services.

Qualifications & exceptions

  • prior to sharing data with the sub-processor
  • before we begin using their services.

Data Access & Collection · Company practice

Fraud and security data can come from users, financial parties and third parties

For fraud prevention and security, information may be collected from Business Users, End Customers, End Users, financial parties and sometimes third parties. Examples include transaction amounts, shipping addresses and dates, plus device and activity signals used to identify bad actors or bots.

Supporting quotations

To prevent fraud and strengthen our security, we may collect information from Business Users, End Customers, End Users, financial parties, and in some cases third parties. For example, we collect and analyze information that helps us identify bad actors and bots, including both transactional data (such as amount, customer shipping address, date, and so on) and advanced fraud detection signals (device and activity signals).

Qualifications & exceptions

  • To prevent fraud and strengthen our security

Data Access & Collection · Company practice

Risk services may collect registration and login behavior before payment

On platforms that enable the publisher’s risk services, registration or login may produce device, browser, IP, activity and interaction signals. These detect fraudulent registrations, account takeover, bots, multi-account abuse and other potentially harmful activity before payment. The implementing Business User or platform must provide notices and obtain permissions required by applicable law.

Supporting quotations

Stripe may also collect device and behavioral signals when an individual registers for or logs into an account on a platform that has enabled Stripe’s risk services. These signals may include information about the individual’s device, browser, IP address, activity, and interactions with the registration or login flow.
Stripe uses these signals to detect fraudulent registrations, account takeovers, bots, multi-account abuse, and other potentially harmful activity before a payment is initiated. The Business User or platform that implements these services is responsible for providing any notices and obtaining any permissions required by applicable law.

Qualifications & exceptions

  • on a platform that has enabled Stripe’s risk services.
  • The Business User or platform that implements these services is responsible for providing any notices and obtaining any permissions required by applicable law.

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)

Security & Safeguards · Company practice

3D Secure compares transaction details with information already on file

Issuers and payment-method providers may use shared information for 3D Secure authentication, including branded schemes such as Visa Secure, Mastercard Identity Check and American Express SafeKey. It compares information supplied at transaction time with existing issuer/provider records to reduce unauthorized card use. The page says 3DS is frequently used for European strong-authentication requirements and similar rules in the UK, India and Australia. When serving a bank through Issuing, the publisher and providers may use card numbers, contact, billing/shipping, device and transaction-history data to facilitate 3DS.

Supporting quotations

Issuers and payment method providers may use the information we share to verify you through a process called 3D Secure Authentication or 3DS.
It works by comparing the information you provide at the time of the transaction with the information that your issuer and payment method provider already have on file, to help reduce the risk that someone else may use your card for an unauthorized transaction.
3DS is frequently used in Europe in support of Strong Customer Authentication requirements under the Payment Services Directive (PSD2) and to comply with similar regulations in other countries including the UK, India and Australia. When we act as a service provider to your bank under our Stripe Issuing program we and our service providers may use Personal Data such as your card number, contact information, payment-specific data, like your billing and shipping address, and contextual data such as your device ID and transaction history to facilitate 3DS authentication.

Qualifications & exceptions

  • When we act as a service provider to your bank under our Stripe Issuing program
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)

Retention & Deletion · Restriction or exception

Dispute recipients generally control and retain received evidence independently

Networks and other payment-method providers generally act as independent controllers of dispute evidence, retaining and processing it under their own policies, applicable law and network rules. For a Business User purchase, you can ask that business about what it submitted or instructed the publisher to submit. The publisher may be unable to change or delete evidence already sent to networks or issuers when law or network rules require retention.

Supporting quotations

Card networks and other payment-method providers generally act as independent data controllers for the evidence they receive. They retain and process that information in accordance with their own privacy policies, applicable law, and payment-network rules.
If the dispute relates to a purchase from a Business User, you may consider contacting that Business User for information about the evidence it submitted or instructed Stripe to submit. 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

  • where retention is required under applicable law or network rules.
Also annotated in the same passage (1)

Security & Safeguards · Company practice

Several products and internal models use personal data against fraud

Radar, Identity and Merchant Risk Tooling use personal data to help Business Users detect and prevent fraud. The publisher also uses internal risk models and product features such as Issuing’s 3D Secure to prevent fraudulent use of its services.

Supporting quotations

The Stripe products that use Personal Data to enable Stripe’s Business Users to detect and prevent fraud include Stripe Radar, Stripe Identity, and Stripe Merchant Risk Tooling. Stripe also employs internal risk models and other product features, such as 3D Secure incorporated into Stripe’s Issuing product, to prevent its products and Services from being used for fraudulent activity.

Inference & Profiling · Company practice

Radar risk outputs may inform whether activity is allowed, blocked or reviewed

Radar scores estimate whether a payment method is offered by someone unauthorized, rather than rating the person’s character or creditworthiness. Depending on the purchased service, Business Users may receive scores and set transaction rules. Outputs can include scores, indicators or recommendations, which the publisher, Business Users, financial partners or other authorized recipients may combine with other information to allow, block, authenticate or review activity. Except where expressly stated otherwise, fraud-risk scores are not character or creditworthiness assessments. Where automated decisions have legal or similarly significant effects, or law otherwise requires, the publisher provides legally required notices, explanations and choices, subject to applicable legal exceptions.

Supporting quotations

These scores are designed to identify fraudulent transactions, they do not rate the character or creditworthiness of the individuals involved in a particular transaction.
Based on the service selected by the Business User, Stripe may provide the Radar scores to its Business Users to help them to combat fraud and provide a mechanism for them to set rules to better manage transactions based on Radar scores and other indicators of fraud.
The outputs of these models may include scores, risk indicators, or recommendations. Depending on the service, Stripe, a Business User, a Financial Partner, or another authorized recipient may use those outputs together with other information when deciding whether to allow, block, authenticate, or review an activity. Except where expressly stated otherwise, a fraud-risk score is not an assessment of an individual’s character or creditworthiness.
Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
These rights may be subject to exceptions under applicable law.

Qualifications & exceptions

  • Based on the service selected by the Business User
  • Except where expressly stated otherwise, a fraud-risk score is not an assessment of an individual’s character or creditworthiness.
  • Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
  • These rights may be subject to exceptions under applicable law.

Not stated here

  • The linked locale-specific Radar page is not independently supplied; this card relies on the saved source’s explicit wording rather than additional terms at that link.

Cross-references

Also annotated in the same passage (8)

Use & Processing · Company practice

Identity can compare biometrics and check data against outside databases

Identity helps Business Users check whether someone is who they claim to be. It compares selfie biometric identifiers against government ID and can validate entered names, birth dates and government ID numbers against government and third-party databases to check consistency with the ID number.

Supporting quotations

Identity compares biometric identifiers in a selfie against government issued ID. Identity can also validate Personal Data, such as name, date of birth, and government ID number, that an End Customer types into a web form against government and third-party databases to determine if the identity presented matches the government issued ID number.

Security & Safeguards · Company practice

Internal fraud models may reject payment methods and block suspicious transactions

The publisher uses Radar scores internally to accept or reject payment methods offered to products including Link, Frontier, Crypto Onramp and Bill Pay. Its internal models also use aggregated cardholder features to recognize many transactions likely coming from one person testing or cashing out stolen payment methods. It says it will block transactions when it recognizes that activity to prevent harm. Where automated decisions have legal or similarly significant effects, or law otherwise requires, the publisher provides legally required notices, explanations and choices, subject to applicable legal exceptions.

Supporting quotations

For instance, Stripe uses Radar scores internally to determine whether a payment method offered to Stripe products such as Link, Frontier, Crypto Onramp, and Bill Pay should be accepted or rejected as likely fraudulent. Stripe’s internal risk models also use aggregated cardholder features to recognize when a large number of transactions are likely being conducted by the same individual for purposes of testing or cashing out stolen payment methods. Where Stripe recognizes such activity, it will block transactions to prevent harm to itself, its users, and others.
Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
These rights may be subject to exceptions under applicable law.

Qualifications & exceptions

  • Where Stripe recognizes such activity, it will block transactions to prevent harm to itself, its users, and others.
  • Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
  • These rights may be subject to exceptions under applicable law.
Also annotated in the same passage (8)

Inference & Profiling · Company practice

Merchant Risk Tooling supplies Connect platforms with reasoned fraud-risk scores

Merchant Risk Tooling applies internal models to Connected Accounts and gives platform fraud teams reasoned scores of indicators consistent with fraudulent use. The scores supplement platform due diligence and do not rate individuals’ character or creditworthiness. Inputs include payment transactions, Representative IP/physical/email addresses, business website content and other business information.

Supporting quotations

Stripe Merchant Risk Tooling leverages Stripe’s internal risk models to help Stripe Connect Platforms identify indicators of potential fraud associated with their Connected Accounts.
Merchant Risk Tooling produces reasoned scores that identify to Platform’s internal fraud teams when there are indicators consistent with a Connected Account attempting to use the Platform’s services (and Stripe) for fraudulent purposes. These scores are designed to supplement the Platforms’ due diligence related to their Connected Accounts and their business activities. They do not score the character or creditworthiness of the individuals involved in the Connected Accounts’ operations.
The data factored into Merchant Risk Tooling includes payments Transaction Data, business Representative details (such as IP address, physical address, and e-mail address) business website content, and other information regarding the businesses Business Users operate on Stripe.

Qualifications & exceptions

  • These scores are designed to supplement the Platforms’ due diligence related to their Connected Accounts and their business activities.
  • They do not score the character or creditworthiness of the individuals involved in the Connected Accounts’ operations.

Security & Safeguards · Company practice

Issuing authentication uses and stores card data and transaction history

Issuing’s 3D Secure feature requires one or more authentication factors before an online transaction and is legally required in certain jurisdictions. The publisher and its providers use and store cardholder PANs, contact information and transaction history for one-time passcodes and checks based on past transactions. When acting as the bank’s Issuing service provider, this may also involve billing/shipping addresses and device ID.

Supporting quotations

This feature is required by law in certain jurisdictions and requires cardholders to authenticate using one or more factors before they can complete an online transaction. Stripe and its service providers use and store Personal Data including cardholder PANs, contact information, and transaction history to authenticate cardholders using one time passcodes and knowledge of past transactions.
When we act as a service provider to your bank under our Stripe Issuing program we and our service providers may use Personal Data such as your card number, contact information, payment-specific data, like your billing and shipping address, and contextual data such as your device ID and transaction history to facilitate 3DS authentication.

Qualifications & exceptions

  • This feature is required by law in certain jurisdictions
  • When we act as a service provider to your bank under our Stripe Issuing program
Also annotated in the same passage (1)

Linking & Identification · Company practice

Account details may be filled from other accounts or outside sources

For fraud detection and financial compliance obligations arising from partners or regulation, missing account fields such as address, phone, SSN, birth date, employer ID or website may be filled using another account or third-party data. Business Users are shown the associated information in their dashboard and can correct it there. For Custom connected accounts, the specific route is to contact the platform or business that created the payment account.

Supporting quotations

Stripe may collect additional information about your account to allow Stripe and its Financial Partners to detect fraud and/or fulfill financial compliance requirements.
Examples of missing data fields include your address, phone number, social security number, date of birth, employer identification number, or website URL. Stripe may be able to fill in some of this information by leveraging data we have collected from one of your other Stripe accounts or by obtaining data from a third party. We will show Business Users the information that we are associating with their account on your dashboard, and Business Users may update or correct that information via your dashboard.
You may view the information that we are associating with your account and update or correct that information by contacting the platform or business that created your Stripe payment account.

Qualifications & exceptions

  • to allow Stripe and its Financial Partners to detect fraud and/or fulfill financial compliance requirements.
  • Business Users may update or correct that information via your dashboard.
  • by contacting the platform or business that created your Stripe payment account.

Not stated here

  • The linked Privacy Policy is not supplied here; this card does not describe its additional terms.
Also annotated in the same passage (1)

Data Access & Collection · Company practice

The publisher does not collect device GPS data but may derive location from IP addresses

Although devices can collect GPS-based precise location, the publisher says it does not collect GPS data from devices or browsers. Depending on services and implementation, cookies and similar technologies collect information including IP addresses, and site visits collect IP addresses. End Customer IP-derived location, including approximate latitude/longitude, may be used to detect fraudulent transactions.

Supporting quotations

Devices such as mobile phones or computers may collect precise location data using GPS technology. Stripe does not collect GPS data from devices and browsers.
Depending on the Services you use and the Business Users’ implementation of our Business Services, we will collect information (including IP addresses) through cookies and similar technology. We will collect your IP address when you visit our Sites.
Stripe may use location information, including approximate latitude and longitude, derived from End Customers IP addresses to detect potentially fraudulent transactions.

Qualifications & exceptions

  • Depending on the Services you use and the Business Users’ implementation of our Business Services
  • derived from End Customers IP addresses to detect potentially fraudulent transactions.

Not stated here

  • The separate Cookie Policy is not supplied here; its full rules and choices cannot be determined from this passage.
Also annotated in the same passage (2)

Data Access & Collection · Company practice

Outside providers supply approximate visitor location for marketing

Third parties such as MaxMind provide approximate country, city or state information to help locate website visitors for marketing, for example invitations to local events. This is distinct from the statement that device GPS data is not collected.

Supporting quotations

We also receive approximate location information (such as country, city or state) from third party providers such as MaxMind to help us determine the approximate location of Visitors to our website for marketing purposes (for example, inviting you to local Stripe events).

Qualifications & exceptions

  • approximate location information (such as country, city or state)

Not stated here

  • MaxMind’s linked privacy-policy text is not supplied here, so its independent practices are not described.

Use & Processing · Context

A sub-processor acts on the publisher’s behalf when it is a processor

The page calls providers sub-processors when the publisher itself acts as processor for Business User or End User personal data. They have or potentially will have access to, or process, data on its behalf. A separate list identifies these providers; this does not mean every recipient described elsewhere is a sub-processor.

Supporting quotations

When we work with service providers in our capacity as a data processor for our Business Users’ and End Users’ Personal Data, the GDPR calls these third-party service providers a sub-processor. Sub-processors are service providers who have or potentially will have access to or process Personal Data on behalf of Stripe where Stripe acts as a data processor for the Business User.

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

Account & Service Control · Company practice

Stored card details may be updated through issuers or card networks

If you supply payment-method details to store or use for a transaction, the publisher may update changed card information, including through your issuer or network, to keep transactions working. If you do not want updated details shared with the publisher, contact your issuing bank.

Supporting quotations

Please note that if you provide us with your payment method information (e.g., a card number and expiration date) to store on file or otherwise in connection with a transaction, Stripe may update your card information if your information has changed or been updated to ensure your transactions go through smoothly, including by working with your card issuer or payment card network. If you would prefer to not have your updated payment method details shared with us, please reach out to your card issuing bank.

Qualifications & exceptions

  • if your information has changed or been updated
  • If you would prefer to not have your updated payment method details shared with us, please reach out to your card issuing bank.

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)

Data Access & Collection · Company practice

Financial Connections collects bank details according to consent and permissions

With consent, Financial Connections links a financial account to a Business User’s product or service. Depending on permissions and the requested service, collection may include account/routing numbers, type and ownership; current/available balances; and transaction amounts, dates, merchant names and categories. In some cases the publisher or provider also processes connection credentials.

Supporting quotations

With your consent, Financial Connections allows you to link a financial account to a Business User’s product or service. Depending on the permissions you grant and the service you request, Stripe may collect account information such as your account number, routing number, account type, and ownership information; current and available balances; and transaction history, including transaction amounts, dates, merchant names, and categories. In some cases, Stripe or its service provider may also process credentials used to connect to your financial institution.

Qualifications & exceptions

  • Depending on the permissions you grant and the service you request
  • In some cases, Stripe or its service provider may also process credentials used to connect to your financial institution.

Cross-references

Use & Processing · Company practice

Linked-account data supports the requested service and permitted additional uses

Financial Connections data is used for the requested service, such as bank payments, ownership verification, predicting payment success or supporting a lending decision. Permitted data may also support fraud prevention, security and relevant service improvements, as described in the Privacy Policy and displayed permissions. Own marketing use requires any separate consent required by applicable law; this is not an unconditional ban on marketing use.

Supporting quotations

Stripe uses this information to provide the service you requested, such as setting up a bank payment, verifying account ownership, assessing whether a bank payment is likely to succeed, or supporting a lending decision. Stripe may also use permitted Financial Connections data for fraud prevention, security, and improving relevant Stripe services, as described in our Privacy Policy and in the permissions presented to you.
Stripe does not use your linked financial-account information for Stripe’s own marketing without obtaining any separate consent required by applicable law.

Qualifications & exceptions

  • as described in our Privacy Policy and in the permissions presented to you.
  • Stripe does not use your linked financial-account information for Stripe’s own marketing without obtaining any separate consent required by applicable law.

Not stated here

  • The separate Privacy Policy and individual permission screens are not supplied; this card cannot describe their additional limits.
Also annotated in the same passage (1)

Account & Service Control · User right or choice

Disconnecting a financial account stops collection but may leave retained data

You can withdraw consent and ask the publisher to stop collecting from a linked account by disconnecting it. Disconnection does not necessarily require deletion of data needed to comply with law, prevent fraud or complete a service already requested. End Customers are directed to linked support topics for details about access, security, credentials, correction, disconnection and deletion.

Supporting quotations

You may withdraw your consent and ask Stripe to stop collecting information from the linked account by disconnecting the account. Disconnecting an account does not necessarily require Stripe to delete information that it must retain to comply with law, prevent fraud, or complete a service already requested.
If you are an End Customer who has been asked to link your financial account using Stripe, please visit the support webpage here to learn more about our privacy practices.

Qualifications & exceptions

  • Disconnecting an account does not necessarily require Stripe to delete information that it must retain to comply with law, prevent fraud, or complete a service already requested.

Not stated here

  • The linked support pages are not supplied here; their detailed procedures and additional practices remain unknown.

Cross-references

Also annotated in the same passage (1)

Account & Service Control · User right or choice

Business Users can disable payment methods that may be enabled by default

Available methods include cards, mobile/online services such as WeChat Pay and Alipay, and BNPL such as Klarna and Afterpay. Some are enabled by default at onboarding; for eligible users, more may be enabled later after notification. The dashboard lets Business Users enable or disable methods at any time. Enabling a method can involve sharing business and Representative data with its provider; disabling is not described here as deleting data already shared.

Supporting quotations

Certain payment methods are enabled by default when you onboard with Stripe. After onboarding, for eligible users, Stripe may enable additional payment methods after notifying you. Your Stripe dashboard allows you to enable or disable payment methods at any time.
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.

Qualifications & exceptions

  • After onboarding, for eligible users, Stripe may enable additional payment methods after notifying you.
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)

Use & Processing · Company practice

Representative contacts may be used for authentication, support and unpaid balances

Representative contact information may be processed to authenticate, provide service updates or support, and address Business User account issues such as unpaid balances. These are examples rather than an exhaustive list.

Supporting quotations

As part of providing our Services we may process Representative contact information for purposes including authentication, providing updates regarding the Services, providing support, and to address issues related to Business Users’ Stripe accounts, such as unpaid balances.

Qualifications & exceptions

  • As part of providing our Services

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.

Inference & Profiling · Company practice

Radar combines data across services to assess potentially unauthorized payments

Radar uses machine learning and other techniques to detect potential transaction fraud, drawing on data across services. End Customer inputs include payment transactions, advanced fraud-detection data, Bank Connections data, IP addresses and physical addresses. These assess whether the offered payment method is likely unauthorized.

Supporting quotations

To do this, Radar leverages data collected across our Services.
Radar uses data collected about the End Customer from various sources, including payments Transaction Data, advanced fraud detection data, Bank Connections data, IP address, and physical address information. Radar uses this data to assess whether the payment method offered by the End Customer is likely unauthorized.

Not stated here

  • The linked advanced-fraud documentation is not supplied here; no additional collection details are inferred from it.

Inference & Profiling · Company practice

Radar scores can drive automated allow, block or review rules

Radar’s AI score assesses transaction-fraud likelihood. Business Users can use it for automated rules to allow, block or flag transactions for review, and may use Radar as one of several inputs in fraud decisions. This passage describes transaction risk, not a standalone judgment of an individual. Where automated decisions have legal or similarly significant effects, or law otherwise requires, the publisher provides legally required notices, explanations and choices, subject to applicable legal exceptions.

Supporting quotations

Radar’s artificial intelligence model produces transaction “scores” indicating the model’s assessment of the likelihood that a transaction is fraudulent. Business Users can leverage this score and use it to implement automated rules to determine whether to allow, block, or flag transactions for additional review. Business Users can use Radar as one of multiple inputs in making decisions with respect to the potential for fraud in a transaction.
Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
These rights may be subject to exceptions under applicable law.

Qualifications & exceptions

  • Business Users can use Radar as one of multiple inputs in making decisions with respect to the potential for fraud in a transaction.
  • Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.
  • These rights may be subject to exceptions under applicable law.

Cross-references

Also annotated in the same passage (7)

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.

Legal Rights & Agreement Rules · Restriction or exception

Business Users must supply notices and obtain necessary rights and consents

Under the publisher’s agreements, Business Users must provide necessary notices and obtain necessary End Customer rights and consents for lawful collection, use, retention and disclosure. As controllers and/or customer-facing entities, they are responsible for their privacy notices and cookie banners.

Supporting quotations

Under the terms of our agreements, Business Users are required to provide all necessary notices and obtain all necessary rights and consents from their End Customers to enable Stripe to lawfully collect, use, retain and disclose the Personal Data as part of the Stripe Services. Business Users, as data controllers and/or the End Customer facing entity, are responsible for the contents of their privacy notice and cookie banner.

Qualifications & exceptions

  • as part of the Stripe Services.

Legal Rights & Agreement Rules · Context

The suggested merchant notice is illustrative, not legal advice

An example notice describes payments, analytics and other services; cookie-related collection of transaction/device/browser data; and uses for operating and improving services, fraud prevention/detection, authentication, performance analytics and user experience. The publisher expressly calls it illustrative, not legal advice, and recommends speaking to an advisor about legal compliance. It is not a substitute for the merchant’s own disclosure responsibilities.

Supporting quotations

We use Stripe for payments, analytics, and other business services. Stripe may collect personal data including via cookies and similar technologies. The personal data Stripe collects may include transactional data and identifying information about devices and browsers that connect to its services. Stripe uses this information to operate and improve the services it provides to us, including for fraud and prevention and detection, authentication, analytics related to the performance of its services, and to enhance and customize the user experience.
Please be aware that the disclosure above is for illustrative purposes only and is not legal advice. Please talk to your legal advisor to understand how to comply with your obligations under applicable law.

Legal Rights & Agreement Rules · Procedure

Business Users are reminded to review actual cookies and update banners

The publisher points to its Cookie Policy for uses and Cookies Settings Dashboard for its list of cookies. It reminds Business Users to review cookies actually placed on their websites and update their banners accordingly; the paragraph does not supply the linked policy or a full cookie inventory.

Supporting quotations

To comply with our transparency obligations, we explain how our cookies are used in our Cookie Policy and our Cookies Settings Dashboard sets out our list of cookies. We remind our Business Users to review the cookies placed on their website and to update their cookie banners accordingly.

Not stated here

  • The Cookie Policy and settings inventory are linked but not supplied here; their full contents are not inferred.

Data Access & Collection · Company practice

German Business User identity checks may use infoscore information

Through service providers, the publisher may use information from infoscore Consumer Data GmbH to verify German Business Users’ identities. The linked provider information is separate.

Supporting quotations

Stripe, through its service providers, may use information from infoscore Consumer Data GmbH to verify the identity of Stripe Business Users in Germany.

Not stated here

  • The linked infoscore information is not supplied; its independent processing terms remain unknown.

Legal Rights & Agreement Rules · Context

Third-party data notices direct recipients to the Privacy Policy

If notified that the publisher obtained your data from a third party, this section says the Privacy Policy governs processing and describes controller/DPO contacts, purposes and legal bases including lawful prospecting/direct marketing, recipients, international-transfer safeguards and how to obtain them, retention periods or criteria, applicable access/correction/deletion/restriction/objection/portability rights and supervisory-authority complaints. These are the section’s descriptions of a separate policy, not independently verified contents or a fixed retention period.

Supporting quotations

If you have been notified by Stripe that we obtained your data from a third party, the following applies:
Your Personal Data will be processed as set out in Stripe’s Privacy Policy, which in accordance with Art. 14 GDPR describes:
the identity and the contact details of Stripe;
the contact details of Stripe’s Data Protection Officer;
the purposes of the processing for which the Personal Data are intended as well as the legal basis for the processing, which includes prospecting and direct marketing, as permitted under applicable law;
that Stripe intends to transfer Personal Data to a recipient in a third country and a reference to the appropriate or suitable safeguards and the means to obtain a copy of them or where they have been made available
the period for which the Personal Data will be stored and/or the criteria used to determine that period;
the existence of the right to request from Stripe access to and rectification or erasure of Personal Data or restriction of processing concerning the data subject and to object to processing as well as the right to data portability or any other applicable rights under data protection laws
the right to lodge a complaint with a supervisory authority.

Qualifications & exceptions

  • If you have been notified by Stripe that we obtained your data from a third party
  • as permitted under applicable law;

Not stated here

  • The linked Privacy Policy text is not supplied; its detailed rights, recipients, safeguards and retention rules are not established by this summary.

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.

Data Access & Collection · Company practice

Business prospecting data includes detailed professional and company information

The third-party-data notice lists full names, business emails, direct phones, professional social profiles, business addresses, company metadata such as name/registration/size/domain, roles and titles, industry and professional history. Sources include Cognism, ZoomInfo, Clearbit (API Hub), Crunchbase, Clay Labs, PitchBook, infoAnalytica, People Data Labs, Apollo.ai GmbH, Dealroom.co, corporate registers and public online sources. Those providers are independent controllers; contact them directly for removal from their databases.

Supporting quotations

Categories of Personal Data Obtained: We process granular categories of Personal Data, including full name, business email address, direct phone number, professional social media profiles, business physical address, company metadata (such as company name, registration number, size, and domain), professional role and title, industry sector, and professional history.
Data Sources: We collect Personal Data from third-party providers, including Cognism Limited, ZoomInfo Technologies Inc., API Hub, Inc. (Clearbit), Crunchbase Inc., Clay Labs Inc., PitchBook Data, Inc., infoAnalytica, Inc., People Data Labs, Inc., Apollo.ai GmbH, and Dealroom.co, as well as publicly available corporate registers and online sources. These third parties operate as independent data controllers. If you wish to be removed from their databases, please contact them directly.

Qualifications & exceptions

  • These third parties operate as independent data controllers. If you wish to be removed from their databases, please contact them directly.

Legal Rights & Agreement Rules · Context

The third-party-data notice relies on legitimate interests and describes objection rights

For the processing covered by this notice, the publisher cites Article 6(1)(f) GDPR legitimate interests: research/analysis, prospecting/sales, and marketing/advertising. The accompanying rights statement says applicable rights may include objecting at any time to legitimate-interest processing including direct marketing, via the Privacy Portal or DPO. This states the publisher’s asserted basis, not a conclusion that every use is lawful.

Supporting quotations

Legal Basis for Processing: All processing of data obtained from third parties is based on Stripe’s legitimate interests pursuant to Art. 6(1)(f) GDPR. These legitimate interests include:
market research and analysis;
prospecting and selling; and
marketing and advertising.
Your Rights as a Data Subject: You may have explicit rights under applicable laws regarding your Personal Data, including the right to request access, rectification, restriction of processing, data portability, erasure (right to be forgotten), and the right to object at any time to processing based on legitimate interests (including direct marketing).

Qualifications & exceptions

  • You may have explicit rights under applicable laws regarding your Personal Data
Also annotated in the same passage (2)

Use & Processing · Company practice

Prospect enrichment can include current payment and billing providers

For potential Business Users and their representatives, enrichment and public sources may supply company size, industry, growth indicators and existing payment-service or billing providers. The publisher uses this to understand business needs, maintain accurate records, tailor outreach and market services where law permits. Applicable objection rights remain available through the Privacy Portal or DPO.

Supporting quotations

Where you are a potential Business User or a representative of a potential Business User, Stripe may also obtain information about you and your organization from enrichment providers and publicly available sources. This may include firmographic information such as company size, industry, growth indicators, and information about the organization’s existing payment-service or billing providers.
Stripe uses this information to understand an organization’s potential business needs, maintain accurate business records, tailor outreach, and market Stripe services where permitted by applicable law.
To exercise any of these rights, please submit a request through our Privacy Portal or contact our Data Protection Officer directly.

Qualifications & exceptions

  • Where you are a potential Business User or a representative of a potential Business User
  • where permitted by applicable law.
Also annotated in the same passage (2)

Legal Rights & Agreement Rules · User right or choice

Third-party data subjects may request rights through the portal or DPO

For the third-party-data notice, applicable rights may include access, rectification, processing restriction, portability, erasure and objection at any time to legitimate-interest processing, including direct marketing. Requests go through the Privacy Portal or directly to the Data Protection Officer. Rights depend on applicable law.

Supporting quotations

Your Rights as a Data Subject: You may have explicit rights under applicable laws regarding your Personal Data, including the right to request access, rectification, restriction of processing, data portability, erasure (right to be forgotten), and the right to object at any time to processing based on legitimate interests (including direct marketing). To exercise any of these rights, please submit a request through our Privacy Portal or contact our Data Protection Officer directly.

Qualifications & exceptions

  • You may have explicit rights under applicable laws regarding your Personal Data
Also annotated in the same passage (2)

Data Access & Collection · Company practice

Calls may be recorded or transcribed, with notice and a qualified choice

Voice/video calls may be recorded or transcribed, including through Zoom, Salesloft or AI transcription tools. Recording is disclosed at the start; unless recording is legally required, the publisher asks for consent and/or offers a chance to decline. Recordings serve purposes stated at the start, typically quality and training. Applicable rights are available; a requested copy may be redacted audio or a redacted transcript where appropriate and legally permitted.

Supporting quotations

In some situations, we may record and/or transcribe voice or video calls we have with you. At the start of the call, we disclose the fact that a call is being recorded and, unless we are legally required to record the call, will ask for your consent to record the call and/or offer you the option to decline the call being recorded. We may use third-party systems to record and/or transcribe calls, including Zoom and Salesloft. In some cases, transcripts are generated by AI tools.
The call recordings will be processed for the purposes stated at the start of the call, typically for quality and training purposes, and in accordance with Stripe’s Privacy Policy.
In the event that you request a copy of the recording, Stripe may provide you with a redacted copy of the recording, or a (redacted) transcript of the recording, where appropriate, and as permitted under applicable law.

Qualifications & exceptions

  • unless we are legally required to record the call
  • for the purposes stated at the start of the call
  • where appropriate, and as permitted under applicable law.

Not stated here

  • The linked Privacy Policy is not supplied here; its detailed request procedures are not described.
Also annotated in the same passage (1)

Retention & Deletion · Company practice

Recording retention is normally one year, with five-year and legal extensions

Call recordings are normally held for up to one year. Support calls are normally kept for five years because the publisher says it has a legal obligation, and collection-related recordings are also kept five years. Recordings are then deleted unless a valid legal ground supports longer retention. Transcripts may remain for a further limited period for training, quality and operations; no fixed additional transcript period is given.

Supporting quotations

We normally retain call recordings for up to 1 year. We may retain transcripts for a further limited period for training, quality and operational purposes.
User support related phone calls are normally retained for 5 years as Stripe is under a legal obligation to keep this data for 5 years. Collection related call recordings are also kept for 5 years.
After this, call recordings will be deleted, unless we have a valid legal ground to keep the call recordings for a longer period of time.

Qualifications & exceptions

  • We may retain transcripts for a further limited period for training, quality and operational purposes.
  • unless we have a valid legal ground to keep the call recordings for a longer period of time.

Use & Processing · Company practice

Automated and AI communications may support service, sales and prospect qualification

With consent where required, automated dialing and AI voice, transcription, chat and email tools may communicate with current or prospective Business Users and Representatives. Purposes include support, answers, account/service communications, lawful sales/marketing, prospect qualification and improving communication efficiency and relevance.

Supporting quotations

Where required with your consent, Stripe may use automated dialing systems and AI technologies to communicate with existing or prospective Business Users and their Representatives. These technologies may include AI-powered voice agents and automated transcription, chat, and email tools.
Stripe may use these technologies for purposes including:
providing operational and customer support;
responding to questions and requests;
communicating about Stripe accounts and Services;
sales and marketing, where permitted by applicable law;
identifying and qualifying prospective Business Users; and
improving the efficiency and relevance of Stripe’s communications.

Qualifications & exceptions

  • Where required with your consent
  • where permitted by applicable law;

Inference & Profiling · Company practice

AI interactions may produce data used for model training and evaluation

Automated/AI interactions may collect contacts, interaction contents, recordings, transcripts and technical or engagement information. Where law permits, recordings and transcripts may be used for staff training, quality assurance, research, operational improvements and training, testing, evaluating and improving AI/ML models. Notice is provided for recorded calls or as legally required. At the start prompt you can opt out of recording, though the conversation may need to move to another channel; the general call section excepts legally required recording from its consent/decline offer.

Supporting quotations

When you interact with an automated or AI-powered communication tool, Stripe may collect and process your contact information, the contents of the interaction, and associated recordings, transcripts, and technical or engagement information.
Stripe may use recordings and transcripts generated through these interactions for staff training, quality assurance, research, operational improvement, and to train, test, evaluate, and improve artificial intelligence and machine-learning models, where permitted by applicable law.
Stripe will provide notice where a call is recorded or where otherwise required by applicable law. If you do not want a call to be recorded, you may opt out when prompted at the beginning of the call. Depending on the reason for the call, opting out of recording may require the conversation to continue through another communication channel.
unless we are legally required to record the call, will ask for your consent to record the call and/or offer you the option to decline the call being recorded.

Qualifications & exceptions

  • where permitted by applicable law.
  • Depending on the reason for the call, opting out of recording may require the conversation to continue through another communication channel.
  • unless we are legally required to record the call
Also annotated in the same passage (1)

Data Access & Collection · Company practice

Phone verification may use carrier account and device data

Identity checks may support legal compliance, fraud prevention or Business Users you transact with, including whether your phone matches other supplied details. Third-party providers may assist. If available, your carrier may disclose account/device information to the publisher or its providers during the business relationship to identify you or your device, prevent fraud and for uses described in the separate Privacy Policy.

Supporting quotations

One of the data points we may consider for these purposes is whether your phone number is associated with the other information you have provided while seeking services from us or our Business Users.
We may rely on third-party services providers to assist us in performing such verification checks. In particular, your wireless carrier may disclose information about your account and your wireless device, if available, to Stripe or our service providers for the duration of your business relationship, to help us identify you or your wireless device, to prevent fraud, and as otherwise described in our Privacy Policy.

Qualifications & exceptions

  • if available
  • for the duration of your business relationship

Not stated here

  • The separate Privacy Policy is not supplied; its additional carrier-data uses cannot be inferred.

Use & Processing · Company practice

Link co-marketing uses transaction information without sharing it with the featured businesses

For Link accounts, the publisher may review transactions to identify businesses used and potentially useful services. Where law permits, email, device and transaction information may support its marketing or co-marketing about using services with businesses you interact with. It says it does not share transaction or other personal data with those businesses to facilitate these marketing activities; that limit does not cover all unrelated payment or fraud disclosures.

Supporting quotations

If you have a Link account, Stripe may review your Link Transaction Data to determine which businesses you transact with and which additional services you may benefit from. We may also, where permitted by law, use your Personal Data (such as your email address, device information, and transaction history) to send you marketing information about our Services or co-marketing communications about how you can use our Services with Business Users you transact or interact with. We do not share your Transaction Data or other Personal Data with these Business Users to facilitate these marketing activities.

Qualifications & exceptions

  • where permitted by law
  • We do not share your Transaction Data or other Personal Data with these Business Users to facilitate these marketing activities.

Legal Rights & Agreement Rules · Context

The CCPA table reports collection and business-purpose disclosures over twelve months

This table describes categories collected and used in the last twelve months and says data was also disclosed for business purposes in the preceding twelve months. Its recipient cells describe possible disclosures subject to applicable law, not proof that every person’s data went to every named recipient.

Supporting quotations

Below are the categories of data we collect and how that information is used in the last 12 months. We also disclosed this data for a business purpose within the preceding 12 months.

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)

Use & Processing · Restriction or exception

Sensitive-data processing is described with a California purpose limit

The publisher says it processes sensitive personal information only for purposes specified in section 7027(m) of the CCPA regulations, or without the purpose of inferring consumer characteristics. This preserves the source’s alternative wording: it does not say that all inference is prohibited or supply the cited regulation’s full permitted-purpose list.

Supporting quotations

Stripe only processes sensitive personal information for the purposes specified in section 7027(m) of the California Consumer Privacy Act Regulations, or without the purpose of inferring characteristics about a consumer.

Qualifications & exceptions

  • or without the purpose of inferring characteristics about a consumer.

Not stated here

  • The cited California regulation is not supplied; its full list of specified purposes is not inferred.
Also annotated in the same passage (3)

Use & Processing · Company practice

Sensitive ID documents support identity checks, security, services and compliance

The sensitive-data table includes driver’s licenses, passports and social-security information, including underlying sensitive attributes such as racial or ethnic origin in an ID. Listed uses are identity verification, fraud/security, services and legal obligations, subject to the section’s specified-purpose or no-characteristic-inference limit.

Supporting quotations

Identification documents, including driver’s license, passport, and social security (including any underlying sensitive information in the identity card, such as racial or ethnic origin)
Identity verification, fraud prevention and security, to provide our Services, and to comply with legal obligations.
Stripe only processes sensitive personal information for the purposes specified in section 7027(m) of the California Consumer Privacy Act Regulations, or without the purpose of inferring characteristics about a consumer.

Qualifications & exceptions

  • Stripe only processes sensitive personal information for the purposes specified in section 7027(m) of the California Consumer Privacy Act Regulations, or without the purpose of inferring characteristics about a consumer.
Also annotated in the same passage (3)

Use & Processing · Company practice

Sensitive biometrics and location have distinct listed uses

Biometrics are listed for identity verification, fraud/security and other purposes consistent with consent and law, such as improving verification systems. Location data is listed for fraud/security, legal compliance and services. Both remain subject to the section’s specified-purpose or no-characteristic-inference limit; the location label does not independently establish GPS collection.

Supporting quotations

Biometric information
Identity verification, fraud prevention and security, and for other purposes consistent with your consent and applicable law, such as to improve our verification systems.
Location Data
Fraud detection and security, to comply with law, and to provide our Services.
Stripe only processes sensitive personal information for the purposes specified in section 7027(m) of the California Consumer Privacy Act Regulations, or without the purpose of inferring characteristics about a consumer.

Qualifications & exceptions

  • for other purposes consistent with your consent and applicable law
  • Stripe only processes sensitive personal information for the purposes specified in section 7027(m) of the California Consumer Privacy Act Regulations, or without the purpose of inferring characteristics about a consumer.
Also annotated in the same passage (3)

Use & Processing · Company practice

Sensitive account credentials support services and consent-consistent uses

The sensitive-data table includes account logins and financial accounts combined with codes, passwords or credentials allowing access. Purposes include services such as Financial Connections, legal compliance, enforcing terms and other uses consistent with consent and law, subject to the section’s specified-purpose or no-characteristic-inference limitation.

Supporting quotations

Account log-in, financial account in combination with any required security access code, password, or credentials allowing access to an account
To provide our Services (e.g., Financial Connections), comply with law, enforce our terms of services, and for other purposes consistent with your consent and applicable law.
Stripe only processes sensitive personal information for the purposes specified in section 7027(m) of the California Consumer Privacy Act Regulations, or without the purpose of inferring characteristics about a consumer.

Qualifications & exceptions

  • for other purposes consistent with your consent and applicable law.
  • Stripe only processes sensitive personal information for the purposes specified in section 7027(m) of the California Consumer Privacy Act Regulations, or without the purpose of inferring characteristics about a consumer.

Not stated here

  • The linked Financial Connections product page is not supplied; this card does not infer its additional terms.
Also annotated in the same passage (3)

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”

Retention & Deletion · Company practice

Retention considers purpose, jurisdiction, relationships and legal needs

Retention is described as necessary for the listed purposes, with criteria including jurisdiction, relationship, products, data nature/sensitivity, legal requirements and legitimate interests such as fraud/crime prevention, legal rights/process, quality improvements and lawful promotion. For most jurisdictions, Business User data is generally retained five or more years after the later of relationship end or last transaction. This is not a universal fixed period: the category table gives narrower rules, including biometrics until the earlier of one year or consent withdrawal and other consent-based sensitive data ending on withdrawal.

Supporting quotations

To determine the appropriate retention periods for different categories of Personal Data, we consider various criteria such as the jurisdiction you are located in, the nature of our relationship with you, the types of products or Services being offered or provided to you, the nature and sensitivity of your Personal Data, retention requirements under applicable laws and regulations, and other legitimate interests we may pursue through retaining your Personal Data, including detecting and preventing fraud and financial crimes, enforcing and defending our legal rights, complying with valid legal process requests from courts or competent authorities, improving the quality of our Services, and promoting our products and Services as appropriate and as permitted by applicable law and agreements.
For most jurisdictions, Stripe will generally keep Personal Data we obtain from our Business Users for a period of five or more years from the end of the business relationship with you, or the date of the last transaction, whichever is later.
The table below outlines different categories of personal data collected, along with the retention period or the criteria used to determine that period.
Biometric information (e.g., biometric identifiers from photo IDs and selfies used to confirm your identity)
No longer than 1 year, or upon revocation of your consent, whichever is earlier.
Where we rely on consent to collect your other sensitive personal information (e.g, financial account login credentials), Stripe will no longer retain this data upon your revocation of consent.

Qualifications & exceptions

  • For most jurisdictions
  • from the end of the business relationship with you, or the date of the last transaction, whichever is later.
  • No longer than 1 year, or upon revocation of your consent, whichever is earlier.
  • Where we rely on consent to collect your other sensitive personal information (e.g, financial account login credentials), Stripe will no longer retain this data upon your revocation of consent.

Cross-references

Also annotated in the same passage (1)

Retention & Deletion · Company practice

Contact and statutory identifier categories have purpose-based retention

The table groups non-sensitive identifiers such as names, postal/email addresses and account names with California statutory contact/card information and other categories. It retains these for as long as needed for law compliance, services and legitimate interests including fraud/crime prevention, legal rights/process, quality improvement and appropriate lawful promotion. It gives criteria rather than a single fixed deletion date for this row.

Supporting quotations

Non-sensitive Identifiers (e.g., name, postal address, email address, account name)
Categories of personal information described in Cal. Civ. Code § 1798.80(e) (such as name, address, telephone number, credit card or debit card number)
For the duration necessary for Stripe to: (1) comply with law; (2) provide the Stripe Services, and; (3) pursue our legitimate interests, including detecting and preventing fraud and financial crimes, enforcing and defending our legal rights, complying with valid legal process requests from courts or competent authorities, improving the quality of our Services, and promoting our products and Services as appropriate and as permitted by applicable law and agreements.

Qualifications & exceptions

  • For the duration necessary for Stripe to:
  • as appropriate and as permitted by applicable law and agreements.
Also annotated in the same passage (1)

Retention & Deletion · Company practice

Several categories have retention based on services, law and legitimate interests

The retention table groups protected-class characteristics such as ID-document age/gender, commercial transactions, online device/browser/usage activity and audiovisual information such as identity photos. They remain for the duration necessary for legal compliance, services and legitimate interests including fraud/crime prevention, legal rights/process, service improvement and appropriate lawful promotion. This row sets purpose criteria, not a universal deletion date.

Supporting quotations

Characteristics of protected classifications under California or federal law
Commercial information
Online activity information
Audiovisual
For the duration necessary for Stripe to: (1) comply with law; (2) provide the Stripe Services, and; (3) pursue our legitimate interests, including detecting and preventing fraud and financial crimes, enforcing and defending our legal rights, complying with valid legal process requests from courts or competent authorities, improving the quality of our Services, and promoting our products and Services as appropriate and as permitted by applicable law and agreements.

Qualifications & exceptions

  • For the duration necessary for Stripe to:
  • as appropriate and as permitted by applicable law and agreements.
Also annotated in the same passage (1)

Retention & Deletion · Company commitment

Biometric identifiers are kept until the earlier of one year or consent withdrawal

For biometric information such as identifiers from IDs and selfies used to confirm identity, the table states a maximum of one year or until consent is revoked, whichever comes first. This limit concerns biometrics, not every copy of an ID image or every account record.

Supporting quotations

Biometric information (e.g., biometric identifiers from photo IDs and selfies used to confirm your identity)
No longer than 1 year, or upon revocation of your consent, whichever is earlier.

Cross-references

Also annotated in the same passage (1)

Retention & Deletion · Company practice

Location data has purpose-based retention for law, services and risk protection

Geolocation such as IP addresses is retained as necessary for law compliance, services and legitimate interests including fraud/financial-crime prevention, legal rights and valid legal-process requests. This row gives no fixed period.

Supporting quotations

Geolocation Data (e.g., IP addresses)
For the duration necessary for Stripe to: (1) comply with law; (2) provide the Stripe Services, and; (3) pursue our legitimate interests, including detecting and preventing fraud and financial crimes, enforcing and defending our legal rights, and complying with valid legal process requests from courts or competent authorities.

Qualifications & exceptions

  • For the duration necessary for Stripe to:

Retention & Deletion · Company practice

Employment and nonpublic education data may remain for workforce and legal needs

Professional/employment data and nonpublic education information as defined by FERPA remain as needed for law, employment/performance decisions, future hiring, workplace health/safety, administration such as benefits, and legitimate interests including legal rights and valid legal process. The source cites FERPA without supplying its text.

Supporting quotations

Professional or Employment-Related Information
Education information that is not publicly available as defined in the Family Educational Rights and Privacy Act (20 U.S.C. § 1232g)
For the duration necessary for Stripe to: (1) comply with law; (2) make certain employment and performance-related decisions; (3) address future hiring needs; (4) ensure health and safety in the workplace; (5) conduct certain administrative tasks, including to administer benefits; and (6) pursue our legitimate interests, including enforcing and defending our legal rights and complying with valid legal process requests from courts or competent authorities.

Qualifications & exceptions

  • Education information that is not publicly available as defined in the Family Educational Rights and Privacy Act (20 U.S.C. § 1232g)
  • For the duration necessary for Stripe to:

Retention & Deletion · Company practice

Sensitive-data retention distinguishes IDs from consent-based credentials

Government-ID information, including sensitive content, and location data remain as necessary for law, services and legitimate interests such as fraud/crime prevention and legal rights/process. Biometrics follow the earlier one-year-or-withdrawal rule. For other sensitive data collected on consent, such as financial-account login credentials, retention ends when consent is withdrawn.

Supporting quotations

Sensitive personal information, as defined by California law
For information regarding your government IDs (including the sensitive data therein) and your location data, Stripe will retain that data for the duration necessary to: (1) comply with law; (2) provide the Stripe Services, and; (3) pursue our legitimate interests, including detecting and preventing fraud and financial crimes, enforcing and defending our legal rights, complying with valid legal process requests from courts or competent authorities. For biometric data, see above.
Where we rely on consent to collect your other sensitive personal information (e.g, financial account login credentials), Stripe will no longer retain this data upon your revocation of consent.
No longer than 1 year, or upon revocation of your consent, whichever is earlier.

Qualifications & exceptions

  • Where we rely on consent to collect your other sensitive personal information (e.g, financial account login credentials), Stripe will no longer retain this data upon your revocation of consent.
  • No longer than 1 year, or upon revocation of your consent, whichever is earlier.
Also annotated in the same passage (2)

Legal Rights & Agreement Rules · Context

Published privacy-request metrics refer to 2023, not a current service guarantee

The page reports 2023 aggregate requests from Californians that may also include nonresidents: seven requests to know and 7,719 deletion requests received and complied with wholly or partly, zero correction requests, and a one-day average response to know/delete requests. These historical aggregates do not promise a one-day response or full deletion in an individual case.

Supporting quotations

The following includes aggregate metrics of data subject rights requests received in the 2023 calendar year. This data reflects requests received from individuals in California and may also include requests from individuals who do not reside in California.
Number of “request to know” received and complied with in whole or in part: 7
Number of “requests to delete” received and complied with in whole or in part: 7719
Number of “request to correct” received: 0
Average number of days taken to respond to a request to know or delete: 1

Qualifications & exceptions

  • This data reflects requests received from individuals in California and may also include requests from individuals who do not reside in California.

Retention & Deletion · Procedure

General deletion requests are routed by relationship, with legal retention limits

General deletion requesters are directed to a support page to act according to their relationship with the publisher, with a contact option for concerns. Data may remain where law permits, including after account closure for prescribed anti-terrorism/AML retention. The passage does not supply a single applicable period or the linked support page’s full procedure.

Supporting quotations

Due to the nature of Stripe’s products and Services, when we receive a general “request to delete,” our process is to direct the requestor to a page to action their request depending upon the relationship they have with Stripe.
Stripe may retain Personal Data where permitted by law, including to comply with our legal obligations. For example, as a provider of payment services, Stripe is required to comply with many regulations, including anti-terrorism and anti-money laundering laws. These laws require Stripe to retain certain information associated with Stripe users for a prescribed period of time after account closure.

Qualifications & exceptions

  • depending upon the relationship they have with Stripe.
  • where permitted by law, including to comply with our legal obligations.

Not stated here

  • The linked support page and Privacy Policy are not supplied; their full deletion procedures and retention obligations are not inferred.

Legal Rights & Agreement Rules · Context

Controller processing relies on several bases, with rights and regional qualifications

The publisher describes controller processing for business/user relationships, transactions, regulatory/legal duties and legitimate interests. It says interests are balanced against individual rights, consent can be withdrawn without undoing earlier lawful processing, and jurisdiction-specific rules may add bases or requirements through the separate Privacy Policy. Processing solely on a Business User’s documented instructions instead makes it a processor/service provider, with the Business User determining the basis.

Supporting quotations

As a data controller we rely upon a number of legal grounds to enable our use of your Personal Data.
Legitimate interests are balanced against individual rights. Consent may be withdrawn without affecting earlier lawful processing.
Jurisdiction-specific rules may add requirements or bases as set out in the ‘Jurisdiction-specific provisions’ section of our Privacy Policy.
When Stripe processes Personal Data solely on a Business User’s documented instructions, Stripe acts as a data processor or service provider and the Business User determines the legal basis.

Qualifications & exceptions

  • Legitimate interests are balanced against individual rights. Consent may be withdrawn without affecting earlier lawful processing.
  • When Stripe processes Personal Data solely on a Business User’s documented instructions

Not stated here

  • The separate Privacy Policy’s jurisdiction-specific provisions are not supplied; additional local requirements remain unknown.
Also annotated in the same passage (1)

Inference & Profiling · Company practice

Personal data may support AI development and improvement where law permits

The publisher may process personal data to develop, train, test, evaluate and improve AI/ML models used to provide, protect and improve its services, where permitted by applicable law. This general statement does not override product-specific consent or purpose limits.

Supporting quotations

Where permitted by applicable law, we may also process Personal Data to develop, train, test, evaluate and improve artificial intelligence and machine-learning models used to provide, protect and improve our Services.

Legal Rights & Agreement Rules · Context

The End User table points Link and Financial Connections to a separate center

An End User directly uses a consumer service for personal purposes. The introduction says Link and Financial Connections are covered at a linked center, although the following table also explicitly includes a Link consent row. The saved page therefore supports those explicit statements, not an assumption that all other End User rows govern those products or that the linked center’s terms are supplied.

Supporting quotations

When you directly use a consumer Service for your personal use, we refer to you as an “End User.” Please note that Link and Financial Connections are covered here.
For the provision of our Services including Link, Atlas and Identity.

Qualifications & exceptions

  • When you directly use a consumer Service for your personal use

Not stated here

  • The linked Link privacy center is not supplied; the scope relationship between its terms and this table is not fully explained.
Also annotated in the same passage (1)

Use & Processing · Company practice

End User service processing includes authorized AI-agent purchases and payments

The table covers delivery, support, personalization and messages, plus facilitating, authenticating, processing, protecting and supporting payments initiated through AI agents/platforms or other authorized software, including credentials/tokens, authorizations, refunds and disputes. Data includes name/contact and bank/card details including CVC/expiry; agentic payments may add purchase instructions, authorization scope/status, delivery information, credentials/tokens and transactions. Listed bases are contractual necessity, legitimate interests in authentication/fraud/loss protection, and legal/payment-network requirements.

Supporting quotations

Provide our Services. To provide Services to you, including delivery, support, personalization and messages related to the service. This includes facilitating, authenticating, processing, supporting and protecting purchases and payments initiated through an AI agent, AI platform or other authorized software, including managing related payment credentials, tokens, authorizations, refunds, disputes and transaction-related requests.
Your name, contact information, payment information including Bank Account Information and Bank Payments, and/or payment card number, CVC code and expiration date. For agentic payments, this may also include purchase instructions, authorization scope and status, contact and delivery information, paymentcredentials and associated tokens, and relevant Transaction Data.
Our contractual necessity to perform our contractual relationship with you, under applicable data protection laws.
We also rely on our legitimate interests in authenticating transactions, preventing fraud and financial loss, and protecting the Services, and on our legal obligations and applicable payment-network requirements.

Qualifications & exceptions

  • Our contractual necessity to perform our contractual relationship with you, under applicable data protection laws.

Account & Service Control · User right or choice

The explicit consent row describes Link storage and withdrawal of consent

The row names Link, Atlas and Identity, and states consent-based processing can be withdrawn any time without affecting earlier lawful consent-based processing. Its data example says choosing Link permits storage of payment-method and related information for easier merchant purchases; its legal-basis cell is consent. The introduction also points Link to a separate center, so this card is limited to the row actually supplied.

Supporting quotations

For the provision of our Services including Link, Atlas and Identity. When we process data based on your consent, you have the right to withdraw your consent at any time without affecting the lawfulness of processing based on such consent before the consent is withdrawn.
If you choose to use Link you agree to let Stripe store your payment method and related information so that you can more readily make purchases with Business Users who use Stripe to provide payment processing Services (e.g. Stripe Checkout).
Based on consent in processing this personal information.
Please note that Link and Financial Connections are covered here.

Qualifications & exceptions

  • without affecting the lawfulness of processing based on such consent before the consent is withdrawn.

Not stated here

  • The linked Link privacy center is not supplied; no additional product terms are inferred.
Also annotated in the same passage (1)

Use & Processing · Company practice

Card and financial-product offers can use identity, account and online data

For card/financial products including Issuing and Treasury, the table lists offering products under the publisher’s or a Business User’s brand. Data includes names, contacts/addresses, transactions, passwords/PINs, card PANs, age/birth date, card/license/tax IDs, cookies/tags/beacons and IP. The stated basis is legitimate interests in promoting products and determining eligibility/offering new services, subject to the general balancing and regional qualifications.

Supporting quotations

Card Products and Financial Products including Issuing and Treasury
We use your Personal Data to offer you card products and financial products and Services under the Stripe brand and/or under the brand of a Business User.
Your name, email address, phone number, postal address, transaction information, password, PIN or similar credentials, card PANs, age, DOB, credit card number, drivers license number, tax ID, cookie data, tags and beacons, IP address.
Our legitimate interests in promoting our products and in determining eligibility for and offer new Stripe products and Services.
Also annotated in the same passage (1)

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)

Use & Processing · Company practice

Digital-asset services may record transactions on public blockchains

Cryptocurrency/stablecoin services include payments, payouts, purchases and transfers that may be recorded publicly on a blockchain. Authentication, support, fraud prevention, sanctions and regulatory compliance may use names, emails, birth dates, billing/IP, transactions, identity/KYC, wallet/blockchain identifiers and legally required originator/beneficiary details. The table cites requested-transaction necessity, AML/sanctions/Travel Rule duties, fraud/security/loss interests, and consent where law specifically requires or for optional use.

Supporting quotations

Provide cryptocurrency, stablecoin and blockchain-related Services, including enabling payments, payouts, purchases and transfers involving stablecoins or other digital assets. These transactions may be recorded on a public blockchain. We also process Personal Data to authenticate and support transactions, prevent fraud, conduct sanctions screening and comply with applicable financial-regulatory requirements.
Your name, email address, date of birth, billing address, IP address, Transaction Data, identity and KYC information, wallet addresses and identifiers, blockchain transaction information, and originator and beneficiary information where required by applicable law.
Our contractual necessity to provide the transaction requested by you.
Our legal obligations, including applicable AML, sanctions and Travel Rule requirements applicable to stablecoin and other qualifying digital-asset transfers; and our legitimate interests in fraud prevention, security and loss prevention. We rely on consent where specifically required by applicable law or for an optional use.

Qualifications & exceptions

  • originator and beneficiary information where required by applicable law.
  • We rely on consent where specifically required by applicable law or for an optional use.
Also annotated in the same passage (1)

Use & Processing · Company practice

Digital-asset data processing includes compliance, with permanent public-ledger limits

The End User table lists identity/contact, birth date, billing/IP, transactions, KYC, wallet/blockchain and legally required originator/beneficiary information for digital-asset services. Bases include requested-transaction necessity, applicable AML/sanctions/Travel Rule duties, fraud/security/loss interests and required or optional-use consent. The separate blockchain explanation says on-chain records cannot be altered or deleted, may show wallets/amounts/times and may be linked to individuals; identity can be decoupled where possible, but the public record remains.

Supporting quotations

Your name, email address, date of birth, billing address, IP address, Transaction Data, identity and KYC information, wallet addresses and identifiers, blockchain transaction information, and originator and beneficiary information where required by applicable law.
Our contractual necessity to provide the transaction requested by you.
Our legal obligations, including applicable AML, sanctions and Travel Rule requirements applicable to stablecoin and other qualifying digital-asset transfers; and our legitimate interests in fraud prevention, security and loss prevention. We rely on consent where specifically required by applicable law or for an optional use.
These transactions may be recorded on a public blockchain.
Payments in stablecoin or other digital assets are recorded on a public blockchain, which is permanent and cannot be altered or deleted.
Although wallet addresses typically do not directly display a person’s name, they may be linked to an individual through other information.

Qualifications & exceptions

  • originator and beneficiary information where required by applicable law.
  • We rely on consent where specifically required by applicable law or for an optional use.
  • Although wallet addresses typically do not directly display a person’s name, they may be linked to an individual through other information.
Also annotated in the same passage (3)

Charges & Financial Obligations · Company practice

Financing eligibility may be assessed before an offer is made

The service-offer/change-notice row gives Capital as an example: partners offer financing to users meeting criteria, and eligibility data is processed before an offer. Although in the End User table, its data cell specifically names Business User Representatives’ identity/contacts, business address and platform ID, and platform performance or voluntarily supplied off-platform performance. The stated basis is legitimate interests in promotion and eligibility/new offers, not a guarantee of financing.

Supporting quotations

Offer our Services and Alert you of Changes to our Services.
Certain information will be processed by Stripe prior to the offer of financing in order to determine eligibility.
The name and other identifying details and contact information of a Business User’s Representatives, physical address of Business User, and the Business User's Stripe ID and information related to the Business User’s performance on Stripe or off of Stripe if the Business User chooses to provide such information.
Our legitimate interests in promoting our products and in determining eligibility for and offer new Stripe products and Services.

Qualifications & exceptions

  • off of Stripe if the Business User chooses to provide such information.

Security & Safeguards · Company practice

End User fraud detection relies on transaction and online-activity data

The fraud row uses data across services to protect the publisher, Business Users and financial partners, including detecting unauthorized logins. Inputs include identity/contact and payment/card/bank/image details, merchant/location, amount/date and sometimes purchase information, phone/tax ID, browsing/usage/referrer/location/cookie/device/IP/physical-address data. The stated basis is legitimate interests in detecting harmful fraud affecting End Users.

Supporting quotations

Fraud Detection Services.
We use your Personal Data collected across our Services (e.g. Stripe Radar) to detect and prevent fraud against us, our Business Users and Financial Partners, including to detect unauthorized log-ins using your online activity.
Transaction information. This includes: name, email address, billing and/or shipping address, payment method information (such as credit or debit card number, bank account information or payment card image), merchant and location, purchase amount, date of purchase, and in some cases, some information about what you have purchased, phone number and tax-related ID. This includes web browsing information, usage data, referring URLs, location, cookies data, device data and identifiers. IP address and physical address.
Our legitimate interests in monitoring and detecting fraud to ensure we detect activity that can have a harmful effect on our End Users.

Use & Processing · Company practice

The marketing row distinguishes End User advertising from End Customer disclosures

The row describes End User eligibility/offers and interest-based marketing using name, email, work phone/title, IP and browsing behavior. It lists both consent and legitimate interests in offering relevant products, without specifying which applies in every case. It separately says End Customer data is not shared for third parties’ own marketing without permission to the publisher or third party. Those two audiences and purposes should not be treated as interchangeable.

Supporting quotations

Marketing and Advertising. We may use your Personal Data to assess your eligibility for and offer you other Services. We use End User Personal Data for interest-based advertising and marketing purposes. We do not share End Customer Personal Data to third parties for their marketing purposes unless you give us or the third party permission to do so.
Contact information including: name, email address, work phone number, and job title.
Connection data such as IP address, and web behavior (page visited, length on page, etc.)
Based on consent in processing this personal information.
Our legitimate interest in undertaking marketing activities to offer you products or Services that may be of interest to you.

Qualifications & exceptions

  • We do not share End Customer Personal Data to third parties for their marketing purposes unless you give us or the third party permission to do so.

Legal Rights & Agreement Rules · Company practice

End User data may be processed or shared for compliance and harm prevention

As believed necessary, processing/sharing can cover law and payment-method rules, contractual rights, protection against harm/fraud/security incidents and valid legal process, including foreign authorities. Any processed personal data may be involved, including ID documents and selfies. Stated bases include legal obligations, vital/public/substantial-public interests and the publisher’s or others’ legitimate interests in security, preventing lawbreaking/harm/crime, defending rights, tax collection/fraud prevention and preventing loss.

Supporting quotations

Compliance and Harm Prevention. We process and share Personal Data as we believe necessary: (i) to comply with applicable law, (ii) for compliance with rules imposed by payment method in connection with use of that payment method (e.g. network rules for Visa); (iii) to enforce our contractual rights; (iv) to secure or protect the Services, rights, privacy, safety and property of Stripe, you or others, including against other malicious or fraudulent activity and security incidents; and (v) to respond to valid legal process requests from courts, law enforcement agencies, regulatory agencies, and other public and government authorities, which may include authorities outside your country of residence.
Any Personal Data we process, including information necessary for identity verification such as government-issued IDs or selfie images.
Where these processing activities or disclosures are necessary to comply with our legal obligations, for the protection of a person's vital interests, for reasons of public interest, for reasons of substantial public interest, or for the purposes of Stripe’s or a third party’s legitimate interest in keeping Stripe secure, preventing a breach of the law, harm or crime, enforcing or defending legal rights, claims, or obligations, facilitating the collection of taxes and prevention of tax fraud or preventing loss or damage.

Qualifications & exceptions

  • as we believe necessary
  • Where these processing activities or disclosures are necessary to comply with our legal obligations

Use & Processing · Company practice

End Customer processing supports merchant payments, taxes and billing

End Customers transact with a Business User without directly doing business with the publisher. Their table covers online/in-person payments, tax calculation, invoicing/billing and revenue calculation for Business Users. Transaction information may arrive directly, through the Business User or through a provider depending on integration, including when a purchase begins or a refund occurs. The row cites financial/regulatory legal duties and consent where required for BNPL pre-qualification/disclosure.

Supporting quotations

but are not directly doing business with Stripe, we refer to you as an “End Customer.”
Provide our Services to Business Users, including to process online payment transactions or in-person checkout, to calculate applicable tax, to invoice and bill, and to calculate their revenue.
Depending on how the Business User has integrated our Business Services, we may receive this information directly from you, the Business User or another service provider to you or the Business User.
Our legal obligations in respect of our financial and regulatory obligations.
We rely on consent where required for BNPL pre-qualification or disclosure.

Qualifications & exceptions

  • Depending on how the Business User has integrated our Business Services
  • We rely on consent where required for BNPL pre-qualification or disclosure.
Also annotated in the same passage (2)

Data Access & Collection · Company practice

End Customer transaction data can arrive before a purchase is completed

For merchant payment, tax and billing services, the publisher receives End Customer transaction information for payments, cart-reminder activity, refunds, purchase starts and other transactions, with sources depending on integration. Clearly listed fields include name/email, billing/shipping, card/bank/image details, merchant/location, amount/date and merchant transaction history. The source’s phrase “some information about what you have collect” is incomplete; it does not clearly identify an additional data category. The table cites financial/regulatory obligations and required BNPL consent.

Supporting quotations

If you are an End Customer, when you make payments to, send shopping cart reminders, get refunds from, begin a purchase or otherwise transact with a Business User through Stripe’s Services or a Stripe-provided device, Stripe will receive your transaction information. Depending on how the Business User has integrated our Business Services, we may receive this information directly from you, the Business User or another service provider to you or the Business User.
Your name, email, billing and/or shipping address, payment method information (such as credit or debit card number, bank account information or payment card image), merchant and location, purchase amount, date of purchase, and in some cases, some information about what you have collect
We may also receive your transaction history with the Business User.
Our legal obligations in respect of our financial and regulatory obligations.
We rely on consent where required for BNPL pre-qualification or disclosure.
Provide our Services to Business Users, including to process online payment transactions or in-person checkout, to calculate applicable tax, to invoice and bill, and to calculate their revenue.

Qualifications & exceptions

  • Depending on how the Business User has integrated our Business Services
  • We rely on consent where required for BNPL pre-qualification or disclosure.

Not stated here

  • The incomplete source phrase does not establish what additional purchase information was intended; no missing words or category are inferred.
Also annotated in the same passage (2)

Data Access & Collection · Company practice

End Customer data categories include unsubmitted checkout fields

The merchant-services row expressly includes information typed into a checkout field even when it is not ultimately submitted to the Business User. The row concerns payment, tax, billing and revenue services and lists financial/regulatory legal duties plus BNPL consent where required; it does not say completing the purchase is necessary for this category to be processed.

Supporting quotations

Transaction-Related Information / Purchase Interests. Information typed into a checkout field that is not ultimately submitted to the Business User.
Provide our Services to Business Users, including to process online payment transactions or in-person checkout, to calculate applicable tax, to invoice and bill, and to calculate their revenue.
Our legal obligations in respect of our financial and regulatory obligations.
We rely on consent where required for BNPL pre-qualification or disclosure.

Qualifications & exceptions

  • We rely on consent where required for BNPL pre-qualification or disclosure.
Also annotated in the same passage (2)

Use & Processing · Company practice

Verification data supports payment ordering, merchant fraud thresholds and offered BNPL

For End Customers, verification supports ordering payment methods per customer, merchant-chosen fraud thresholds, payment-method verification and, where offered, BNPL pre-qualification/transactions. Data may be age for restricted goods or authority to use a method; what you choose to share may include government ID, photos/live images or information visible in a card image. Bases are financial/regulatory duties and consent where required for BNPL pre-qualification/disclosure.

Supporting quotations

Provide our Services to Business Users, to order payment methods on a per-customer basis on behalf of the Business User, to implement fraud thresholds chosen by the Business User, and to verify your payment method. This may also include enabling BNPL pre-qualification or transactions where offered by the Business User.
Verification Information. Your age (when purchasing age restricted goods) or information about you being the person who is authorized to use a payment method.
The information collected will be the information that you choose to share for these purposes, which may include your government ID, your photo, your live image, and Personal Data apparent from the physical payment method (e.g. credit card image).
Our legal obligations in respect of our financial and regulatory obligations.
We rely on consent where required for BNPL pre-qualification or disclosure.

Qualifications & exceptions

  • Your age (when purchasing age restricted goods)
  • The information collected will be the information that you choose to share for these purposes
  • We rely on consent where required for BNPL pre-qualification or disclosure.

Security & Safeguards · Company practice

End Customer identity checks may compare selfies and IDs and share issuer risk signals

Identity data supports verification for the publisher or merchants, fraud/loss reduction, security, 3DS/similar authentication and issuer risk signals. In some cases selfies and ID images are compared for a match, and provider/service information assists verification. The table lists consent and legitimate interests in fraud/loss prevention, disputes and payment improvement; it does not assign one basis to every specific check.

Supporting quotations

Reduce fraud and enhance security. We will use Personal Data about your identity, including information that you provide, to perform verification Services for Stripe or for the Business Users that you are doing business with and to reduce fraud and loss, and enhance security, and to support 3DS and similar authentication and share risk signals with issuers.
In some cases you may provide a “selfie” along with an image of your identity document, and we will use technology to compare and calculate whether they match and can be “verified.” We will use information from our service providers and our Services to help verify your identity and fraud prevention.
Based on consent in processing this personal information.
Our legitimate interests in fraud and loss prevention, dispute resolution, and payment improvement.

Qualifications & exceptions

  • In some cases you may provide a “selfie” along with an image of your identity document
  • Based on consent in processing this personal information.

Inference & Profiling · Company practice

Radar and card verification may generate automated risk outputs and share limited data

For End Customers, Radar/card verification detects fraudulent cards and unauthorized logins, may share limited data with requesting merchants for attempted-transaction risk, and may use card images for service improvement. Automated/AI models can generate fraud, failure and chargeback scores or recommendations to authenticate, approve, block or review. Inputs include transaction/contact/payment/card-image and purchase data, phone/tax ID, browsing/usage/referrer/location/cookie/device/IP/physical-address information and model inputs/outputs. The stated basis is legitimate interests in preventing fraud/loss/unauthorized payments and improving risk models. Where law requires, notices and rights are provided for automated decisions with legal or similarly significant effects.

Supporting quotations

In providing such Services, we may provide Business Users that have requested such Services with limited Personal Data about End Customers so that the Business Users can assess the fraud risk associated with an attempted transaction by its End Customer. We may also use payment card images to improve our Business Services. We may use automated tools and artificial intelligence or machine-learning models to assess fraud, payment-failure and chargeback risk and to generate scores, indicators or recommendations concerning authentication, approval, blocking or review.
Transaction information. This includes: name, email address, billing and/or shipping address, payment method information (such as credit or debit card number, bank account information or payment card image), merchant and location, purchase amount, date of purchase, and in some cases, some information about what you have purchased, phone number and tax-related ID.
This includes web browsing information, usage data, referring URLs, location, cookies data, device data and identifiers. Data may also include model inputs and outputs, such as fraud-risk scores, payment-failure or chargeback predictions, and recommendations concerning a transaction or account.
IP address and physical address.
Our legitimate interests in detecting, monitoring and preventing fraud, loss, and unauthorized payment transactions, as well as developing and improving our fraud and payment-risk models. Where required by applicable law, we provide notices and rights relating to automated decisions that produce legal or similarly significant effects.

Qualifications & exceptions

  • Business Users that have requested such Services
  • Where required by applicable law, we provide notices and rights relating to automated decisions that produce legal or similarly significant effects.

Legal Rights & Agreement Rules · Company practice

End Customer compliance disclosures include financial, identity and security data

The publisher shares relevant End Customer data as believed necessary for law/payment-method rules, contractual rights, security and harm/loss prevention, or valid legal process including foreign authorities. Data can include transactions, identity, wallets/transfers, tax, communications, fraud/security and originator/beneficiary information. Bases include necessary legal compliance and stated interests in security, preventing harm/loss/crime, legal rights and tax collection. The final basis ends “and prevention of.” without naming the object; no omitted purpose is inferred.

Supporting quotations

Compliance and Harm Prevention. We share Personal Data as we believe necessary: (i) to comply with applicable law, (ii) to comply with rules imposed by payment method in connection with use of that payment method; (iii) to enforce our contractual rights; (iv) to secure or protect the Services, rights, privacy, safety and property of Stripe, you or others, including against other malicious or fraudulent activity, loss, and security incidents; and (v) to respond to valid legal process requests from courts, law enforcement agencies, regulatory agencies, and other public and government authorities, which may include authorities outside your country of residence.
Any relevant Personal Data we process, including Transaction Data, identity, wallet, transfer, tax, communications, fraud and security data, and originator and beneficiary information.
Our legal obligations where disclosures are necessary to comply with our legal obligations.
Our legitimate interest in keeping Stripe secure, preventing a breach of the law, harm, loss, or crime, enforcing or defending legal rights, claims, or obligations, facilitating the collection of taxes and prevention of.

Qualifications & exceptions

  • as we believe necessary
  • where disclosures are necessary to comply with our legal obligations.

Not stated here

  • The source ends the basis with “and prevention of.”; the missing object and any intended additional basis remain unknown.

Use & Processing · Company practice

Representative account and security processing has several stated bases

Representatives act for existing or potential Business Users, such as founders or merchant-account administrators. Identity and account data supports creating/administering accounts, authentication, fraud prevention and independent Connect compliance/platform purposes. Inputs include voluntarily supplied onboarding ID/photo/live/card-image details, credentials/accounts, government/tax/bank data, transactions and device/risk/compliance signals. Bases include financial/regulatory duties such as AML/KYC/sanctions/reporting and legitimate interests in administration, security and loss/platform management. Contractual necessity applies where the Representative is a party to or personally requests the service.

Supporting quotations

When you are acting on behalf of an existing or potential Business User (e.g., you are a founder of a company, or administering an account for a merchant who is a Business User), we refer to you as a “Representative.”
Reduce fraud, administer accounts and protect the platform and enhance security. We will use Personal Data about your identity, including information that you provide, to create and administer Business User accounts; authenticate and verify Representatives; prevent fraud; and process Connected Account data for Stripe’s independent Connect compliance and platform purposes.
Onboarding and verification information that you choose to share for these purposes, which may include your government ID, photo, live image, and Personal Data apparent from the physical payment method (e.g. credit card image). Credential and account data, government, tax and bank data, photos and live images, Transaction Data, and device, fraud, risk and compliance signals.
Our legal obligations in respect of our financial and regulatory obligations.
Our legitimate interests in account administration, authentication, security, loss prevention and platform management.
Contractual necessity applies where the Representative is party to or personally requests the Service.

Qualifications & exceptions

  • Onboarding and verification information that you choose to share for these purposes
  • Contractual necessity applies where the Representative is party to or personally requests the Service.

Use & Processing · Company practice

Representative data may support advertising, enriched leads and eligibility offers

Representative data may be used/shared for marketing and interest-based advertising, subject to legally required consent, to enrich leads and assess relevant-service eligibility including Capital. It includes names, emails, work phones/titles, IP/web behavior, account engagement and employer/company/public/enrichment information. Stated bases are legitimate interests in prospecting, accurate data, permitted marketing and relevant offers, with consent where required.

Supporting quotations

Advertising, Leads and Offers. We may use and share Representative Personal Data with others so that we may advertise and market our products and Services to you, including through interest-based advertising subject to any consent requirements under applicable law. Identify and enrich business leads, and assess eligibility for relevant Services, including Stripe Capital.
Contact information including: name, email address, work phone number, and job title.
Connection, account activity data and engagement data such as IP address, and web behavior (page visited, length on page, etc.) Employer and firmographic data, public and enrichment data.
Our legitimate interests in prospecting, data accuracy, permitted marketing and relevant offers. Consent where required in processing this personal information.

Qualifications & exceptions

  • subject to any consent requirements under applicable law.
  • Consent where required in processing this personal information.

Use & Processing · Company practice

Representative communications and optional profiles can involve AI tools

The row covers service/support and permitted marketing, event/survey invitations, optional profiles and automated dialing/AI voice/transcription/chat/email, including permitted recordings for quality and model improvement. Data includes contacts/profiles, interaction contents, calls/recordings/transcripts/chats/emails, technical and engagement information. Bases are contractual necessity or legitimate interests for permitted service/support/profile functions, quality/improvement interests, consent where required for outreach/recording/transcription/model use, and duties for required recordings.

Supporting quotations

Communications and Stripe Profile. We may send you service, support and permitted email marketing communications about Stripe products and Services, invite you to participate in our events or surveys, or otherwise communicate with you for marketing purposes. Create and manage an optional Stripe Profile; and use automated dialing, AI voice, transcription, chat or email tools, including permitted recordings or transcripts for quality and model improvement.
Contact information and profile data such as your name, email address, phone number; interaction content, calls, recordings, ranscripts, chats, emails, technical metadata and engagement data.
Contractual necessity or our legitimate interests for permitted Service, support and profile functions. Our legitimate interests in quality and improvement. Consent where required for outreach, recording, transcription or model use, and legal obligations for required recordings.

Qualifications & exceptions

  • Consent where required for outreach, recording, transcription or model use, and legal obligations for required recordings.

Charges & Financial Obligations · Company practice

Tax, Atlas and Capital use representative identity, financial and business data

For tax/incorporation, KYC/regulation, government filings, permitted professional referrals and Capital assessment/servicing, data may include contacts, ownership, birth date, government/tax IDs, bank/business/filing information, payment performance, balances, credit, applications and repayments. Bank information can also be supplied by choice. Bases include financial/regulatory obligations, contractual necessity, legitimate interests in permitted Capital eligibility/administration/risk/fraud, and consent for referrals, credit or data access where required.

Supporting quotations

Tax, Atlas (Incorporation) and Capital Services. We may use your Personal Data to provide tax and Atlas incorporation Services, KYC and regulatory processing, government filings and permitted professional referrals; assess and service Stripe Capital financing.
Your contact details, such as name, postal address, telephone number, and email address; and financial and personal information about you, such as your ownership interest in the Business User, your date of birth and government identifiers associated with you and your organization (such as your social security number, tax number, or Employer Identification Number). Tax, bank, business and filing data; payment performance, balances, credit, application and repayment data. You may also choose to provide bank account information.
Our compliance with legal obligations in respect of our financial and regulatory obligations.
Our contractual necessity to perform our contractual relationship with you, under applicable data protection laws.
Our legitimate interests in permitted Capital eligibility, administration, risk management and fraud prevention. Consent for referrals, credit or data access where required.

Qualifications & exceptions

  • You may also choose to provide bank account information.
  • Consent for referrals, credit or data access where required.
Also annotated in the same passage (1)

Legal Rights & Agreement Rules · Context

Tax, Atlas and Capital bases include compliance, contracts and qualified consent

The Representative table’s Tax/Atlas/Capital row cites identity verification for fraud monitoring, AML/KYC and financial reporting, contractual necessity, and legitimate interests in permitted Capital eligibility, administration, risk and fraud prevention. Consent is used for referrals, credit or data access where required. This continues the row’s identity, financial, ownership, filing, credit and repayment data description.

Supporting quotations

Our compliance with legal obligations in respect of our financial and regulatory obligations. We process Personal Data to verify the identity of the Representatives of our Business Users in order to comply with fraud monitoring, prevention and detection obligations, laws associated with the identification and reporting of illegal and illicit activity, such as AML (Anti-Money Laundering) and KYC (Know-Your-Customer) obligations, and financial reporting obligations.
Our contractual necessity to perform our contractual relationship with you, under applicable data protection laws.
Our legitimate interests in permitted Capital eligibility, administration, risk management and fraud prevention. Consent for referrals, credit or data access where required.

Qualifications & exceptions

  • under applicable data protection laws.
  • Consent for referrals, credit or data access where required.
Also annotated in the same passage (1)

Use & Processing · Company practice

Visitor inquiries can lead to responses and marketing with consent or an opt-out

Visitors include people browsing without logging in or otherwise contacting the publisher. Provided contact information supports responses, and inquiries about services may lead to marketing emails with consent requested or an opt-out in messages. Chatbots/chat/email and permitted call recording/transcription may be used. Data includes contacts, interactions/product interests, device/technical information and calls/recordings/transcripts. Bases are legitimate interests in responses, service notices, support, engagement and permitted quality assurance, plus consent where required.

Supporting quotations

When you visit a Site without being logged into a Stripe account or otherwise communicate with Stripe, we refer to you as a “Visitor.”
Communications. We use any contact information that you provide to us to respond to any inquiries or requests for information you made; and if you have asked about us or our Services, to send you marketing emails by either asking for your consent or providing you an opt out in any messages we send. We may also provide support or information through chatbots, chat, email and other engagement tools, and where permitted, record or transcribe calls.
Contact information such as your name, email address, phone number.
Interaction and product-interest data; device and technical data; and calls, recordings and transcripts.
Our legitimate interests in responding to inquiries, sending Service notices and providing customer support, improving engagement and permitted quality assurance.
Consent where required for communications, recording or transcription.

Qualifications & exceptions

  • if you have asked about us or our Services
  • Consent where required for communications, recording or transcription.

Use & Processing · Company practice

Visitor cookies support site functions, analytics and permitted advertising

The publisher and providers may use visitor/device data to operate, personalize and analyze sites, diagnose problems, use lead forms, advertise including interest-based ads/lead generation, and measure engagement. Cookies can supply IP, device/browser IDs and pages/interactions. The row cites legitimate interests in relevant marketing, site operation and permitted analytics, with consent for nonessential cookies, targeted ads or lead processing where required.

Supporting quotations

Advertising, personalization and analytics. When you visit our Sites, we (and our service providers) may use Personal Data collected from you and your device to operate, personalize and analyze Sites; diagnose issues; use lead forms; conduct permitted advertising (including “interest-based advertising” and lead generation); and measure engagement.
Information collected from cookies such as your IP, device, browser ID, and pages on and interactions with our website and Services which you have visited or used.
Our legitimate interest in undertaking marketing activities to offer you products or Services that may be of interest to you, Site operation, permitted analytics.
Consent for non-essential cookies, targeted advertising or lead processing where required.

Qualifications & exceptions

  • Consent for non-essential cookies, targeted advertising or lead processing where required.

Security & Safeguards · Company practice

Visitor security data includes event access, recordings and CCTV

Visitor data across services supports bot/abuse/loss/fraud/security detection, events and premises administration, and protection of people/property through access controls, event recordings and CCTV. Inputs include cookie fraud signals, device/browser/IP/activity/threat information, registration/attendance/access, supplied accessibility information and images/recordings. Bases are fraud/loss/site/premises/event interests, safety/accessibility legal duties and consent for optional or sensitive uses where required.

Supporting quotations

Fraud Detection and Security. We use your Personal Data collected across our Services to detect bots, abuse, loss, and prevent fraud and security incidents; administer Stripe events and premises; and protect people and property using access controls, event recordings, and CCTV.
Advanced Fraud Signals information collected via cookies. This includes Device, browser, cookie, IP, activity and threat-intelligence data; registration, attendance and access data; accessibility information provided; images, recordings and CCTV.
Our legitimate interests in fraud and loss prevention, Site and premises security and event administration.
Our legal obligations for monitoring safety or accessibility.
Consent for optional or sensitive uses where required.

Qualifications & exceptions

  • Consent for optional or sensitive uses where required.

Legal Rights & Agreement Rules · Procedure

Business Users can consult DPA FAQs or contact the publisher

The page describes a DPA as a controller–processor contract setting roles and responsibilities for personal-data processing. Business Users are directed to linked FAQs and to contact the publisher or their account manager with questions. This passage does not supply the separate DPA’s obligations.

Supporting quotations

A Data Processing Agreement (“DPA”) is a contract between a data controller and a data processor that describes the roles and responsibilities of the parties when personal data is processed.
If you are a Business User, please visit our FAQs page here to learn more about our DPA.

Not stated here

  • The linked DPA FAQ and the DPA itself are not supplied here; detailed contract rights and duties remain outside this card.

Security & Safeguards · Company practice

Product launches use a privacy-team review process

The publisher says it relies on an internal privacy team and a review process for every new product launch, aiming to embed privacy throughout engineering and product development. This describes a design process, not a guarantee that every privacy risk is eliminated.

Supporting quotations

We rely on our internal privacy team and a review process for any new product launch. We are dedicated to proactively embedding privacy throughout the product development lifecycle, from engineering to product management.

Legal Rights & Agreement Rules · Procedure

Identity and card-image verification details are provided in separate help pages

People asked to verify identity are directed to separate Identity help pages covering roles, biometrics, consent, security, collection, retention and deletion. Businesses using Identity are pointed to disclosure/privacy/review guidance. Customers asked to scan a credit card before a transaction are pointed to a separate card-image verification page. These references do not themselves supply the linked practices or procedures.

Supporting quotations

If you have been asked to verify your identity or have verified your identity using Stripe Identity, please visit the support web pages here and here to learn more about our privacy practices for Stripe Identity.
If you are a Business User that is using or intends to use Stripe Identity, please visit the support web page here for additional guidance on what you can tell your users and here and here for additional guidance on privacy considerations for your business.
If you have been asked by your merchant (i.e., a Stripe Business User) to scan your credit card before completing your requested transaction, please visit the support webpage here to learn more about Stripe’s Card Image Verification.

Not stated here

  • The linked Identity and card-image help pages are not supplied; their detailed practices and choices are not inferred.

Use & Processing · Context

Connect roles depend on the activity rather than one fixed relationship

Connect lets a third-party platform enable payment services and/or payouts. The publisher generally acts as processor on platform/Business User instructions and as controller when determining purposes and means, including identity checks, regulation, fraud/security and platform management. The responsible entity depends on individual/business location, service and purpose; the earlier entity section supplies the mapping.

Supporting quotations

Stripe Connect is a payment software your third party platform provider (Platform) may use to enable you to receive Stripe Services (including payment processing) and/or receive payouts.
Stripe may act as both a data controller and a data processor in connection with Stripe Connect. Stripe generally acts as a processor when it processes Personal Data on the instructions of a Platform or another Business User. Stripe acts as a controller where it determines the purposes and means of processing, including for identity verification, regulatory compliance, fraud prevention, security, and Stripe platform-management activities.
The Stripe entity responsible for particular processing depends on the relevant individual’s or Business User’s location, the Stripe services being provided, and the purpose of the processing.

Qualifications & exceptions

  • The Stripe entity responsible for particular processing depends on the relevant individual’s or Business User’s location, the Stripe services being provided, and the purpose of the processing.

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.

Data Access & Collection · Company practice

Custom account information may be completed from other accounts or third parties

For fraud detection and financial compliance, the publisher may fill missing address, phone, SSN, birth date, employer ID or website information using another Stripe account or a third party. A Custom account user must contact the platform or business that created the account to view, update or correct the associated information.

Supporting quotations

Stripe may leverage data we already have from one of your Stripe accounts or Stripe may fill in some of this information by receiving data from a third party. You may view the information that we are associating with your account and update or correct that information by contacting the platform or business that created your Stripe payment account.

Qualifications & exceptions

  • by contacting the platform or business that created your Stripe payment account.
Also annotated in the same passage (1)

Account & Service Control · Procedure

Platforms must handle Custom account verification and corrections

The platform is responsible for interactions, collecting verification information, building a dashboard and communication channels, and acting on requests to update or correct Custom account information. Custom account holders cannot log into Stripe themselves.

Supporting quotations

You, the Platform, are responsible for all interactions with your Custom accounts and for collecting all of the information needed to verify the Custom account-holders. Since Custom account holders cannot log into Stripe, it is up to you to build the user dashboard and communication channels. You are responsible for actioning any request by a user to update or correct their Stripe Custom account information.

Qualifications & exceptions

  • Since Custom account holders cannot log into Stripe

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.

Data Access & Collection · Company practice

Checkout promotional preferences can be collected without a completed purchase

The Promotional Emails feature collects preferences for messages from the merchant at a Stripe Checkout page. Prospective customers qualify if they start a purchase and enter contact information without deleting it before the session ends; completion of a purchase is unnecessary.

Supporting quotations

When you visit a Business User’s checkout page (that is powered by Stripe Checkout Services), the Promotional Email feature will enable Stripe to collect information about your preferences to receive promotional emails from that merchant.
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

  • 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.
Also annotated in the same passage (1)

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)

Use & Processing · Context

Promotional Emails operates at the merchant’s direction

For this feature the publisher acts as processor/service provider at the implementing Business User’s direction. The named processor is Stripe, LLC in the US and Stripe Payments Europe Limited outside the US, including Europe. A separate Privacy Policy supplies further payment-data collection details.

Supporting quotations

meaning that Stripe is acting at the direction of the Business User that has implemented this Stripe provided feature.
Stripe, LLC in the United States.
Stripe Payments Europe Limited outside of the United States, including Europe
Stripe’s Privacy Policy describes in more detail the Personal Data that Stripe collects in connection with payment transactions.

Qualifications & exceptions

  • Stripe, LLC in the United States.
  • Stripe Payments Europe Limited outside of the United States, including Europe

Not stated here

  • The linked Privacy Policy is not supplied; its additional collection details are not inferred.

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)

Account & Service Control · User right or choice

Merchants must offer and promptly honor promotional opt-outs

Messages resulting from this feature are sent by the merchant or identified sender, not Stripe. Contact that merchant to stop them; implementing merchants must provide unsubscribe/opt-out and promptly comply, or breach the publisher’s terms. Necessary purchase/support contact may continue despite a promotional opt-out. Review the merchant’s own policy for practices outside this feature.

Supporting quotations

Stripe requires that Business Users that choose to implement the Promotional Email feature also provide the option to unsubscribe or opt-out of receiving further promotional messages. It would be a breach of Stripe’s terms of service for a Business User to not promptly comply with opt-out requests.
Stripe requires that Business Users that choose to implement the Promotional Email feature also provide the option to unsubscribe or opt-out of receiving further promotional messages.
End Customers and prospective End customers should always review the privacy policy or notice of the Business Users they visit and do business with for information about the Business User’s data collection practices and purposes outside of this Stripe feature.
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

  • 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 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.

Legal Rights & Agreement Rules · Context

The publisher describes Promotional Emails as processing for the merchant

This section says the feature is not a sale of personal data: the publisher acts as processor/service provider. Contact the merchant about its own practices and applicable sale/processing rights. This feature-specific assurance does not resolve separate advertising disclosures elsewhere in this document. Business Users are referred to a separate implementation guidance page.

Supporting quotations

The Promotional Emails feature is not the sale of Personal Data. Rather, Stripe acts as a processor (or service provider) to Business Users for the Promotional Email feature.
please visit the support webpage for tips and guidance on information to share with your End Customers and prospective End Customers regarding privacy considerations in connection with the Promotional Emails feature for your business.

Not stated here

  • Linked implementation guidance is not supplied; no further merchant requirements are inferred.

Cross-references

Account & Service Control · User right or choice

Delegated Authentication may offer biometric verification and stored-card consent

Cardholders may be offered on-device biometric verification and consent to storing payment-method details for later transactions using the same card. Detailed practices and consent-withdrawal instructions are referred to separate support pages and are not supplied here.

Supporting quotations

You may be given the option to enable on-device biometric verification and provide your consent for Stripe to store your payment method details for future transactions that use the same card.

Qualifications & exceptions

  • for future transactions that use the same card.

Not stated here

  • Linked support practices and withdrawal details are not supplied.

Data Access & Collection · Permission or license

Choosing Link stores payment information for use at participating merchants

Using Link authorizes storage of payment-method information such as name, card number, CVC and expiry for purchases with participating Business Users. Other transaction data collected includes billing/shipping addresses, email and phone; payment-method data is secured using PCI-DSS standards. A non-user receiving an SMS because an inaccurate number was entered can use the linked opt-out route for deletion.

Supporting quotations

When you choose to use Link, you agree to let us store your payment method so that you can more readily make purchases through Link with Business Users of our payment processing Business Services (e.g., name, card number, cvc, and expiration date). We will also collect other Transaction Data, including billing address, shipping address, email and phone number. Your payment method data is secured using PCI-DSS standards.
Should you not have used Link and receive an SMS in error due to an inaccurate number being inserted at the authentication flow stage you can opt out here and your Personal Data will be deleted.

Qualifications & exceptions

  • Should you not have used Link and receive an SMS in error due to an inaccurate number being inserted at the authentication flow stage

Account & Service Control · User right or choice

Agentic payments use the authority you grant and may create a scoped payment token

An AI agent/platform or other agent operator may initiate purchases and payments within your authorization. When enabled, the publisher may create a tokenized credential associated with those permissions, and receive purchase instructions and contact, delivery and payment information from the operator. You may review, change or revoke authority in Link settings if connected there, or through the operator that established it.

Supporting quotations

to initiate purchases and payments on your behalf within the scope of the authorization you provide.
When you enable agentic payments, Stripe may create a tokenized payment credential associated with the permissions you have granted to the agent operator. The agent operator may provide Stripe with your purchase instructions and information needed to complete the transaction, such as your contact, delivery, and payment information.
You may review, modify, or revoke an agent operator’s authorization through your Link account settings, where the agent is connected to Link, or through the agent operator that established the authorization.

Qualifications & exceptions

  • where the agent is connected to Link, or through the agent operator that established the authorization.

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.

Account & Service Control · Procedure

Sold through Link makes Stripe merchant of record and requires an account for subscriptions

For digital products sold through Managed Payments under this brand, Stripe handles the purchase as merchant of record on the Business User’s behalf. Link provides order history, purchase management, payment/subscription tools and renewal/refund/customer support. Subscriptions require a Link account for identity verification, ongoing payments and support; separate Link policy and terms also apply.

Supporting quotations

When you see “Sold through Link,” Stripe acts as the merchant of record on behalf of the Business User.
Business Users can offer and sell their digital products using Stripe Managed Payments under the “Sold through Link” brand.
Stripe also provides additional support and order management services through Link to help you manage your orders that were Sold through Link.
A dashboard where you can see your order history, track, and manage your purchases
Tools to update payment methods or manage subscriptions
Support for renewals, refunds, or customer service
For subscriptions that are Sold through Link, you must have a Link account to ensure we can verify your identity, manage ongoing payments, and provide continuous support.

Qualifications & exceptions

  • on behalf of the Business User.

Not stated here

  • Linked Link Privacy Policy and terms are not supplied; their additional rules are not inferred.

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.

Charges & Financial Obligations · Context

Capital financing partners vary by business location

Capital provides Business User funding access and lets platforms extend offers to Connected Accounts; financing type depends on corporate structure and jurisdiction. The notice names Celtic Bank or YouLend in the US; YouLend in EU/UK; YouLend SAS/affiliates in France; YouLend GmbH/affiliates in Germany; Fundbox Australia in Australia; and Fundbox, Inc. in Canada. These are stated partners, not guaranteed eligibility.

Supporting quotations

Depending on your business's corporate structure and jurisdiction, you may be eligible for different types of financing.
financing is provided by one of our financial partners depending on where your business is located:
US: Celtic Bank or YouLend Ltd.
EU/UK: YouLend Ltd.
France: YouLend SAS and its affiliates.
Germany: YouLend GmbH and its affiliates.
Australia: Fundbox Australia Pty Ltd.
Canada: Fundbox, Inc.

Qualifications & exceptions

  • Depending on your business's corporate structure and jurisdiction, you may be eligible for different types of financing.

Not stated here

  • The linked financial-partner privacy documents are not supplied; their data practices and financing terms are not inferred.

Inference & Profiling · Company practice

Capital eligibility assessment uses existing account and financial data

Before a financing offer, the publisher evaluates Business User or Connected Account data. Potential inputs include processing volume, chargeback rate, relationship length, bank balances, transaction history and creditworthiness. This financing assessment is distinct from fraud scores described elsewhere as not evaluating creditworthiness.

Supporting quotations

In Capital for Platforms, we follow the same approach, except that we will review existing data linked to a Connected Account’s Stripe Account to assess their eligibility.
The following information may be considered prior to the offer of financing in order to determine eligibility, including:
Payment processing volume
Chargeback rate
Duration of relationship with Stripe
Bank account balances
Transaction history
Information about your creditworthiness

Cross-references

Data Access & Collection · Company practice

US Capital assessment may require additional linked financial and Representative information

US businesses may be asked to link bank accounts or business credit sources. Pre-offer processing may include business credit history and information about the business and Representatives: name, address, credit/banking/financial history and last four SSN digits. For Connected Accounts it may include off-Stripe transactions received from the platform under their agreement.

Supporting quotations

If your business is based in the U.S., you may also be asked to link additional data sources, such as business bank accounts or business credit information, in order to receive financing through Stripe Capital.
Business credit history
Information about you and your Representatives, which may include name, address, credit history, banking relationships, last four digits of a Social Security Number, and financial history.
If you’re a Connected Account, off-Stripe transaction history that we receive from your Platform, in accordance with your agreement with them.

Qualifications & exceptions

  • If you’re a Connected Account, off-Stripe transaction history that we receive from your Platform, in accordance with your agreement with them.

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

Data Access & Collection · Company practice

Authorized Capital signers may need to provide personal identity documents

A Representative authorized to sign for the company may be asked for name, ownership threshold if an owner, home address and verification document, government ID number and verifying ID, tax ID, date of birth, email and phone. Information provided for the application is shared with the regional financial partner.

Supporting quotations

may be asked to provide the following personal information as part of the application process and that information will be shared with our financial partner in your region:
Name
If Owner, Percentage Ownership Threshold
Home address, and provision of a document, such as a household bill, which verifies their home address
Government ID number, and provision of an ID document which verifies the number provided
Tax identification number
DOB
Email
Phone Number

Qualifications & exceptions

  • If Owner, Percentage Ownership Threshold

Use & Processing · Company practice

Capital processing relies on legitimate interests for verification, financial risk and model improvement

The publisher states legitimate business interests as its basis for analysis of Business User/Representative information. Purposes include identity verification for fraud, AML/KYC and reporting obligations, assessing financing risk to the publisher, partners and Business Users, and improving models to tailor financing and decrease risk to current and other Business Users.

Supporting quotations

We will process your Personal Data in accordance with our legitimate business interests.
Verify the identity of our Business Users in order to comply with fraud monitoring, prevention and detection obligations, applicable laws associated with the identification and reporting of illegal and illicit activity, such as AML (Anti-Money Laundering) and KYC (Know-Your-Customer) obligations, and financial reporting obligations.
Assess the level of financial risk to us, financial partners and to Business Users involved in offering Business Users financing.
Enhance our machine learning models to allow us to better tailor financing to, and decrease the risk to, you and other Business Users.
Also annotated in the same passage (1)

Use & Processing · Company practice

Frontier uses consent, with legitimate interests for proactive inquiries

The Frontier section states consent as a processing basis, but uses legitimate business interests where you proactively provide data to obtain answers or support. Marketing/events/surveys require permission or legal allowance and compliance with consent/opt-out rules. The general controller section says legitimate interests are balanced against rights and withdrawing consent does not affect earlier lawful processing.

Supporting quotations

We rely on consent to process your data. Where you proactively reach out to Stripe and provide your data, Stripe will process your data based on Stripe’s legitimate business interests (e.g. help answer your queries, and provide customer support).
provided that we do so in accordance with applicable law, including any consent or opt-out requirements.
Legitimate interests are balanced against individual rights. Consent may be withdrawn without affecting earlier lawful processing.

Qualifications & exceptions

  • Legitimate interests are balanced against individual rights. Consent may be withdrawn without affecting earlier lawful processing.

Not stated here

  • The linked Privacy Policy is not supplied; additional legitimate-interest terms are not inferred.
Also annotated in the same passage (1)

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).

Account & Service Control · User right or choice

Frontier marketing opt-outs and privacy rights depend on the request and jurisdiction

Marketing emails include unsubscribe links; the publisher will try to comply as soon as reasonably practicable. Other rights depend on location/law and concern data it controls. EEA/UK users can contact the DPO; EEA residents or those with Stripe Payments Europe as controller who believe GDPR applies can contact Ireland’s DPC, while UK residents can contact the ICO. California and other jurisdiction rules are referred to the separate Privacy Policy. Questions/complaints can be directed to the publisher.

Supporting quotations

If you no longer want to receive marketing-related emails from us, you may opt-out via the unsubscribe link included in such emails
We will try to comply with your request(s) as soon as reasonably practicable.
If you are a resident of the EEA or we have identified Stripe Payments Europe Limited as your data controller, and believe we process your information within the scope of the General Data Protection Regulation (GDPR), you may direct your questions or complaints to the Irish Data Protection Commission. If you are a resident of the UK, you may direct your questions or concerns to the UK Information Commissioner’s Office.
If you are a consumer located in California, please review the California Consumer Privacy Act (“CCPA”) section of our Privacy Policy.
See our privacy policy for additional jurisdiction-specific provisions.
If you have any questions or complaints, please contact us.

Qualifications & exceptions

  • We will try to comply with your request(s) as soon as reasonably practicable.

Not stated here

  • The linked Privacy Policy is not supplied; additional jurisdiction-specific rights are not inferred.

Account & Service Control · Procedure

A DPO and Quebec privacy lead are identified

The publisher has appointed a Data Protection Officer. Although this section’s email-labelled link uses an HTTPS path, the India section explicitly supplies dpo@stripe.com for DPO privacy questions. For Quebec’s private-sector personal-information law, the Global Head of Privacy is the responsible person and can be contacted at privacy@stripe.com.

Supporting quotations

Yes, Stripe has appointed a Data Protection Officer (“DPO”), who can be reached via email.
Stripe’s Global Head of Privacy is the person in charge of personal information under the Quebec Act Respecting the Protection of Personal Information in the Private Sector. You may contact Stripe’s Global Head of Privacy at privacy@stripe.com.
For privacy related questions or concerns, you may also contact Stripe’s Data Protection Officer (“DPO”) via dpo@stripe.com.

Not stated here

  • The linked HTTPS DPO contact target is not independently supplied; the email address is supported by the explicit DPO contact statement elsewhere in this saved source.
Also annotated in the same passage (1)

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.

Security & Safeguards · Company commitment

The Quebec section describes privacy protection and destruction procedures

The publisher describes policies against unauthorized access/use/disclosure, timely effective request/complaint processes, retention/destruction aligned with legal obligations and secure destruction when no longer required, defined employee responsibilities, and regular privacy training. It does not give a fixed destruction deadline here.

Supporting quotations

We are committed to protecting personal information and have established policies and procedures that govern our treatment of personal information.
policies and procedures to protect personal information in our custody and control from unauthorized access, use or disclosure.
processes to respond to data subject requests and complaints in a timely and effective manner.
a framework for the retention and destruction of personal information to ensure compliance with legal obligations, and to securely destroy personal information once no longer required.
a privacy framework that defines the roles and responsibilities for our employees with respect to the treatment of personal information.
providing our employees with regular privacy training and awareness.

Qualifications & exceptions

  • once no longer required.

Security & Safeguards · Company commitment

Security controls restrict access and record data handling

The publisher describes security/risk and asset-management programs, virtual and data access restrictions, disclosure controls during transmission/transport/storage, and audits of who entered, changed or deleted data. Access is limited by authorization and rights, rather than described as open to all personnel.

Supporting quotations

Stripe employs security controls and maintains and enforces a security program that addresses the management of security.
Stripe applies technical and organizational measures that include the following:
Virtual access control to prevent data processing systems from being used by unauthorized persons.
Data access control to ensure that persons entitled to use a data processing system gain access only to such Personal Data in accordance with their access rights, and that Personal Data cannot be read, copied, modified or deleted without authorization.
Disclosure control to ensure that Personal Data cannot be read, copied, modified or deleted without authorization during electronic transmission, transport or storage on storage media (manual or electronic), and that it can be verified to which companies or other legal entities Personal Data are disclosed.
Entry control to audit whether data have been entered, changed or removed (deleted), and by whom, from data processing systems.

Qualifications & exceptions

  • in accordance with their access rights
Also annotated in the same passage (1)

Security & Safeguards · Company commitment

Hosting providers supply physical controls alongside loss and purpose-separation controls

Third-party providers host production infrastructure and apply physical-access controls to premises/systems. Availability controls protect against accidental loss/destruction, and separation controls allow data collected for different purposes to be processed separately. The statement describes implemented controls, not risk-free storage.

Supporting quotations

Stripe relies on third party service providers to host its production infrastructure. Those third parties apply physical access control to prevent unauthorized persons from gaining access to the data processing systems available at premises and facilities (including databases, application servers, and related hardware), where Personal Data are processed.
Availability control to ensure that Personal Data are protected against accidental destruction or loss (physical/logical).
Separation control to ensure that Personal Data collected for different purposes can be processed separately.

Security & Safeguards · Company practice

Encryption is the default and dashboard two-step authentication is available

The notice states default encryption at rest/in transit, audit logs/access policies, TLS 1.2 endpoint configuration, TLS and/or SSL for HTTPS and regular infrastructure testing. Two-step authentication is available for dashboard login; the text does not say it is mandatory for every user.

Supporting quotations

By default, Stripe encrypts data at rest and data in transit.
Security controls implemented at Stripe include TLS 1.2 configuration of endpoints for data in transit, TLS and/or SSL encryption for HTTPS and regular testing of infrastructure components. Two-step authentication is available for an extra layer of security at Dashboard login.

Qualifications & exceptions

  • By default, Stripe encrypts data at rest and data in transit.

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.

Legal Rights & Agreement Rules · Company practice

DPF takes priority when applicable, with other transfer mechanisms as fallback

The notice states participation in EU-US DPF, the UK Extension and Swiss-US DPF. DPF takes precedence if multiple mechanisms apply, while alternatives are incorporated if DPF is invalidated or unavailable. Business Users can ask the publisher/account manager about DPF transfers; separate DPF policy and addendum links supply further details not reproduced here.

Supporting quotations

In case the DPF is invalidated or Stripe is otherwise prevented from relying on the DPF, we incorporate multiple transfer mechanisms to ensure that data transfers can continue. If more than one data transfer mechanism applies, the DPF takes precedence.
Stripe’s Data Transfers Addendum sets out the data transfer mechanisms that Stripe may rely on to carry out international transfers of personal data, including the EU-U.S. DPF.

Qualifications & exceptions

  • If more than one data transfer mechanism applies, the DPF takes precedence.

Not stated here

  • The linked Data Transfers Addendum and DPF policy are not supplied; their full obligations are not inferred.
Also annotated in the same passage (2)

Legal Rights & Agreement Rules · Procedure

Applicable SCCs are incorporated and transfer clauses can be found in the addendum

The publisher says it may rely on SCCs for EEA transfers and updated its addendum/agreements to include them where applicable. The separate Data Transfers Addendum is the stated place to obtain SCCs, UK and Swiss addenda; their full contractual obligations are not supplied here.

Supporting quotations

Stripe may rely on the SCCs for transfers of EEA data in our Services. We have updated our Data Transfer Addendum and agreements to incorporate the SCCs (where applicable).
You can review our Data Transfers Addendum which includes the latest data transfer mechanisms, including the SCCs, the UK addendum and the Swiss addendum here.

Qualifications & exceptions

  • (where applicable).

Not stated here

  • The linked Data Transfers Addendum is not supplied; full SCC, UK and Swiss clause terms cannot be described.

Account & Service Control · User right or choice

Privacy rights depend on location and applicable law

Potential rights include confirmation, access, correction, portability, restriction, objection, withdrawal where consent is relied on, and deletion. These are conditional rights under applicable law, not an unconditional promise that every requester has every right.

Supporting quotations

Depending on your location and subject to applicable law, you may have the following rights:
Right to confirmation of processing
Right to access
Right of rectification/correction
Right to data portability
Right to restrict processing
Right to object to processing
Right to withdraw consent (where it is relied upon)
Right to erasure/deletion

Qualifications & exceptions

  • Depending on your location and subject to applicable law, you may have the following rights:
  • Right to withdraw consent (where it is relied upon)

Cross-references

Also annotated in the same passage (5)

Account & Service Control · User right or choice

Available opt-outs and accountability rights include advertising, profiling and appeals

Subject to location/law, the notice lists targeted-advertising, certain significant-effect profiling, electronic communications, sale and California-sharing opt-outs; limiting sensitive-data use/sharing; confirmation of recipients; non-discrimination; appeals and UK GDPR complaints. This list identifies possible rights and does not remove statutory conditions or exceptions.

Supporting quotations

Depending on your location and subject to applicable law, you may have the following rights:
Right to opt-out of processing for targeted advertising
Right to opt-out from profiling for certain decisions with legal or similarly significant effect
Right to opt-out of receiving electronic communications from us
Right to non-discrimination for exercising your rights
Right to opt-out from a sale of personal information
Right to opt-out of “sharing” under California privacy law
Right to confirm the third parties or categories of third parties to which personal data has been disclosed
Right to limit the use or sharing of sensitive personal information
Right to appeal Stripe’s response to your data subject request
Right to complain under UK GDPR

Qualifications & exceptions

  • Depending on your location and subject to applicable law, you may have the following rights:
Also annotated in the same passage (5)

Account & Service Control · Procedure

Rights requests can be sent by email, form or listed physical address

The publisher accepts requests through email, its linked privacy-request form or Contact Us physical addresses. The notice also states a right to complain to the local data-protection authority if dissatisfied with its privacy practices.

Supporting quotations

To submit a request to exercise any of the rights described above, please reach out to us by email, or via our form or by physical addresses listed in Contact Us.
You have the right to complain to your local data protection authority if you are unhappy with our privacy practices.

Not stated here

  • The alternate linked Contact Us page is not independently supplied; this card relies on the contact routes expressly described in the saved document.

Inference & Profiling · Company practice

Automated tools may make or support payment decisions without manual review

Uses include services, fraud/financial-loss prevention, payment performance and processes. Examples are risk assessment, apparent funds availability, payout pauses on risk indicators, backup payment choice, authentication/retry/block/review decisions and dispute/chargeback/claim evaluation or applicable resolution. Inputs may include transactions/history, device/browser/account activity, fraud signals, business/partner information and third-party/public sources, depending on service and decision. Significant-effect decisions carry applicable legal notice/choice requirements described in the accompanying rights card.

Supporting quotations

Stripe may use automated tools to process Personal Data and make or support decisions without manual human review.
Examples of automated decisions may include:
assessing fraud or financial-loss risk associated with a payment, payout, Business User, End User, or End Customer;
checking whether sufficient funds appear to be available for a transaction;
pausing a payout where risk indicators are detected;
selecting or recommending a backup payment method;
deciding whether a transaction should be authenticated, retried, blocked, or referred for further review; and
evaluating disputes, chargebacks, or claims, including determining what information is required or, where applicable, resolving a dispute.
The information considered depends on the Stripe Service and the decision being made.
Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law.

Qualifications & exceptions

  • The information considered depends on the Stripe Service and the decision being made.
Also annotated in the same passage (8)

Account & Service Control · User right or choice

Significant-effect automated decisions have jurisdiction-dependent explanation and review rights

Where automated decisions/profiling have legal or similarly significant effects, or law otherwise requires, the publisher provides legally required notices, explanations and choices. Depending on jurisdiction these may include logic/consequences information, opt-out, human intervention/review, expressing a view, contesting a decision or appealing a response. Legal exceptions may apply; use Contact Us to exercise an applicable right. This is not a universal right to veto every automated decision.

Supporting quotations

Where automated decision-making or profiling produces legal or similarly significant effects concerning you, or where otherwise required by applicable law, Stripe will provide the notices, explanations, and choices required by that law. Depending on your jurisdiction, these may include the right to:
request information about the automated processing, including the logic involved and its significance and envisaged consequences;
opt out of certain automated decision-making or profiling;
request human review or intervention;
express your point of view;
contest a decision; or
appeal Stripe’s response to your request.
These rights may be subject to exceptions under applicable law.

Qualifications & exceptions

  • These rights may be subject to exceptions under applicable law.

Cross-references

  • qualifies (model-proposed): Radar scores can drive automated allow, block or review rules — Automated Radar rules are subject to applicable legally required notices, explanations and choices where decisions produce legal or similarly significant effects, with jurisdiction-dependent rights and exceptions.
Also annotated in the same passage (7)

Legal Rights & Agreement Rules · User right or choice

The state table lists confirmation, access and portability for nineteen states

The saved table lists these rights for California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia. Rights may differ under state law; the table is the publisher’s mapping, not independent advice on current statutory coverage.

Supporting quotations

Laws in the various U.S. states may provide different privacy rights.
Right to confirmation of processing
California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia
Right to access
California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia
Right to data portability
California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia

Qualifications & exceptions

  • Laws in the various U.S. states may provide different privacy rights.
Also annotated in the same passage (1)

Legal Rights & Agreement Rules · User right or choice

The state table lists correction for seventeen states

The saved correction row names California, Colorado, Connecticut, Delaware, Indiana, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Virginia. Iowa and Utah are not listed in this row; this is the notice’s conditional state-law mapping, not a conclusion that no other correction avenue exists.

Supporting quotations

Laws in the various U.S. states may provide different privacy rights.
Right to correction
California, Colorado, Connecticut, Delaware, Indiana, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Virginia

Qualifications & exceptions

  • Laws in the various U.S. states may provide different privacy rights.
Also annotated in the same passage (1)