Despega

Privacy Policy

Version 1.5 · Last updated October 9, 2026

This policy explains what data Despega collects, what it is used for, who it is shared with and what rights you have over it.

1. What we collect

Account data: your email, name and password (encrypted). If you enable the PIN or biometrics, they are stored only on your device. If you turn on two-step verification with Google Authenticator, we store its secret key encrypted, only a fingerprint of each backup code (not the code itself) and when you turned it on. The key and your email are also stored in Google Authenticator, which may copy them to your Google account if you have its backup turned on. While you finish turning it on, we also store your backup codes encrypted; they stop working after fifteen minutes if you do not finish, and we delete them in the next automatic cleanup, usually within a day. All of this is deleted when you turn it off or delete your account.

Banking data, through Plaid: institution name, type and last digits of each account, balances, credit limit, payment dates and transactions, including the spending category Plaid assigns to each transaction (for example restaurants, travel or health). We never receive or store your bank credentials; you enter them directly in Plaid.

We also ask for your checking and savings accounts, not only your cards: that is what lets us show your balances, your debit spending and which account you pay from. We only read; we never move money.

Notification data: if you turn on notifications, an identifier of your device (push token) used only to deliver them to you.

Notice usage data: when each notice is sent and to which type of phone, when you see it in the app and when you open it. The record of sends, views and opens is deleted ninety days after sending. The notice itself stays until you delete your account, with its date, its type and whether it is marked as read: if you delete it from your notification bell its text is removed, but its date and type stay. Also, so as not to repeat a notice, each transaction and each bank account keep when we last notified you about them, and your settings keep the date of the last daily summary.

Subscription data: if you subscribe, the store (Apple or Google) tells us through RevenueCat whether your subscription is active, on which plan and when it renews. We never receive your card number or payment details.

Support messages: what you write in the in-app support chat, so we can help you.

Usage data: language, app settings, technical logs and error reports needed for the app to work and to fix faults.

Card image: which card image you choose for each connected account, or whether you tell us it is none of the ones we show you, and when you chose. It is deleted when you disconnect that bank or delete your account.

IP address: we keep it with some security actions on your account, to protect it and detect unusual access, until you delete your account.

2. What we use it for

To show you your accounts, compute your credit health, organize your payments, send the reminders you enable, manage your subscription and provide support. We do not sell your data or use it for third-party advertising. We use the send, view and open dates of notices to improve them.

3. Who we share it with

Plaid, Inc., which connects to your bank and delivers the data to us. Its policy: https://plaid.com/legal/

Render, Inc., where our API runs, and Supabase, Inc., which hosts the database. Both keep their servers in Oregon, United States, and process the data on our behalf, not for their own purposes.

Resend, Inc., which receives your email address in order to deliver verification codes and the notices you turn on.

Apple Inc. and Google LLC, which deliver notifications to your phone (APNs and Firebase Cloud Messaging) and charge the subscription. They receive your device's notification identifier and the text of each notice; never your banking data.

Expo (650 Industries, Inc.), which routes each notice from our servers to Apple or Google. It receives the notification identifier and the text of the notice.

RevenueCat, Inc., which manages the status of your subscription under an anonymous identifier. It does not receive your banking data.

Functional Software, Inc. (Sentry), which receives a technical report when the app or the server fails, so we can fix the error. Those reports do not include your banking data.

To show merchant logos next to your transactions, our server visits each merchant's website and the addresses that website serves its icon from, and queries Wikidata and Wikimedia Commons, public services run by the Wikimedia Foundation, Inc. It only sends them the merchant's name or the website address: never your name, your email, your accounts, your amounts or anything that identifies you. Our server does this, not your phone, and the logos obtained this way are stored on our servers and reach you from there.

We do not use advertising networks or third-party tracking tools.

Authorities, when required by law.

4. How long we keep it

We keep your data while your account is active.

When you delete your account from the app (Profile → Security) the deletion is immediate: we first revoke access to your banks in Plaid and then everything of yours is deleted in cascade, accounts, transactions, plans, reminders, support messages and settings. If Plaid does not respond when we revoke access, whether you delete your account or disconnect a bank, we keep the access token for that bank encrypted for up to ninety days, only to try again; if that does not work within that time, we delete the token and only the identifier of that connection in Plaid remains. Beyond that, we do not keep any copy.

