Privacy Policy

Information you provide

Credily collects the information you enter during sign-in, onboarding, and Settings, such as your email address, name, phone number, and rewards preference.

Credily also stores account status information needed to run the app, including onboarding state, session state, subscription state, and account deletion request state.

Connected financial data

If you connect accounts with Plaid, Credily may receive and store information such as institution details, linked card names, account identifiers, card profile selections, transaction dates, merchant names, descriptions, amounts, currencies, categories, and merchant category codes.

Credily uses this data to show connected cards, compare card rewards, calculate reward-related summaries, label transaction context, and produce recommendations.

When you confirm which saved card profile matches a connected account, Credily may use a keyed, non-readable fingerprint derived from Plaid's institution-provided official account name, together with the institution, account type, subtype, and confirmed catalog card, to improve future account-to-card suggestions for other customers. The shared matching record does not contain the readable account name, mask, Plaid account identifier, transaction data, or your Credily account identifier.

To prevent one underlying account from contributing more than once, Credily also stores a separate keyed, non-readable source-account fingerprint derived from Plaid's persistent account identifier when available, or from the institution and account mask as a fallback. The shared learner does not retain the raw identifier or mask.

Ask Credily and AI processing

Ask Credily is optional. When you ask a question, Credily sends your question, limited relevant conversation history, your time zone, and relevant card, reward, or transaction facts to OpenAI to generate an answer. Credily uses summaries where possible and bounded transaction details when needed, which may include merchant names, dates, amounts, currencies, categories, and whether a transaction is pending or posted.

Credily screens known direct identifiers before sending content to OpenAI and excludes private account identifiers from financial tool results. This is data minimization, not guaranteed anonymization. Free text and financial details can still identify someone. Do not include passwords, full card or bank account numbers, or other sensitive information in questions or pasted links.

Public web research uses a separate request containing public topics, card catalog information, or screened public links, rather than your private conversation and financial tool results. OpenAI and its search services process that research request. If you open a cited website, that website's own privacy practices apply.

OpenAI states that API data is not used to train its models by default. Credily disables stored API responses, but this is not Zero Data Retention. Standard abuse-monitoring logs may contain prompts and responses for up to 30 days, or longer where required by law or reasonably necessary to prevent harm. Feature-specific retention, including prompt caching, can still apply. OpenAI describes these controls at https://developers.openai.com/api/docs/guides/your-data.

Credily saves your original questions and validated answers, including cited sources, as encrypted chat content until you delete the chat or your account. Credily also keeps limited operational metadata, such as timestamps, response status, policy version, and usage counts, to operate and protect the feature. You can read and delete saved chats even when your membership no longer permits new answers or generation is unavailable.

Credily also counts the categories and places your questions are about, such as dining or a store's name, so it can show what you ask about most first on Home and among suggested questions. A category or place is learned after you ask about it three times. One you stop asking about fades after two weeks and is dropped after six. This is kept in your Credily account in encrypted form, so it follows you to any phone you sign in on. It only changes what comes first, never which card Credily recommends, and it is not sent to OpenAI. In Settings you can see what Credily has learned, remove any of it, reset all of it, or turn learning off. Turning learning off stops new counting and hides what was learned until you turn it back on. Removing a topic keeps only a note that you removed it, so it isn't learned again until you reset. Deleting a chat does not change what was learned from it.

Deleting a chat removes it from Credily's live systems. It does not erase provider records already retained, and routine backup removal may lag live deletion. Stopping an answer does not retract data already sent. Choosing not to use Ask Credily does not delete earlier chats; use the saved-chat deletion control or request account deletion.

Credily also uses OpenAI to choose a spending category for the purchases on your connected accounts and for places on the map, because the category decides what each card earns. This runs in the background and does not depend on whether you use Ask Credily. Credily only sends purchases from accounts that have agreed to this version of this policy.

For a purchase, Credily sends the merchant's name and its merchant category code with that code's official name. When a purchase has no code, Credily also sends the bank's description of it, with digits, email addresses and web addresses removed. The description of a payment to a person through Venmo, Zelle, Cash App, Apple Cash or PayPal is never sent. For a place, Credily sends its name and map tags.

