Is it safe to share {X} with {Y}?

Sharing IBAN data with ChatGPT is strongly discouraged. Inputs entered into ChatGPT may be used by OpenAI to train or improve its models, meaning account identifiers could be stored and processed beyond the original interaction. By default, conversation data can be retained for up to 30 days even when chat history is disabled.

Why this matters

IBAN numbers are unique account identifiers that, once exposed, cannot be changed the way passwords can, making any unintended retention a lasting risk.
OpenAI's data handling infrastructure operates across multiple regions, which means IBAN data entered into ChatGPT may be processed outside the jurisdiction where the account holder is located.
There is no contractual guarantee in the standard ChatGPT consumer terms that IBAN data will be isolated, deleted on demand, or excluded from model training pipelines.

For enterprise

Employees who paste IBAN data into ChatGPT outside of approved internal tools may be violating data handling policies without realizing it. Many organizations operate under regulatory frameworks such as GDPR or PCI DSS that impose strict controls on where account identifiers can be transmitted and stored. Using a consumer AI tool for tasks involving IBAN data introduces compliance exposure that internal security reviews are unlikely to have assessed or approved.

Compliances at risk

What counts as IBAN Data?

International Bank Account Numbers (IBAN)
Cross-border bank account identifiers
International payment account numbers
SEPA account identifiers
Global banking identifiers

Why people share IBAN Data with ChatGPT

To prepare international payments
To verify overseas banking details
To summarize cross-border payment information
To complete wire transfer instructions

What actually happens when you paste IBAN Data into ChatGPT

When you paste IBAN Data into ChatGPT, that data is transmitted from your device to external servers operated by the AI provider.

Depending on system configuration and policies, the data may be logged, temporarily stored, or reviewed for safety and quality purposes. Retention can last from days to weeks, and in some cases may extend beyond the immediate session.

Statements such as “we do not train on your data” do not eliminate risks related to retention, logging, or internal access. These controls vary by product and setting, and are not always visible to end users.

From a governance perspective, any non-zero retention window introduces exposure risk when sensitive data is shared without controls, auditability, or enforcement.

Risks of sharing IBAN Data with ChatGPT

Unauthorized transactions: Card or bank details can be used for fraudulent payments.
Fraud escalation: Transaction data can help bypass fraud detection systems.
Credential abuse: Payment credentials can be reused across platforms.

Real incidents

Redis bug exposing chat and payment data : A vulnerability exposed chat histories and partial payment information across users.
Credential theft via infostealer malware : Over 100,000 ChatGPT credentials were stolen from infected devices.
Training data extraction : Researchers extracted memorized financial and personal information.

Is this allowed under policy or law?

Context	Is it safe?
Personal experimentation	No
Business use	No
Regulated industry	Definitely not
With redaction	Rarely

Safer ways to handle IBAN Data

IBAN Data should not be shared with consumer AI tools without controls in place. If AI assistance is required, organizations should use systems that enforce data redaction, access controls, and policy enforcement before data leaves their environment.

Automatically redact sensitive fields before sending data to AI models
Prevent unauthorized data from being entered into external tools
Maintain audit logs and visibility into how data is used
Ensure compliance with frameworks like GDPR, CCPA, and SOC 2

Platforms like Wald are designed to enable safe AI usage by ensuring sensitive data never leaves your control unprotected.

How Wald.ai handles this safely

Wald adds a governance layer to AI usage, helping organizations monitor and control how sensitive data like IBAN Data is shared.

AI DLP

Identifies IBAN Data in context and enables teams to:

Observe AI usage
Detect sensitive data in prompts
Allow, warn, or block actions
Maintain audit logs

LLM Pack

Provides controlled access to multiple AI models (ChatGPT, Claude, Grok, and others) through a single governed environment.

Centralized model access
Policy enforcement
Usage visibility
Auditability

Frequently Asked Questions

Is it safe to share IBAN Data with ChatGPT?

In most cases, no. Sharing IBAN Data with ChatGPT introduces unnecessary exposure risk and is generally discouraged unless strong governance controls are in place.

What happens when IBAN Data is entered into ChatGPT?

The data is transmitted to the AI provider's infrastructure for processing. Depending on the service and configuration, it may be temporarily stored, logged, or retained for security and operational purposes.

Can ChatGPT retain IBAN Data after a conversation ends?

ChatGPT providers may temporarily retain prompts and responses for security, abuse monitoring, or operational purposes. Depending on the platform and settings, IBAN Data may remain stored beyond the immediate session. In some cases, submitted data may be retained for up to 30 days before deletion. Organizations should assume that any sensitive information shared with AI systems could persist beyond the active conversation.

Does ChatGPT train on IBAN Data?

Some AI providers allow organizations to disable training on submitted data, while others may use interactions to improve services. Even when training is disabled, IBAN Data may still be processed, logged, or retained according to provider policies.

What happens if IBAN Data is accidentally shared with ChatGPT?

Once submitted, organizations may have limited visibility into how the information is retained, processed, or accessed. The appropriate response depends on the sensitivity of the data, internal policies, and incident response procedures.

Why do traditional DLP solutions struggle to identify IBAN Data in AI prompts?

Traditional DLP tools rely heavily on pattern matching and predefined rules. AI prompts often contain fragmented, transformed, or contextual information that can be difficult to classify accurately. Context-aware AI DLP solutions can evaluate surrounding context to better distinguish between similar data types and reduce false positives and false negatives.

Secure Your Employee Conversations with AI Assistants

Book A Demo