Stripe Privacy Center (supplemental privacy notices)

Stripe · Official agreement

Read the agreement

17 of 266 cards in Security & Safeguards

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)

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.

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.

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;

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.

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)

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.

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)

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)

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.

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.

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.

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.

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.