Credily does not send a purchase's amount or date, your card or account, or who you are. This is data minimization, not guaranteed anonymization. A merchant's name or a bank's description can itself contain someone's name, such as a sole trader's.

Credily saves each answer with the details used to get it, encrypted and found by a keyed, non-readable fingerprint, so the same merchant or place is only asked about once. Saved answers are shared across Credily, hold nothing about your account, and stay after you delete your account.

OpenAI states that API data is not used to train its models by default. This is not Zero Data Retention. Standard abuse-monitoring logs may contain these requests and answers for up to 30 days, or longer where required by law or reasonably necessary to prevent harm.

Location and nearby recommendations

If you grant location permission, Credily can use location signals to find nearby merchants and recommend which linked card may be best at that location.

If you enable Usage analytics, Credily may send PostHog limited events when a nearby card recommendation is presented or a nearby notification is scheduled or opened. This event includes a random event identifier and presentation time, but no Credily account, merchant, notification, coordinate, speed, heading, altitude, or address data.

Notifications and device data

If you allow notifications, Credily may store a push notification token issued for your device so the backend can send alerts. Tokens are issued through Firebase Cloud Messaging, which delivers to iOS devices through Apple Push Notification service and to Android devices through Google Play services. Notification preferences and notification history may be stored so the app can show unread counts and route you to the relevant screen.

You can turn notifications off in your Android or iOS system settings or in Credily settings. Some background education or nearby alert behavior depends on those permissions.

Subscriptions and payments

Credily uses RevenueCat to synchronize subscription status and entitlements. Credily stores subscription identifiers, product identifiers, status, period dates, billing issue state, and related entitlement metadata needed to operate the subscription.

Purchases, payment processing, renewal, payment methods, receipts, refunds, and cancellation happen through the store where you subscribed — the Apple App Store on iOS or Google Play on Android. Credily does not receive or store your full payment-card details.

How Credily uses information

• To create and secure your account.
• To send and verify email one-time passcodes.
• To connect cards and account data through Plaid.
• To calculate reward comparisons, summaries, and recommendations.
• To answer questions you submit to Ask Credily using relevant financial facts and public research.
• To power nearby merchant prompts, notifications, and in-app routing.
• To manage subscription access and billing status.
• To process sign-out, session refresh, account deletion, provider revocation, and operational recovery.

Service providers

Credily relies on service providers to operate the app, including Plaid for account linking, OpenAI for Ask Credily answers, public web research and choosing the category of purchases and places, RevenueCat for subscription entitlement synchronization, Apple for App Store purchases and billing on iOS, Google for Google Play purchases and billing on Android, Firebase Cloud Messaging with Apple Push Notification service and Google Play services for push notification delivery, backend hosting and database infrastructure, and email delivery infrastructure for account emails.

These providers process data only for the parts of the product they support. Their own terms and privacy practices may also apply.

Optional usage analytics

Usage analytics is optional and separate from accepting the Terms and Privacy Policy. You can allow it or choose Not now on the dedicated onboarding screen, continue using the app either way, and change your choice in Settings. Credily does not treat a missing preference or acceptance of updated legal documents as permission to enable analytics.

If you allow Usage analytics, Credily sends PostHog events about how you use the app: the screens, sheets and dialogs you open and how long they stay open, the buttons, tabs, switches and other controls you tap (identified by fixed names), the features you use, onboarding and tutorial progress, permission and notification outcomes, nearby notification activity, and how the app performs, including start-up and screen load times, request times and failures, and crash and error reports. Each event also includes your plan (Free or Pro), how you signed in (email, Apple or Google), and roughly how long ago you joined, in broad ranges. Only activity while analytics is enabled is collected; Credily does not collect activity while it is disabled for later upload.

Credily does not send its account identifier, names, email addresses, authentication or push tokens, financial details such as card names, balances or amounts, merchant or place names, precise location, anything you type (including searches and Ask Credily questions), or chat content. Crash and error reports contain the type of error and where in the app's code it happened, not what was on your screen. PostHog assigns installation and session identifiers and processes device, app, and network information, including the IP address used to connect. This information is not necessarily anonymous. Credily does not create PostHog person profiles.