The names of the businesses your bank recognizes through Plaid in your transactions go into our shared logo catalog and stay there even if you delete your account, without recording which customer they came from. They are saved as they arrive, except for the account holder's name that some banks add with the label "INDN:", which we remove before saving them. The names you write yourself, when you rename a transaction or in your rules, and the bank's text on a transaction you mark as a subscription without renaming it can also go into the catalog; for those, the catalog records which ones are yours only so it can delete them, and they are deleted when you delete your account or when you disconnect the bank they came from and they no longer appear in any of your transactions (if something fails at that moment, they are deleted later, in the daily automatic cleanup). They stay, with nothing linking them to you, if another customer has the same name in their rules, if it matches the name of a business Plaid recognizes or if they have a logo or website. Whatever was already in the catalog before this version may stay, also with nothing linking it to you. The names you give a money transfer between people or a remittance that we recognize as such (Zelle, Venmo, PayPal, Cash App, Western Union and the other services on our list) never go into the catalog: from those transfers only the service goes in, never who the money goes to. The names you write are not sent to Wikidata, Wikimedia or merchants' websites to look up their logo.

The database is backed up automatically once a day and each backup is kept for seven days; after that it is overwritten on its own, and whatever you had deleted goes with it. Beyond that, we only keep what the law requires us to keep, and for the period it sets.

Technical error reports are kept for ninety days and then deleted on their own, even if your account is still active.

Deleting your Despega account does not delete what Plaid keeps on its own. You can see and revoke the connections you made through Plaid at https://my.plaid.com

5. Your rights

You can access your data, correct it, request a copy, disconnect any bank and delete your whole account from within the app (Profile → Security). You can also write to us to exercise any of these rights.

If you live in California, the CCPA and the CPRA also give you the right to know what personal data we hold about you and where it came from, to ask us to delete or correct it, and not to be treated differently for exercising those rights. We do not sell personal data and we do not share it for behavioural advertising, and we have not done so in the last twelve months.

If you live in Virginia, Colorado, Connecticut, Utah, Texas or another state with its own privacy law, you have equivalent rights.

To exercise them write to us at support@despegacredito.com. We will reply within forty five days at most.

6. Security

Data travels encrypted (HTTPS/TLS). The access tokens to your bank are stored encrypted with AES-256-GCM, and the whole database is encrypted at rest by the provider that hosts it. Your bank credentials never pass through our servers.

You can protect your account with a PIN or biometrics on your phone. When you sign in on a new device we ask for the code we send to your email, and you can also turn on two-step verification with Google Authenticator, which also asks for that app's code.

What we do not have yet: an external audit (SOC 2) or an independent penetration test. What we do have: Plaid reviewed our application and approved us to operate in its production environment, we scan the code with security tools on every change, and we will publish here every audit we obtain. How to report a security issue: https://despegacredito.com/security

No system is infallible; if we detect a breach that affects you, we will notify you.

7. Minors

The app is not directed at people under 18 and we do not knowingly collect data from minors.

8. Changes and contact

If we change this policy in a material way we will notify you in the app.

Questions or requests about your data: support@despegacredito.com. VMMV Partners LLC, 174 Wimbledon Lake Dr Apt 174, Plantation, FL 33324, United States.

Change history

1.0, August 27, 2026: first version.

1.1, September 11, 2026: every third party named (Apple, Google, Expo, RevenueCat and Sentry in addition to Plaid, Render, Supabase and Resend), notification and subscription data, support messages, encryption named, two-step verification, Plaid spending category, ninety-day error reports and what Plaid keeps after you delete your account.

1.2, September 12, 2026: daily backups kept seven days (it used to say up to thirty), why we ask for bank accounts and not only cards, what we do not have yet in security (audit, penetration test) and how to report an issue, and this section.

1.3, September 27, 2026: merchant websites and Wikimedia (Wikidata and Commons), where merchant logos come from, and what is sent to them; the shared logo catalog, which is not deleted when you delete your account; notice usage data: when notices are sent, seen and opened; the card image you choose for each connected account; and the IP address we keep with some security actions.

1.4, September 27, 2026: the shared logo catalog records which customer wrote each of the names customers write, only to delete them when that customer deletes their account or disconnects the bank they came from; names given to money transfers between people never go into it; and the account holder's name marked with "INDN:" is removed from the bank's text.

1.5, October 9, 2026: two-step verification with Google Authenticator and what we keep for it; and what happens to your bank access token if Plaid does not respond when we revoke it.