Welcome to the Stripe Privacy Center
Stripe respects the privacy of everyone that engages with our platform, and we are committed to being transparent about our privacy processes and policies. We are a platform that enables millions of businesses, and in order to provide our services to our 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.
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.
We made the following types of changes:
- We included a new introduction that provides you more information about Stripe.
- We updated the policy to remove services that we no longer offer (e.g. Stripe Shop), to remove references to product brands we no longer use (e.g. Remember Me is now Link with Stripe) and to add more clarity around the descriptions of our services.
- We updated the language around the Privacy Shield for data transfers between EEA and the US and instead refer you to the Privacy Center to learn more about our cross border data transfers.
- We provided more information about privacy rights that exist in some countries where Stripe offers Services.
- We have moved the details for our contact information into the Privacy Center.
How We Collect, Disclose, and Use Personal Data
Is Stripe acting as a data controller or a data processor?
The answer is both.
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. These data processing activities include (1) providing the Stripe products and services, (2) monitoring, preventing and detecting fraudulent payment transactions and other fraudulent activity on the Stripe platform, (3) complying with legal or regulatory obligations applicable to the financial sector to which Stripe is subject, and (4) analyzing, developing and improving Stripe’s products and services. Please see this Privacy Center article for more information on Stripe’s controller activities.
Stripe is a data processor where it is facilitating payment transactions on behalf of and at the direction of a Stripe User. Our Users direct us to take payment from cardholders - Stripe is considered a processor when directed to process payments, i.e., Stripe receives instructions about whom to pay, how much to pay, when to pay.
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 Users (including some of the world’s largest companies) on this basis.
What legal basis does Stripe rely on to process personal data as a data controller?
We rely upon a number of legal grounds to enable our use of your Personal Data. In short, we use Personal Data to facilitate the business relationships we have with our Users, to comply with our financial regulatory and other legal obligations, and to pursue our legitimate business interests. We also use Personal Data to complete transactions and to provide payment-related services to our Users.
Here’s a more detailed overview of why and how we use your Personal Data.
Contractual and pre-contractual business relationships
We use Personal Data for the purpose of entering into business relationships with prospective Stripe Users, and to perform the contractual obligations under the contracts that we have with Stripe Users. Activities include:
- Creation and management of Stripe accounts and Stripe account credentials, including the evaluation of applications to commence or expand the use of our Services;
- Creation and management of Stripe Checkout accounts;
- Accounting, auditing, and billing activities; and
- Processing of payments, including fraud detection and prevention, optimizing valid transactions, communications regarding such payments, and related customer service.
We use Personal Data to verify the identity of our 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.
Legitimate business interests
Where allowed under applicable law, we rely on our legitimate business interests to process Personal Data about you. For example, we:
- Detect, monitor and prevent fraud and unauthorized payment transactions;
- Mitigate financial loss, claims, liabilities or other harm to Customers, Users and Stripe;
- Determine eligibility for and offer new Stripe products and services;
- Respond to inquiries, send Service notices and provide customer support;
- Promote, analyze, modify and improve our Services, systems, and tools, and develop new products and services, including reliability of the Services;
- Manage, operate and improve the performance of our Sites and Services by understanding their effectiveness and optimizing our digital assets;
- Analyze and advertise our Services;
- Conduct aggregate analysis and develop business intelligence that enable us to operate, protect, make informed decisions, and report on the performance of, our business;
- Share Personal Data with third party service providers that provide services on our behalf and business partners which help us operate and improve our business;
- Enable network and information security throughout Stripe and our Services; and
- Share Personal Data among our affiliates for administrative purposes.
Payment transactions and related services (Stripe as a data processor)
We use Personal Data of Customers to provide our Services to Users, including to process online payment transactions and authenticate Customers on behalf of our Users.
Marketing and events-related communication
We may send you 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, provided that we do so in accordance with applicable law, including any consent requirements.
When you visit our Sites, we (and our service providers) may use Personal Data collected from you and your device to target advertisements for Stripe Services to you on our Sites and other sites you visit (interest-based advertising), where allowed by applicable law, including any consent requirements. We do not use, share, rent or sell the Personal Data of our Users’ Customers for interest-based advertising. We do not sell or rent the Personal Data of our Users, their Customers or our Site Visitors.
What are your data controller activities?
- Providing the Stripe products and services to Stripe users, including determining the third parties (banks and payment method providers) to be utilized;
- Monitoring, preventing and detecting fraudulent payment transactions and other fraudulent activity on the Stripe platform;
- Complying with legal or regulatory obligations applicable to the financial sector to which Stripe is subject, including applicable anti-money laundering screening and compliance with know-your-customer obligations; and
- Analyzing, developing and improving Stripe’s products and services.
As a Stripe User and as a data controller, what does GDPR mean for me?
Take a look at our GDPR Guide.
In addition, as data controller, you are responsible for the relationship with the data subject (i.e., your end customer). You may instruct a third party (like Stripe) to process the data but it is your job to set the purpose (or objectives) and legal basis for the processing.
All third parties have to abide by the terms agreed by the data controller and the data subject. To be sure of this, the data controller must have Data Processing Agreements (i.e., DPAs) with each one. Our DPA has been designed to serve this purpose for you; it is strongly aligned with payment transactions, so it should establish that you are compliant with GDPR from a payments perspective.
Who are Stripe’s sub-processors and how are they vetted?
Please see our service providers page where we have a list of our most common sub-processors. 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 potential vendors are vetted and approved through Stripe’s security review process before we begin using their services.
I heard that Stripe is collecting additional information about my account from a third party and/or my other Stripe account. Why is Stripe collecting this information?
In addition to its sub-processors, what other third parties does Stripe share information with?
When we work with service providers in our capacity as a data processor for our User’s personal data, the General Data Protection Regulation (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. These third parties are disclosed on our Stripe Service Providers List.
In addition to Stripe’s sub-processors, we may also share user onboarding data and payment instrument information with third party business partners when this is necessary to provide our services to our users. We do so, for example, for the purposes of offering payment processing services to our users or facilitating payment settlements.
Third parties to whom we may disclose personal data for this purpose are banks, payment method providers and payment processors, including, but not limited to, the following entities:
- American Express Payment Services Limited and American Express Payments Europe S.L.
- Banking Circle S.A.
- Barclays Bank PLC
- Credit Mutuel Arkea and Arkea Banking Services
- Currence iDEAL B.V.
- Klarna AB
- Mastercard Europe S.A.
- Polski Standard Płatności
- PPRO Financial Ltd.
- Swisscard AECS GmbH
- Visa Europe Limited
The data shared with payment method providers will depend on the payment method(s) enabled on the User’s account.
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. Depending on the enabled payment method(s), personal data may be transferred to the jurisdiction(s) of the respective payment method(s).
Data Processing Agreement
What is a Data Processing Agreement (DPA) and how can I get one with Stripe?
A Data Processing Agreement is a contract between a data controller and a data processor, which describes the roles and responsibilities of the parties when personal data is processed. Article 28 of the GDPR sets out a number of requirements that a Data Processing Agreement must satisfy in order to be compliant with European data privacy law. We have made a Data Processing Agreement available to Stripe Users. When you are logged in to your Stripe account you can review and accept the Stripe DPA.
Information about Stripe Products
How do you implement Privacy by Design at Stripe?
Privacy by design aims at building privacy and data protection up front, into the design specifications and architecture of information and communication systems and technologies, in order to facilitate compliance with privacy and data protection principles. We rely on our internal privacy team and a review process for any new product launch. We are dedicated at every level of product development to making privacy a key consideration – from engineering to product management. This helps ensure that people can trust the Stripe products that they enjoy every day.
If you have been asked to verify your identity or have verified your identity using Stripe Identity, please visit the support webpages here and here to learn more about our privacy practices for Stripe Identity. Or you can jump to the specific topics linked here:
- Understanding Stripe Identity
- Biometric verification
- Consent to use my identity information
- Security of my identity data
- What data is collected
- Identity data retention
- Stripe’s role in controlling and processing identity data
- How I delete my identity data
Business That Requested Verification
If you are a business that is using or intends to use Stripe Identity, please visit the support webpage here for additional guidance on what you can tell your users and here for additional guidance on privacy considerations for your business.
Stripe Connect At a Glance
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.
Data Controller/ Data Processor
Stripe acts as both a data controller and data processor for the Platform. The Stripe entity that acts as data controller/ data processor for data processed in Europe is Stripe Payments Europe Limited.
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 Stripe User or Platform will transfer personal data to Stripe. The personal data exchanged between Stripe and the User/Platform may be transmitted to verification agencies and 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 credit 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.
I am a U.S. user with a Custom connected account. Does Stripe also collect information about my Custom connected account from a third party?
What responsibilities do Connect platforms with custom accounts have to allow their users to update or correct information associated with their accounts?
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.
I am a U.S. user with a Custom connected account. Will data collected from a third party be visible to my customers?
Card networks and issuers use statement descriptors to identify payments on a cardholder’s bank statement. Statement descriptors usually include information about the payment, such as the name and phone number of the seller. However, the exact information displayed is ultimately up to a cardholder’s bank. 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.
What are Stripe ACS, Transaction Authentication, and Behavioral Biometrics?
What is Stripe ACS?
Stripe ACS is Stripe’s transaction authentication solution for card issuers (e.g. banks). Stripe ACS helps card issuers to authenticate transactions of cardholders when they are making payments online using their cards.
What is behavioral biometrics?
Behavioral biometrics is an innovative technology that can be used for the purpose of preventing fraud and identifying legitimate transactions. Behavioral biometrics leverages a combination of personal data and device characteristics to distinguish between legitimate customers and fraudsters or bots.
How is behavioral biometrics data collected and used in Stripe ACS?
This processing is designed to verify a cardholder’s identity based on their behavioral biometric data which is modeled based on data collected during each authentication attempt.
This type of transaction authentication will typically observe interactions within a system or device to verify a cardholder’s identity for the purposes of authenticating online payments. The following elements may be processed during the authentication process:
- Length of text field inputs
- Location of mouse pointer
- Modifier key details (e.g. CTRL, SHIFT)
- Timing and location of mouse clicks
- Timing and location of touch events
- Timing between keystrokes
- Window scroll position
Purpose of processing and Stripe’s role
Stripe may process biometric data relating to cardholders in order to assist card issuers to authenticate payment transactions. This is done as part of Stripe’s payment transaction authentication services provided to card issuers (including for the purposes of meeting Strong Customer Authentication requirements).
As part of providing this authentication services to card issuers, Stripe engages with a third party provider, Mastercard, which also acts as a data controller. See Mastercard’s Privacy Notice for details on Mastercard’s processing activities in this context.
Customers rights and choices
Upon initiating a transaction, cardholders will have the option of providing their consent to processing their behavioral biometrics data as part of the transaction authentication flow. This will be presented to the cardholder during the checkout flow on the merchant’s website or app when authentication is requested from the card issuer. Cardholders will have the option to withdraw their consent during each subsequent transaction flow.
To withdraw consent outside of a transaction flow, you can email email@example.com with the subject matter line “Stripe ACS - withdraw consent”. In your email to withdraw consent, please provide: (a) the first 6 digits of your card number as this enables Stripe to identify your issuing bank (please do not provide any digits other than the first 6 digits); and (b) the phone number (including the country code) registered with your bank account that is used for one-time passcodes.
We will action this withdrawal request as soon as possible after it is verified, but please note that this can take up to 10 working days as we may need to verify the request with your card issuer. You may also contact the card issuer in order for the issuer to implement this withdrawal of consent by engaging with Stripe.
Promotional Emails Feature
For customers and prospective customers of our Merchant Users
What is the Promotional Emails feature?
Promotional Emails is a feature that gives merchants (Stripe Users) who use “Stripe Checkout” services a new tool to enable sending email promotional content to their customers and prospective customers. When you visit a merchant’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.
Promotional email preferences are collected whether or not you complete the purchase or are just a prospective customer. “Prospective customer” means you visited a merchant site and expressed an intent to make a purchase by starting a purchase on the merchant’s checkout page, but did not complete that purchase during that session. To be a “prospective 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.
If you, prospective customer, indicate permission to receive news and personalized offers by virtue of the opt-in/opt-out checkbox on your merchant’s checkout form, the following personal data is provided to your merchant so that your merchant 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).
What is Stripe’s role (Data Processor/Controller) in the processing of my Personal Data?
For the Promotional Emails feature, Stripe acts as a data processor or service provider, meaning that Stripe is acting at the direction of the merchant that has implemented this Stripe provided feature. The Stripe entity that acts as a data processor for personal data is:
- Stripe Inc. in the United States.
- Stripe Payments Europe Limited outside of the United States, including Europe.
What Personal Data Is Stripe Collecting?
What Personal Data is Shared by Stripe with the Merchants I use?
With the Promotional Emails feature:
- If you are a prospective customer (you start a purchase with your merchant on their checkout form but do not complete that purchase), the personal data that we share with your merchant depends on the following:
- If you have not inputted any personal data into your merchant’s checkout form, then we will not share any personal data with that merchant.
- If you have inputted personal data into your merchant’s checkout form:
- If the checkbox for receiving news and personalized offers is not enabled when you leave your merchant’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 merchant’s checkout session, we will share the following information with that merchant:
- Email (if provided by you).
- Items in your cart with that merchant (if any).
Does Stripe share my personal data with other Merchants?
How do I stop promotional emails from a merchant?
Any offers or promotional emails that you receive as a result of a merchant’s use of the Promotional Emails feature are sent by merchants (or others identified in the message), and not by Stripe. We think that you may find value in receiving these emails, but if you do not, please contact the merchant you are receiving the messages from. Stripe requires that merchants 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 merchant to not promptly comply with opt-out requests.
How Does the Data Collection and Transfer Work?
How do I stop the sale of my personal data in connection with this feature?
Stripe requires that merchants 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 merchant to not promptly comply with opt-out requests.
How to Use this Service as a Merchant
If you are a business that is using or intends to use Stripe’s Promotional Emails feature, please visit the support webpage for tips and guidance on information to share with your customers and prospective customers regarding privacy considerations in connection with the Promotional Emails feature for your business.
Linked Financial Accounts
If you are a 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. Or you can jump to the specific topics linked here:
- Linking my financial account and consent
- Data collected, stored, and shared from my linked account
- How Stripe accesses data from my linked account
- Relationship between Stripe and its service providers
- Data security
- Who can access data from my linked account and for what purposes
- Who will obtain my login credentials
- Requesting disconnection or data deletion
- Correcting my financial account information
Data Protection Officer
Does Stripe have a Data Protection Officer (DPO)?
Yes, Stripe has appointed a DPO and they can be reached via firstname.lastname@example.org.
International Data Transfers
The detail below is provided for informational purposes. It is not intended to provide legal advice. Stripe urges Users to consult with counsel to familiarize themselves with the requirements that govern their specific situations.
How is Stripe dealing with international data transfers?
On 4 June 2021, the European Commission adopted a new set of Standard Contractual Clauses (SCCs) for cross-border data transfers. SCCs are a transfer mechanism (in the form of a legal contract) used by Stripe to provide a legal mechanism to transfer EU personal data outside of the EEA/UK. These are required under EU data protection law (known as the GDPR) and are incorporated into our agreements.
These modernised SCCs cover data transfers from controllers or processors in the EU/EEA (or otherwise subject to the GDPR) to controllers or processors established outside the EU/EEA (and not subject to the GDPR) and replace the three sets of SCCs that were adopted under the previous Data Protection Directive 95/46.
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. Stripe’s measures include the updated EU Commission’s Standard Contractual Clauses (SCCs) to accommodate international data transfers.
Stripe respects the privacy of everyone that engages with our products and services, and 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 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.
Stripe applies technical and organizational measures that include the following:
- 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.
- 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.
- 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.
By default, Stripe encrypts data at rest and data in transit. We further protect your data with tools like audit logs, access management policies and certifications as described on our Payments page in the section “Security and compliance at the core”. 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.
We no longer rely on the Privacy Shield as a transfer mechanism for data transfers given EU-U.S. Privacy Shield and Swiss-U.S. Privacy Shield are no longer valid as a result of the Schrems II decision issued by the European Court of Justice on July 16, 2020. We do continue to commit to the principles of the Privacy Shield Framework as it can still provide privacy protections to users.
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. We are committed to ensuring that our users’ data can continue to flow freely between the EU and the U.S., and we will continue to partner with regulators, industry groups and similarly situated companies to make sure our users’ needs are met.
If you have any questions, please contact us.
How do the European Commission’s new Standard Contractual Clauses impact my organization?
SCCs are legal contracts entered into between parties that are transferring EEA personal data outside of the EEA. At present Stripe relies on the existing SCCs for transfers of EEA data in our services. We have updated our agreements to implement the new SCCs. Users can enter into the new SCCs with Stripe if they wish. Please contact us or your account manager for more detail.
Your Rights and Choices
Can I turn off tracking and advanced fraud signals?
Your web browser may allow you to manage your cookie preferences, including deleting or disabling Stripe cookies. 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 that integrated with Stripe. If a business seeks to disable this data collection there are instructions to do so through Stripe’s docs. You can take a look at the help section of your web browser or follow the links below to understand your options for disabling cookies.
You can learn more about how businesses can disable collection of advanced fraud signals in our documentation for disabling advanced fraud detection.
How do I delete my account?
You can close your Stripe account from the Settings page on the Dashboard. You can read more about that on our support page: Close a Stripe account.
Please be aware that we will delete some, but not all, of the information that we hold, for the reasons explained below.
How do I delete my Custom Connect account?
If you are a Custom Connect account User, your account is managed by a Platform User of Stripe. They are the party responsible for managing payments for you and responding to your query, therefore we recommend reaching out to them for assistance.
How do I delete my Express Connect account?
If you are an Express Connect account User, your account is managed by a Platform User of Stripe. They are the party responsible for managing payments for you and responding to your query, therefore we recommend reaching out to them for assistance.
Cookies & Other Technology
Stripe Cookie Labels
|Stripe Cookie Facts: Stripe.js.com|
|This cookie is set for fraud prevention purposes. Fraud detection uses technology that helps us assess the risk associated with an attempted transaction that is enabled on the Stripe User’s website or the application that collects information.|
|Total Number of Cookies||3|
m.stripe.com (called _guid/ m cookie)
|Advertising||Not used for advertising purposes or sold to third parties||-|
|Stripe Cookie Facts: Atlas|
|These cookies allow Stripe to better track various activities when using Atlas (e.g. marketing campaigns or community forum logins).|
|Total Number of Cookies||5|
|Advertising||Not used for advertising purposes or sold to third parties||-|
|Stripe Cookie Facts: Connect Accounts|
The lsession cookie allows Stripe Connect customers to onboard to an Express account and to visit the Express dashboard.
The connect_locale cookie remembers the language chosen by a user during their session.
|Total Number of Cookies||2|
|Necessary||lsession||28 days or up to 1 year on mobile|
|Advertising||Not used for advertising purposes or sold to third parties||-|
|Stripe Cookie Facts: Stripe Checkout Accounts|
This cookie is set for customers that choose to have Stripe remember their payment method details. A customer visiting Stripe Checkout (checkout.stripe.com) may select a checkbox to save their payment information for future Stripe Checkout transactions. A cookie is set only after the customer passes an authentication step during the subsequent Stripe Checkout transaction. This cookie is necessary to enable the Stripe Checkout functionality if the customer has selected to be remembered. See below for additional detail.
The cookie’s only purpose is to indicate that the customer has been authenticated for a specific browser and device combination. The cookie payload is a randomly-generated string.
|Total Number of Cookies||1|
|Advertising||Not used for advertising purposes or sold to third parties||-|
What is Stripe.js?
For example, fraudsters and bots are less likely to spend time on different pages, which we’re able to detect and use as a signal in stopping fraud.
When you visit a site that uses Stripe, this fraud prevention could appear in a privacy report or tracker list in your web browser.
While you might see Stripe in a tracker list, we’re not building an individual tracking profile on you. Stripe doesn’t—and won’t—share or sell this data to advertisers.This data is securely exchanged between the following Stripe-controlled hosts:
What are advanced fraud signals?
Stripe’s advanced fraud detection looks at signals from a customer’s device characteristics and user activity indicators, such as quickly copy and pasting—things that bots or fraudsters would do, not legitimate customers. These signals are highly indicative of fraud and power Stripe’s fraud prevention systems, such as Radar. 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.
Why are advanced fraud signals not ad tracking?
Stripe only uses these advanced fraud detection signals to enable secure payments and prevent fraud. We don’t use this data to build individual profiles or share or sell it to third-party advertisers.
How does Stripe remember payment method details for Stripe Checkout?
When a customer makes a purchase via a merchant that enables Stripe Checkout (checkout.stripe.com), the customer can ask Stripe to remember their payment method details, such as credit and debit card details. A customer makes this choice by selecting a checkbox that is displayed in the Stripe Checkout user interface, and then entering a phone number when prompted. If an individual chooses to be remembered, Stripe will remember the customer’s email address, phone number and payment method details for future Stripe Checkout transactions.
If the customer enters their email address during a future Stripe Checkout transaction, Stripe will authenticate the customer by sending the customer a One Time Passcode (OTP) via an SMS message. If the customer correctly enters the OTP, Stripe will set a cookie in the customer’s browser, indicating that the customer has been authenticated. If the customer does not enter the OTP, or elects the “log out” option in the window that requests the OTP, then no cookie is set.
Once the cookie is set, the customer may make “1-click” purchases in Stripe Checkout, which means that Stripe will automatically populate the customer’s saved information into Stripe Checkout on their behalf, and use the information to complete the transaction.
A cookie is only stored in a specific browser on a specific device. If a customer wishes to make 1-click purchases in a different browser or on a different device, they must go through the OTP authentication process for the new browser/device combination.
The cookie expires after 90 days, at which point in time it will be necessary for the customer to re-complete the OTP process. The customer may also proactively remove the cookie by clearing cookies in their browser or by selecting the “log out” option when this option is presented in Stripe Checkout.
If a customer no longer wishes for Stripe to remember their payment method details for future Stripe Checkout transactions, the customer may use the self-service deletion tool. Alternatively, the customer may also contact Stripe support to make this request.
The description above describes how a customer may control how their information is stored and used for Stripe Checkout transactions. However, this does not affect the other contexts in which Stripe may store and use customer information. In particular, Stripe may store and use such information as described elsewhere on this page - including for purposes such as for advanced fraud detection.
If you’d like to send us physical mail, please send to:
510 Townsend Street
San Francisco, CA 94103, USA
Attention: Stripe Legal
Stripe Payments Europe Limited
1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland
Attention: Stripe Legal