Trust matters when you connect an account or ask for help managing subscriptions. At Unsubscribe.ai, we believe users should understand not only what information may be used, but also what sensitive information we do not store.

Unsubscribe.ai is designed to access only the information needed to help identify subscriptions, organize recurring charges, and support cancellation requests. We do not want to collect or store unnecessary sensitive information.

This article explains the types of information Unsubscribe.ai is designed not to store and why that matters for your privacy and security.

We Do Not Store Your Bank Login Credentials

Unsubscribe.ai does not store your bank username or password.

When you connect a supported financial account, the connection is handled through a secure account connection provider, such as Plaid. This allows you to connect your account without giving Unsubscribe.ai your banking login credentials.

In simple terms:

• Unsubscribe.ai does not store the username or password you use to log in to your bank.

This helps reduce sensitive data exposure while still allowing Unsubscribe.ai to identify possible subscription activity from permitted account information.

We Do Not Store Full Account Login Details

Unsubscribe.ai does not need to store full login details for your outside accounts in order to help identify subscriptions.

This includes login credentials for accounts such as:

• Bank accounts

• Credit card accounts

• Merchant accounts

• Streaming services

• App subscriptions

• Software subscriptions

• Membership accounts

• Payment platforms

If a merchant requires you to log in directly to cancel a subscription, you may need to complete that step through the merchant's official website or app.

Unsubscribe.ai should not ask you to provide your password for an outside account.

We Do Not Store Full Bank Account Numbers

Unsubscribe.ai does not need your full bank account number to help identify subscriptions.

Connected account information may include limited account details, such as the account type or partial account identifier, so you can recognize which account is connected. However, Unsubscribe.ai is designed not to store full bank account numbers.

For example, you may see a limited account label or partial details to help identify the connected account, but full banking details are not needed for subscription discovery.

We Do Not Store Full Credit or Debit Card Numbers

Unsubscribe.ai does not need your full credit card or debit card number to provide subscription discovery or cancellation assistance.

If payment details are needed for billing your Unsubscribe.ai plan, payment processing may be handled by a third-party payment processor. Unsubscribe.ai may receive limited billing details, such as the last four digits of a card or billing status, but it does not need your full card number for subscription management.

You should not send full card numbers through support messages.

We Do Not Store One-Time Security Codes

Unsubscribe.ai does not need your one-time security codes.

This includes codes sent by:

• Your bank

• Your credit card provider

• A merchant

• A payment platform

• An app store

• A two-factor authentication app

• Text message or email verification

If a merchant or financial institution requires a security code, you should enter that code only through the official website, app, or secure verification flow.

Do not send one-time security codes through support messages.

We Do Not Store Unnecessary Financial Information

Unsubscribe.ai is designed to use financial information for a specific purpose: helping identify and manage subscriptions.

We do not need to store unrelated or unnecessary financial information that is not needed to provide the service.

For example, subscription discovery may use transaction details like merchant name, charge amount, charge date, or recurring billing patterns. It does not require Unsubscribe.ai to store unrelated sensitive financial details that are not needed for subscription detection, dashboard organization, or cancellation support.

Our goal is to keep the data used by the service focused and limited to what is needed.

We Do Not Store Passwords for Merchant Accounts

Some merchants require the account holder to log in directly before a subscription can be canceled.

Even in those cases, Unsubscribe.ai does not need your merchant password.

If a cancellation requires direct login, you may be asked to complete that step yourself through the merchant's official site or app. This helps protect your account and keeps your login credentials private.

Examples may include subscriptions managed through:

• Apple

• Google Play

• PayPal

• Amazon

• Roku

• A phone carrier

• A gym or local membership portal

• A streaming or software account

We Do Not Store Information Just Because It Is Available

Unsubscribe.ai is built around collecting and using information for a clear purpose.

That means we do not aim to store information simply because it may be available through a connection. The information used should support a specific function, such as:

• Identifying possible subscriptions

• Organizing your subscription dashboard

• Estimating recurring spend

• Supporting cancellation requests

• Tracking cancellation status

• Helping with support or account questions

This approach helps reduce unnecessary data exposure and keeps the service focused on subscription management.

What You Should Avoid Sending to Support

For your safety, avoid sending sensitive information that is not needed.

You should not send:

• Bank passwords

• Merchant account passwords

• Full bank account numbers

• Full credit or debit card numbers

• One-time security codes

• Full Social Security numbers

• Online banking login details

• Sensitive documents unless specifically required and appropriate

If a support request requires more information, provide only what is needed to help resolve the issue.

Helpful information may include:

• Your Unsubscribe.ai account email

• The subscription or merchant name

• The last charge amount

• The approximate charge date

• The billing platform, if known

• A customer ID or confirmation number, if available

Why This Matters

Limiting what is stored helps protect users.

The less unnecessary sensitive information a service stores, the less sensitive information is exposed if something goes wrong. This is an important part of privacy-focused design and responsible security practices.

Unsubscribe.ai is designed to help users manage subscriptions without requiring them to hand over unnecessary passwords, full banking details, or sensitive credentials.

What We May Store Instead

To provide the service, Unsubscribe.ai may store limited information needed for subscription management.

This may include:

• Subscription names

• Merchant names

• Transaction amounts

• Transaction dates

• Billing frequency estimates

• Cancellation request status

• Manually added subscription details

• Account settings

• Plan and billing status

• Support messages you choose to send

This information helps Unsubscribe.ai identify subscriptions, organize your dashboard, support cancellation requests, and provide account support.

You Stay in Control

You choose whether to connect an account, which subscriptions to review, and whether to request cancellation help.

You may also be able to:

• Disconnect a connected account

• Revoke permissions through Plaid or your financial institution

• Cancel your Unsubscribe.ai plan

• Request deletion of your data

• Contact support with privacy questions

Disconnecting an account may limit Unsubscribe.ai's ability to refresh subscription activity or detect new subscriptions from that account.

The Bottom Line

Unsubscribe.ai is designed not to store unnecessary sensitive information, including bank login credentials, full account login details, full bank account numbers, full card numbers, passwords, or one-time security codes.

We use the information needed to help identify subscriptions, organize your dashboard, support cancellation requests, and provide account support.

Our goal is to make subscription management easier while keeping the data we use focused, limited, and tied to a clear purpose.