Stripe Privacy Center (supplemental privacy notices)

Pika · Official agreement

Read the agreement

41 of 266 cards in Legal Rights & Agreement Rules

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.

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.

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.

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)

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)

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.

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)

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)

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.

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.

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.

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

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.

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.

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.

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)

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)

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.

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.

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)

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)

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

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.

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)

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.

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.

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

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.

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)