Does FlexJobs store my credit card information?
Current FlexJobs policy draws a distinction: the Provider says it does not store credit card information and uses an external service provider to process transactions, while the Terms say third-party vendors may store payment information.
Trust boundary: This is manually researched payment/privacy guidance, not an A✓/CHECKED verification record, not an A✓/CHECKED approval badge and not a security audit. AlreadyChecked has no proven FlexJobs production affiliate destination, so this page contains no direct merchant affiliate link.
AlreadyChecked Verdict
The current evidence supports a Provider-versus-third-party storage distinction—not “no payment data is stored anywhere.”
FlexJobs' Privacy Policy says the Provider does not store credit card information and uses an external processor, while current Terms say third-party vendors may store payment information. If you need the processor, retained data, access or deletion details for your account, use FlexJobs support/privacy rather than inferring raw-card storage or universal retention rules from account-linked payment data.
| Question | Current evidence | What it supports | Best control | Important limitation |
|---|---|---|---|---|
| Provider Does FlexJobs itself store card information? | Current Privacy Policy says the Provider does not store credit card information and uses an external service provider for transaction processing. | A Provider-side storage distinction for credit card information. | Current Privacy Policy plus account-specific support/privacy when needed. | This wording is not a PCI certification, security audit, encryption guarantee or breach guarantee. |
| Third party Can vendors store payment information? | Current Terms say third-party vendors may store payment information. | Payment information may be retained outside the Provider itself. | Ask FlexJobs for account-specific processor/subprocessor information when needed. | The checked public material does not establish one universal processor or retention period for every transaction. |
| Account-linked method Does saved/associated payment data prove raw-card storage? | No such conclusion is established by the checked public documents. | Association with an account can exist without proving the Provider retains the raw card number. | Use support/privacy for the specific storage/access/deletion question. | AlreadyChecked will not infer backend storage architecture from an account UI or payment-method association. |
Research receipt
Last checked September 8, 2026. This receipt reflects the payment/privacy evidence used on this page; it is not an A✓/CHECKED automated-verification badge.
The key distinction: “FlexJobs itself does not store credit card information” is supported by the current Privacy Policy. “No payment information is stored anywhere” is not supported, because the Terms say third-party vendors may store payment information.
What the Privacy Policy says
The current FlexJobs Privacy Policy says customers must provide payment information such as credit or debit card information, name and billing address to purchase services. It then says the Provider does not store credit card information and uses an external service provider to help process the transaction.
What the Terms add
Current Terms separately say FlexJobs’ third-party vendors may store payment information. That is why the provider-side statement should not be expanded into a claim that no payment information is stored by any third party.
Does an account-linked payment method mean FlexJobs holds my raw card number?
No such conclusion is established by the reviewed public material. The Privacy Policy says payment information is associated with the account after sign-in, but association with an account does not prove the Provider itself retains the raw card number.
Does FlexJobs name one processor or one retention period for every transaction?
The reviewed public material does not establish one universal payment processor for every transaction, one universal card/payment-data retention period, or one universal security certification that applies to every transaction.
The Privacy Policy says service providers under contract can receive information for operations including payment processing and says a fuller processor/subprocessor list can be requested from FlexJobs.
What to do if you need account-specific details
- Use FlexJobs support or privacy channels for questions about a specific saved payment method, processor, access request or deletion request.
- Do not infer raw-card storage by FlexJobs merely because a payment method is associated with your account.
- Do not rely on this page as a security audit, PCI certification, encryption guarantee or breach guarantee.
- Do not post full card numbers, CVVs, bank passwords, one-time codes or other payment-authentication credentials.
Sensitive-data boundary: AlreadyChecked does not need your full card number, CVV, bank password, one-time code or payment-login credentials to explain these published policies.
Sources checked
- FlexJobs Privacy Policy — payment information, Provider storage statement and external processing
- FlexJobs Terms of Use — third-party vendors may store payment information
- FlexJobs Contact — first-party support path
Verdict: Current FlexJobs policy says the Provider does not store credit card information itself and uses an external service provider for transaction processing, while third-party vendors may store payment information. The evidence therefore supports a provider-versus-third-party storage distinction—not the broader claim that no payment information is stored anywhere. Use FlexJobs support/privacy channels for account-specific processor, storage, access or deletion questions.
Commercial boundary: This page is non-monetized. AlreadyChecked has not proven project-controlled FlexJobs affiliate approval or a production merchant destination. Internal links are editorial navigation only.
Last checked September 8, 2026. Refresh due September 22, 2026. This page uses a shortened refresh window because payment and privacy terms can change.