Non-Stripe transaction history may be imported or obtained with financial-account consent
Business Users can import external data in the dashboard to consolidate revenue. Separately, the publisher may obtain financial-account transactions with consent. The linked pages are referrals; they do not supply further collection or storage terms here.
Supporting quotations
Stripe enables the Business User to import non-Stripe data through the Stripe Dashboard to consolidate their revenue data in one place.
Separately, Stripe may also obtain your account transactions from your financial account with your consent.
Qualifications & exceptions
with your consent.
Data Access & Collection · Company practice
Frontier collects supplied communications and engagement data
Frontier facilitates carbon-removal purchases through an advance market commitment. Its collection includes information voluntarily supplied through tickets, email, social media, surveys and calls, including email/name, calling number and chosen message contents. It also collects event registration, attendance/viewing and interactions with personnel. The separate Privacy Policy may add details not supplied here.
Supporting quotations
It facilitates purchases from high-potential carbon removal companies on behalf of buyers.
We will collect any information you choose to provide to us, for example, through support tickets, emails or social media.
We will also collect your engagement data such as your registration for, attendance of, or viewing of Stripe events and other interaction with Stripe personnel.
Not stated here
The linked Privacy Policy is not supplied; additional Frontier practices are not inferred.
Data Access & Collection · Restriction or exception
Disabling cookies does not disable advanced fraud signals
Browsers may allow cookie deletion/disabling, which can impair site/service features. Advanced fraud-signal collection continues despite cookie disabling; the integrating Business User controls it and can consult the publisher’s linked disabling instructions. This is not an End Customer browser opt-out of all fraud collection.
Supporting quotations
If you choose to disable cookies, keep in mind that some features of our Site or Services may not operate as intended. Disabling cookies will not disable the collection of advanced fraud signals, which we use to prevent fraud on Stripe. The collection of this data is controlled by the Business User that integrated with Stripe.
You can learn more about how businesses can disable collection of advanced fraud signals in our documentation for disabling advanced fraud detection.
Qualifications & exceptions
The collection of this data is controlled by the Business User that integrated with Stripe.
Not stated here
The linked advanced-fraud disabling instructions are not supplied; implementation steps are not inferred.
Cookie purposes and placement vary by service, relationship and domain
Cookies/similar technology support functioning, fraud/terms enforcement, Visitor engagement analysis, advertising where allowed, and service/site improvement and personalization. Different cookies apply on public Stripe/Link sites, dashboards/settings and payment pages; cookies change as services develop. Full details are referred to a separate Cookie Policy.
Supporting quotations
We use cookies and similar technologies to (1) ensure that our Services function properly, (2) prevent and detect fraud and violations of our terms of service, (3) understand how Visitors use and engage with our Site, (4) advertise our products and Services, where allowed
Depending on your relationship with Stripe and the domain you are visiting, different cookies apply.
Please be mindful that we change the cookies periodically as we improve or add to our Services.
Qualifications & exceptions
where allowed
Depending on your relationship with Stripe and the domain you are visiting, different cookies apply.
Not stated here
The linked Cookie Policy is not supplied; full cookie inventories and lifetimes are not inferred.
Data Access & Collection · Company practice
Stripe.js also supports remembered Link checkout and implementation analytics
Technology such as pay_sid, link.auth_session_client_secret and elements_session remembers users across merchant checkouts and collects Link implementation analytics. Merchants should review cookies/data and consult counsel on customer disclosure and banners. Product configuration determines cookies, and the notice says elements_session analytics is set only in some US states. The fraud-data advertising restriction should not be generalized to every cookie purpose.
Supporting quotations
Stripe also uses the Stripe.js library to implement cookies and similar technology such as `pay_sid`, `link.auth_session_client_secret`, and `elements_session` to enable Link to remember users’ information for faster checkout across Stripe merchant sites and to collect analytics related to Link’s implementation on checkout pages.
You should regularly review the Stripe cookies that are placed on your website and other data collected by Stripe.js. You should consult your counsel regarding how best to disclose this data collection to your customers, including by updating your cookie banner
for the avoidance of doubt, the elements_session analytics cookie is only set in some US states
The specific cookies used by stripe.js depend on your configuration with the related Stripe products.
Qualifications & exceptions
the elements_session analytics cookie is only set in some US states
The specific cookies used by stripe.js depend on your configuration with the related Stripe products.
The cookie table maps three fraud cookies to Radar
The product overview identifies m, __stripe_mid and __stripe_sid as Fraud Prevention cookies used with Radar to assess attempted-transaction risk. These categories describe function rather than a legal exemption from cookie requirements.
Supporting quotations
Below is an overview of the specific cookies associated with each product and their respective functions for Embeddable Checkout, Elements, Radar, and Link.
m
Fraud Prevention
Set for fraud prevention purposes and helps us assess the risk associated with an attempted transaction.
Radar
__stripe_mid
Fraud Prevention
Set for fraud prevention purposes and helps us assess the risk associated with an attempted transaction.
Radar
__stripe_sid
Fraud Prevention
Set for fraud prevention purposes and helps us assess the risk associated with an attempted transaction.
Radar
Data Access & Collection · Company practice
Authentication cookie functions differ by product
pay_sid provides logged-in Link purchasing on merchant sites and is listed for Link, Embeddable Checkout, Checkout and Elements. __Host-LinkSession stores consumer credentials for one-click checkout with Link/Elements. link.auth_session_client_secret provides logged-in Stripe-hosted payment and Crypto Onramp experiences and is listed for Link. The table does not state their lifetimes.
Supporting quotations
pay_sid
Authentication
Provide a logged-in experience when a consumer uses link.com to make purchases on a merchant site.
Link, Embeddable Checkout, Checkout & Elements
__Host-LinkSession
Authentication
Stores consumer credentials to provide a one-click payment experience at checkout.
Link & Elements
link.auth_session_client_secret
Authentication
Provide a logged-in experience when a consumer uses Stripe-hosted payment UIs to make purchases and Crypto Onramp to purchase crypto.
Link
Data Access & Collection · Restriction or exception
elements_session analytics measures product changes only in some US states
The table lists elements_session for analytics in Embeddable Checkout, Elements and Link, measuring product-change results and performance. Although the row says US-only, the surrounding text narrows it to some US states; product configuration also determines which cookies are used.
Supporting quotations
elements_session
Analytics
The `elements_session` US-only cookie allows us to measure the result of changes we make to the Stripe Elements product and ensure that the performance of the product continues to improve over time.
Embeddable Checkout, Elements & Link
the elements_session analytics cookie is only set in some US states
The specific cookies used by stripe.js depend on your configuration with the related Stripe products.
Qualifications & exceptions
the elements_session analytics cookie is only set in some US states
The specific cookies used by stripe.js depend on your configuration with the related Stripe products.
Fraud and security data can come from users, financial parties and third parties
For fraud prevention and security, information may be collected from Business Users, End Customers, End Users, financial parties and sometimes third parties. Examples include transaction amounts, shipping addresses and dates, plus device and activity signals used to identify bad actors or bots.
Supporting quotations
To prevent fraud and strengthen our security, we may collect information from Business Users, End Customers, End Users, financial parties, and in some cases third parties. For example, we collect and analyze information that helps us identify bad actors and bots, including both transactional data (such as amount, customer shipping address, date, and so on) and advanced fraud detection signals (device and activity signals).
Qualifications & exceptions
To prevent fraud and strengthen our security
Data Access & Collection · Company practice
Risk services may collect registration and login behavior before payment
On platforms that enable the publisher’s risk services, registration or login may produce device, browser, IP, activity and interaction signals. These detect fraudulent registrations, account takeover, bots, multi-account abuse and other potentially harmful activity before payment. The implementing Business User or platform must provide notices and obtain permissions required by applicable law.
Supporting quotations
Stripe may also collect device and behavioral signals when an individual registers for or logs into an account on a platform that has enabled Stripe’s risk services. These signals may include information about the individual’s device, browser, IP address, activity, and interactions with the registration or login flow.
Stripe uses these signals to detect fraudulent registrations, account takeovers, bots, multi-account abuse, and other potentially harmful activity before a payment is initiated. The Business User or platform that implements these services is responsible for providing any notices and obtaining any permissions required by applicable law.
Qualifications & exceptions
on a platform that has enabled Stripe’s risk services.
The Business User or platform that implements these services is responsible for providing any notices and obtaining any permissions required by applicable law.
Data Access & Collection · Company practice
The publisher does not collect device GPS data but may derive location from IP addresses
Although devices can collect GPS-based precise location, the publisher says it does not collect GPS data from devices or browsers. Depending on services and implementation, cookies and similar technologies collect information including IP addresses, and site visits collect IP addresses. End Customer IP-derived location, including approximate latitude/longitude, may be used to detect fraudulent transactions.
Supporting quotations
Devices such as mobile phones or computers may collect precise location data using GPS technology. Stripe does not collect GPS data from devices and browsers.
Depending on the Services you use and the Business Users’ implementation of our Business Services, we will collect information (including IP addresses) through cookies and similar technology. We will collect your IP address when you visit our Sites.
Stripe may use location information, including approximate latitude and longitude, derived from End Customers IP addresses to detect potentially fraudulent transactions.
Qualifications & exceptions
Depending on the Services you use and the Business Users’ implementation of our Business Services
derived from End Customers IP addresses to detect potentially fraudulent transactions.
Not stated here
The separate Cookie Policy is not supplied here; its full rules and choices cannot be determined from this passage.
Outside providers supply approximate visitor location for marketing
Third parties such as MaxMind provide approximate country, city or state information to help locate website visitors for marketing, for example invitations to local events. This is distinct from the statement that device GPS data is not collected.
Supporting quotations
We also receive approximate location information (such as country, city or state) from third party providers such as MaxMind to help us determine the approximate location of Visitors to our website for marketing purposes (for example, inviting you to local Stripe events).
Qualifications & exceptions
approximate location information (such as country, city or state)
Not stated here
MaxMind’s linked privacy-policy text is not supplied here, so its independent practices are not described.
Data Access & Collection · Company practice
Financial Connections collects bank details according to consent and permissions
With consent, Financial Connections links a financial account to a Business User’s product or service. Depending on permissions and the requested service, collection may include account/routing numbers, type and ownership; current/available balances; and transaction amounts, dates, merchant names and categories. In some cases the publisher or provider also processes connection credentials.
Supporting quotations
With your consent, Financial Connections allows you to link a financial account to a Business User’s product or service. Depending on the permissions you grant and the service you request, Stripe may collect account information such as your account number, routing number, account type, and ownership information; current and available balances; and transaction history, including transaction amounts, dates, merchant names, and categories. In some cases, Stripe or its service provider may also process credentials used to connect to your financial institution.
Qualifications & exceptions
Depending on the permissions you grant and the service you request
In some cases, Stripe or its service provider may also process credentials used to connect to your financial institution.
German Business User identity checks may use infoscore information
Through service providers, the publisher may use information from infoscore Consumer Data GmbH to verify German Business Users’ identities. The linked provider information is separate.
Supporting quotations
Stripe, through its service providers, may use information from infoscore Consumer Data GmbH to verify the identity of Stripe Business Users in Germany.
Not stated here
The linked infoscore information is not supplied; its independent processing terms remain unknown.
Data Access & Collection · Company practice
Business prospecting data includes detailed professional and company information
The third-party-data notice lists full names, business emails, direct phones, professional social profiles, business addresses, company metadata such as name/registration/size/domain, roles and titles, industry and professional history. Sources include Cognism, ZoomInfo, Clearbit (API Hub), Crunchbase, Clay Labs, PitchBook, infoAnalytica, People Data Labs, Apollo.ai GmbH, Dealroom.co, corporate registers and public online sources. Those providers are independent controllers; contact them directly for removal from their databases.
Supporting quotations
Categories of Personal Data Obtained: We process granular categories of Personal Data, including full name, business email address, direct phone number, professional social media profiles, business physical address, company metadata (such as company name, registration number, size, and domain), professional role and title, industry sector, and professional history.
Data Sources: We collect Personal Data from third-party providers, including Cognism Limited, ZoomInfo Technologies Inc., API Hub, Inc. (Clearbit), Crunchbase Inc., Clay Labs Inc., PitchBook Data, Inc., infoAnalytica, Inc., People Data Labs, Inc., Apollo.ai GmbH, and Dealroom.co, as well as publicly available corporate registers and online sources. These third parties operate as independent data controllers. If you wish to be removed from their databases, please contact them directly.
Qualifications & exceptions
These third parties operate as independent data controllers. If you wish to be removed from their databases, please contact them directly.
Data Access & Collection · Company practice
Calls may be recorded or transcribed, with notice and a qualified choice
Voice/video calls may be recorded or transcribed, including through Zoom, Salesloft or AI transcription tools. Recording is disclosed at the start; unless recording is legally required, the publisher asks for consent and/or offers a chance to decline. Recordings serve purposes stated at the start, typically quality and training. Applicable rights are available; a requested copy may be redacted audio or a redacted transcript where appropriate and legally permitted.
Supporting quotations
In some situations, we may record and/or transcribe voice or video calls we have with you. At the start of the call, we disclose the fact that a call is being recorded and, unless we are legally required to record the call, will ask for your consent to record the call and/or offer you the option to decline the call being recorded. We may use third-party systems to record and/or transcribe calls, including Zoom and Salesloft. In some cases, transcripts are generated by AI tools.
The call recordings will be processed for the purposes stated at the start of the call, typically for quality and training purposes, and in accordance with Stripe’s Privacy Policy.
In the event that you request a copy of the recording, Stripe may provide you with a redacted copy of the recording, or a (redacted) transcript of the recording, where appropriate, and as permitted under applicable law.
Qualifications & exceptions
unless we are legally required to record the call
for the purposes stated at the start of the call
where appropriate, and as permitted under applicable law.
Not stated here
The linked Privacy Policy is not supplied here; its detailed request procedures are not described.
Phone verification may use carrier account and device data
Identity checks may support legal compliance, fraud prevention or Business Users you transact with, including whether your phone matches other supplied details. Third-party providers may assist. If available, your carrier may disclose account/device information to the publisher or its providers during the business relationship to identify you or your device, prevent fraud and for uses described in the separate Privacy Policy.
Supporting quotations
One of the data points we may consider for these purposes is whether your phone number is associated with the other information you have provided while seeking services from us or our Business Users.
We may rely on third-party services providers to assist us in performing such verification checks. In particular, your wireless carrier may disclose information about your account and your wireless device, if available, to Stripe or our service providers for the duration of your business relationship, to help us identify you or your wireless device, to prevent fraud, and as otherwise described in our Privacy Policy.
Qualifications & exceptions
if available
for the duration of your business relationship
Not stated here
The separate Privacy Policy is not supplied; its additional carrier-data uses cannot be inferred.
Data Access & Collection · Company practice
End Customer transaction data can arrive before a purchase is completed
For merchant payment, tax and billing services, the publisher receives End Customer transaction information for payments, cart-reminder activity, refunds, purchase starts and other transactions, with sources depending on integration. Clearly listed fields include name/email, billing/shipping, card/bank/image details, merchant/location, amount/date and merchant transaction history. The source’s phrase “some information about what you have collect” is incomplete; it does not clearly identify an additional data category. The table cites financial/regulatory obligations and required BNPL consent.
Supporting quotations
If you are an End Customer, when you make payments to, send shopping cart reminders, get refunds from, begin a purchase or otherwise transact with a Business User through Stripe’s Services or a Stripe-provided device, Stripe will receive your transaction information. Depending on how the Business User has integrated our Business Services, we may receive this information directly from you, the Business User or another service provider to you or the Business User.
Your name, email, billing and/or shipping address, payment method information (such as credit or debit card number, bank account information or payment card image), merchant and location, purchase amount, date of purchase, and in some cases, some information about what you have collect
We may also receive your transaction history with the Business User.
Our legal obligations in respect of our financial and regulatory obligations.
We rely on consent where required for BNPL pre-qualification or disclosure.
Provide our Services to Business Users, including to process online payment transactions or in-person checkout, to calculate applicable tax, to invoice and bill, and to calculate their revenue.
Qualifications & exceptions
Depending on how the Business User has integrated our Business Services
We rely on consent where required for BNPL pre-qualification or disclosure.
Not stated here
The incomplete source phrase does not establish what additional purchase information was intended; no missing words or category are inferred.
End Customer data categories include unsubmitted checkout fields
The merchant-services row expressly includes information typed into a checkout field even when it is not ultimately submitted to the Business User. The row concerns payment, tax, billing and revenue services and lists financial/regulatory legal duties plus BNPL consent where required; it does not say completing the purchase is necessary for this category to be processed.
Supporting quotations
Transaction-Related Information / Purchase Interests. Information typed into a checkout field that is not ultimately submitted to the Business User.
Provide our Services to Business Users, including to process online payment transactions or in-person checkout, to calculate applicable tax, to invoice and bill, and to calculate their revenue.
Our legal obligations in respect of our financial and regulatory obligations.
We rely on consent where required for BNPL pre-qualification or disclosure.
Qualifications & exceptions
We rely on consent where required for BNPL pre-qualification or disclosure.
Custom account information may be completed from other accounts or third parties
For fraud detection and financial compliance, the publisher may fill missing address, phone, SSN, birth date, employer ID or website information using another Stripe account or a third party. A Custom account user must contact the platform or business that created the account to view, update or correct the associated information.
Supporting quotations
Stripe may leverage data we already have from one of your Stripe accounts or Stripe may fill in some of this information by receiving data from a third party. You may view the information that we are associating with your account and update or correct that information by contacting the platform or business that created your Stripe payment account.
Qualifications & exceptions
by contacting the platform or business that created your Stripe payment account.
Checkout promotional preferences can be collected without a completed purchase
The Promotional Emails feature collects preferences for messages from the merchant at a Stripe Checkout page. Prospective customers qualify if they start a purchase and enter contact information without deleting it before the session ends; completion of a purchase is unnecessary.
Supporting quotations
When you visit a Business User’s checkout page (that is powered by Stripe Checkout Services), the Promotional Email feature will enable Stripe to collect information about your preferences to receive promotional emails from that merchant.
To be a “prospective End Customer” for the promotional email feature, you also need to have started to input your contact information into the checkout form, and then not delete that information prior to the end of the session.
Qualifications & exceptions
you also need to have started to input your contact information into the checkout form, and then not delete that information prior to the end of the session.
Choosing Link stores payment information for use at participating merchants
Using Link authorizes storage of payment-method information such as name, card number, CVC and expiry for purchases with participating Business Users. Other transaction data collected includes billing/shipping addresses, email and phone; payment-method data is secured using PCI-DSS standards. A non-user receiving an SMS because an inaccurate number was entered can use the linked opt-out route for deletion.
Supporting quotations
When you choose to use Link, you agree to let us store your payment method so that you can more readily make purchases through Link with Business Users of our payment processing Business Services (e.g., name, card number, cvc, and expiration date). We will also collect other Transaction Data, including billing address, shipping address, email and phone number. Your payment method data is secured using PCI-DSS standards.
Should you not have used Link and receive an SMS in error due to an inaccurate number being inserted at the authentication flow stage you can opt out here and your Personal Data will be deleted.
Qualifications & exceptions
Should you not have used Link and receive an SMS in error due to an inaccurate number being inserted at the authentication flow stage
Data Access & Collection · Company practice
US Capital assessment may require additional linked financial and Representative information
US businesses may be asked to link bank accounts or business credit sources. Pre-offer processing may include business credit history and information about the business and Representatives: name, address, credit/banking/financial history and last four SSN digits. For Connected Accounts it may include off-Stripe transactions received from the platform under their agreement.
Supporting quotations
If your business is based in the U.S., you may also be asked to link additional data sources, such as business bank accounts or business credit information, in order to receive financing through Stripe Capital.
Business credit history
Information about you and your Representatives, which may include name, address, credit history, banking relationships, last four digits of a Social Security Number, and financial history.
If you’re a Connected Account, off-Stripe transaction history that we receive from your Platform, in accordance with your agreement with them.
Qualifications & exceptions
If you’re a Connected Account, off-Stripe transaction history that we receive from your Platform, in accordance with your agreement with them.
Data Access & Collection · Company practice
Authorized Capital signers may need to provide personal identity documents
A Representative authorized to sign for the company may be asked for name, ownership threshold if an owner, home address and verification document, government ID number and verifying ID, tax ID, date of birth, email and phone. Information provided for the application is shared with the regional financial partner.
Supporting quotations
may be asked to provide the following personal information as part of the application process and that information will be shared with our financial partner in your region:
Name
If Owner, Percentage Ownership Threshold
Home address, and provision of a document, such as a household bill, which verifies their home address
Government ID number, and provision of an ID document which verifies the number provided