Credily does not record your screen. Older installed versions used a combined analytics and recording preference and may retain it until they refresh or are updated. Removing recording from the updated app does not delete recordings or events already collected by older versions.

Saving an opt-out stops new optional capture on that device even if the server preference update fails; Credily retains a local opt-out so a later sign-in or refresh does not silently turn it back on. Changes on other devices depend on their receiving the server preference. Device storage failures can prevent a choice from surviving a restart and are reported as errors.

Records already sent, in flight, or queued by the analytics software before withdrawal may not be deleted or retracted and may be uploaded after a later opt-in. The control is not a purge of previously collected data. Necessary processing for login emails, security, and requested app features continues independently of optional analytics.

Storage and security

On iOS, the app stores authentication session tokens in the iOS Keychain. On Android, session credentials are held by the Firebase Authentication SDK in the app’s private, sandboxed storage. API requests are sent to Credily’s backend, and the backend stores the data needed to operate the service.

Credily’s backend schema includes encrypted storage for sensitive transaction text fields such as merchant name, transaction description, and merchant category code. No system can promise perfect security, but the app is designed to avoid casual exposure of sensitive financial context.

Shared card-matching evidence uses keyed fingerprints and a random contributor identifier. The mapping between that contributor identifier and your account is removed when your account is deleted.

Deleting your account and data

You can request account deletion in two ways. In the app, use Settings. Without signing in, use https://credily.prodygyn.com/delete-account and enter the email address stored on the account.

The web request does not require a password or login. Credily emails a one-time link to the address already stored on the account to check that you control it. Opening that link does not delete anything; you still have to confirm on the page, and the link expires.

Once you confirm, Credily removes your account and the data tied to it from its live systems, including profile and contact details, connected-account and card records, transaction and reward data, saved Ask Credily chats, what Credily has learned from your questions, notification tokens and history, and local subscription records. Credily also requests revocation of the bank connections you linked through Plaid.

Credily keeps a limited record of your legal acceptance and of the deletion request itself, such as an opaque request identifier, status, and timestamps, for legal, security, and fraud-prevention purposes. Credily does not keep this as a usable copy of your account.

A de-identified card-matching contribution may remain after you disconnect Plaid or delete your Credily account. After account deletion, Credily removes the mapping needed to associate that contribution with your Credily account; the retained record contains no readable account name, raw mask, raw Plaid account identifier, transaction data, or Credily account identifier.

Saved category answers also remain, as described above. They hold nothing about your account, and deleting your purchases removes the link between them and those answers.

Where a provider supports account-linked deletion, Credily sends the required deletion or revocation request; provider schedules vary. Records that are not linked to your account, such as the installation and session identifiers used for analytics described above, cannot be matched to you and are not removed through this request. Store purchase records stay with Apple or Google under their own terms.

Provider cleanup and the removal of copies inside routine backups can lag the deletion of live data rather than happening instantly.

Deletion usually completes within 24 hours and no later than 30 days after you confirm. Credily emails you when the request is received and again when it is complete.

Deleting your Credily account does not cancel an App Store or Google Play subscription. Cancel it separately in your Apple ID subscription settings or your Google Play subscriptions settings, depending on where you subscribed.

If you cannot receive email at the address stored on your account, contact admin@prodygyn.com and Credily will help you complete the request.

Your choices

• You can choose not to continue account creation if you do not agree to these terms.
• You can avoid linking Plaid accounts, though core card recommendation features may not work without connected data.
• You can choose not to use Ask Credily and can delete individual saved chats without deleting your account.
• You can see, remove or reset what Credily has learned from your Ask Credily questions, or turn learning off, in Settings.
• You can manage location and notification permissions in your Android or iOS system settings and in Credily settings.
• You can use Usage analytics in Credily Settings to change your optional analytics choice. Existing explicit opt-outs are preserved. New accounts and accounts without an explicit recorded preference start disabled; an existing explicit opt-in permits analytics, not session recording in the updated app.
• You can manage or cancel your subscription through the subscription management flow.
• You can sign out, and you can request account deletion from Settings in the app or, without signing in, at https://credily.prodygyn.com/delete-account.