Privacy Policy

01 Who controls your personal data

Kredo is operated by Akkram Bederi, which acts as the Personal Information Controller for personal data processed through the Kredo service.

Privacy and data protection inquiries, including requests to exercise the rights described in section 17, may be sent to support@getkredo.app. This address reaches the person responsible for privacy compliance at Kredo.

Philippine data privacy

Kredo processes personal data in accordance with applicable Philippine data-protection law, including Republic Act No. 10173, the Data Privacy Act of 2012, its Implementing Rules and Regulations, and applicable issuances of the National Privacy Commission.

02 About Kredo

Kredo is an independent iPhone app for keeping track of credit cards issued in the Philippines: the cards you own, their published benefits, the promos that apply to them, and the balances and dates you choose to track on your phone. Kredo is not a bank, a lender, or a payment processor, and it does not connect to your bank accounts.

Kredo has no automated link to any issuer. It never signs in to your online banking, and it cannot move money, make payments, or read your account with a bank. Everything Kredo knows about your cards is either published card information from our own researched catalog or something you entered yourself.

03 What Kredo never asks for

Because there is no field that asks for these values, the one way they could reach us is if you typed them somewhere they do not belong. Please do not enter full card numbers, security codes, PINs, online-banking passwords, or other banking credentials into free-text fields, Ask Kredo, card nicknames, transaction notes, or support messages. Kredo has no use for them, and a question you type is sent to our backend and on to our AI model provider to be answered.

04 Information we collect

4.1 Account and authentication

Creating a Kredo account requires signing in. Kredo uses no passwords at all — there are three sign-in methods, and each produces an account record consisting of a Kredo user ID (a random identifier), your email address, the sign-in method used, and basic profile information supplied by that method.

• Email one-time code. You enter your email address and we send a six-digit code to it. The code expires after 10 minutes and is used only to confirm the address and start a session. The same flow creates the account if the address is new.
• Google Sign-In. See section 5.
• Sign in with Apple. See section 6.

Sign-in is handled by Supabase Auth, which also stores the account record and issues the session token the app uses for subsequent requests.

4.2 Card management information

When you are signed in and add a card, Kredo stores a record of which card it is, so your cards are available across your devices and after reinstalling. A card record contains only:

• which catalog product the card is, or — for a card our catalog does not carry — a card name, bank name, and network you type yourself;
• a nickname and the name you put on the card face;
• whether the annual fee is waived, whether payment reminders are on, whether the card is archived, and the card artwork you picked.

The figures you track are stored only on your device. Your credit limit, outstanding and statement balances, minimum amount due, amounts you record as paid, and statement and due dates are kept in the app's own storage on your phone and are never stored on our servers; our database discards them even if an older version of the app sends them. When you sign in on a new phone or after reinstalling, your cards come back and you enter those figures again.

4.3 Transactions and spending activity

Transactions you log or import are stored on your device, in the app's own storage. Kredo's servers hold no transaction records and no table for them. Like any app data, they are included in your phone's own device backup (iCloud Backup or a computer backup) if you have that turned on; that backup is between you and Apple, and Kredo cannot read it. Your on-device spending history is what powers the Activity and Analytics screens in the app.

Transaction information and card figures leave your device only in the two situations described in section 9: as compact totals sent with an AI request when you have enabled that, and as statement text when you choose AI-assisted statement reading. In both cases they are used to answer that one request and are not stored. Raw transaction lists, merchant names, and transaction notes are never sent to our AI backend — the request format has no field that would carry them.

4.4 Saved promos

When you bookmark a promo while signed in, Kredo stores the promo's identifier and the time you saved it, linked to your account. It stores no copy of the offer itself.

4.5 AI and personalization settings

Your AI & Personalization settings — personalized insights, use of transaction data, and inclusion of card balances — are stored with your account so the backend can enforce them, not merely trust the app. See section 9.

4.6 Ask Kredo and card recommendations

When you ask Kredo a question or request a card recommendation, the request sent to our backend contains your question or purchase details, a conversation identifier, and — only where your settings permit it — the personal context described in section 9. Your app builds that context from the figures on your phone and sends it with the request; our backend passes it to our AI model provider to produce the answer and does not store it.

Our backend's operational log for these requests records the function name, the model provider and model name, the conversation identifier, whether personalization was permitted, the detected question type, and token counts. It does not record your question text, the answer text, or any amount or balance.

4.7 Statement import

Kredo can read a credit card statement to help you log transactions. You choose how:

• On device. The statement is parsed on your phone and nothing about it is sent to us.
• With AI. The text of the statement is sent to our backend and on to our AI model provider to be read, and the extracted rows come back to your device. This endpoint writes nothing to any database, does not include statement content in error responses, and does not log the statement text. If it fails, the app falls back to reading the file on your device.

4.8 Voice dictation

If you dictate instead of typing, audio is transcribed entirely on your device using an on-device speech model. No audio is sent to us or to any third party, and none is retained.

4.9 Using Kredo without an account

Kredo can be used as a guest. In guest mode, cards, their figures, transactions, and saved promos stay on your device and are not written to our servers. So that Ask Kredo works without an account, each install is given an anonymous identity on our servers. It has no email address or name, and it holds only your AI & Personalization settings and the request counters that enforce usage limits. If you later sign in, the guest data on that device is carried into your account and the anonymous identity is retired.

4.10 Notifications

Payment reminders are scheduled locally on your device by iOS, using the dates you entered. They are not sent from a server, and Kredo operates no push notification service.

05 Google Sign-In

If you choose "Continue with Google", Kredo asks Google only for the basic sign-in scopes — the standard OpenID Connect identity scopes (openid, email, profile). Kredo's sign-in request adds no other scopes.

From those scopes we receive, and use, the following:

You can disconnect Kredo from your Google Account at any time in your Google Account's security settings. Doing so stops future Google sign-ins; to remove the data Kredo holds, delete your account as described in section 14.

06 Sign in with Apple

If you choose "Continue with Apple", Kredo requests your name and email address from Apple. If you choose Apple's "Hide My Email" option, we receive a private relay address instead of your real one, and that relay address becomes your Kredo account identifier. Kredo receives no other Apple account data.

07 How we use information

• To create your account, sign you in, and keep you signed in.
• To store and sync the cards and saved promos you chose to keep with your account. The figures you track on a card are not stored with your account.
• To match promos and card benefits to the cards you own.
• To answer your Ask Kredo questions and produce card comparisons.
• To read a statement when you ask us to.
• To operate, debug, and keep the service reliable and secure, including the rate limits that protect sign-in.
• To respond to you when you contact support.

Kredo does not use your information to serve advertising, and does not build advertising or cross-app tracking profiles.

08 Why Kredo is allowed to process your information

Depending on the processing activity, Kredo processes personal information because:

• it is necessary to provide a service or feature you requested — creating an account, signing you in, syncing your cards, saving a promo, or answering an Ask Kredo request;
• you have given consent, which is the basis for the optional AI personalization described in section 9 and for optional AI-assisted statement reading;
• processing is necessary to comply with a legal obligation; or
• processing is reasonably necessary for legitimate interests such as securing, maintaining, preventing abuse of, and improving Kredo, where those interests are not overridden by your rights and freedoms.

Where processing rests on consent, you can withdraw it at any time in the app under Privacy & Data, and withdrawal takes effect on every request made after that. Withdrawing consent for AI personalization does not sign you out or remove your cards — it stops your personal context being included in future AI requests.

09 AI features and your control over them

Kredo uses artificial intelligence for features such as Ask Kredo, card comparisons and recommendations, and optional AI-assisted statement reading. These are powered by a third-party AI model provider (see section 11).

What that provider is allowed to see about you is governed by the AI & Personalization switches in the app, under Privacy & Data:

• Personalized insights — the master switch. With it off, no personal financial data is sent with an AI request at all.
• Use transaction data for recommendations — allows per-period category spending totals and counts to be included.
• Include card balances — allows credit limit, available credit, and utilization to be included.

These settings are enforced on our server, not just in the app. Before an AI request is assembled, the backend re-reads your saved settings and derives what is permitted; anything not permitted is discarded before the model is called, and the tools that could fetch personal data are not made available to the model at all. A request that claims more permission than your saved settings grant is refused that data. If you have no saved settings — for example you have never enabled personalization — the backend treats that as "not allowed".

When personalization is permitted, what can be sent is limited by design to compact, capped aggregates: the catalog identifiers and nicknames of cards you own, per-period category spending totals and counts, credit limit / available credit / utilization figures, and statement and due dates. Raw transaction lists, merchant names, and transaction notes are not accepted by the request format at all.

These figures are sent, not stored. Your app reads them from your phone and attaches them to the question you are asking. Our backend uses them to build that one request to the AI model provider and keeps no copy — no database record and no log entry contains them. The next question sends them again, from your phone, if your settings still allow it.

Turning off personalization prevents that personal context from being included in future AI requests. Your settings apply prospectively: they govern every request made after you change them, and they cannot retrieve or delete a request that has already been sent to the model provider. What happens to a request already delivered is governed by that provider's own terms.

AI answers are informational. They can be incomplete, outdated, or incorrect, and they are not financial, legal, tax, investment, or credit advice — confirm anything that affects a financial decision with your card issuer.

10 Automated processing and personalization

When you enable personalization, Kredo may use automated processing to evaluate the information you have permitted us to use — the cards you own, category spending aggregates, card utilization, statement and due dates sent from your device with each request, and the preferences you set — in order to personalize informational card comparisons, promo matching, and the answers Ask Kredo gives you.

These outputs are informational comparisons. They do not determine whether you receive credit, approve or deny a financial product, change your credit limit, process a transaction, or make any decision on behalf of a bank or card issuer. Kredo does not assess creditworthiness or affordability, does not produce a credit score, and does not share these outputs with any issuer.

With personalization off, card comparisons and answers are produced from Kredo's published catalog and what you type into the request, without personal context.

11 Service providers and processing outside the Philippines

Kredo relies on the following providers to operate. They process information on our behalf, for the purposes below.

Our backend also supports an alternative AI provider (Anthropic) that we use for internal benchmarking. It is not enabled for production traffic, so your requests are not sent to it. If we change the production AI provider, we will update this section before the change takes effect.

Processing outside the Philippines

Some of these providers may process information on infrastructure located outside the Philippines. When Kredo uses a service provider to process personal data on its behalf, Kredo remains responsible for that processing and for putting in place the contractual, organizational, and technical safeguards required by applicable law.

Where each provider processes your information:

• Supabase — Kredo's database and backend run in Singapore (AWS region ap-southeast-1). This is where your account record, card records, saved promos, AI settings, and product analytics events are stored.
• DeepSeek — DeepSeek states that it processes and stores personal data in the People's Republic of China. Anything sent with an AI request, including personal context your settings permit, is processed there. See section 13 for what DeepSeek's terms say about retention and training.
• Resend, Google, and Apple process information under their own terms and may do so outside the Philippines, including in the United States.

If you do not want personal context to leave the Philippines for AI processing, keep Personalized insights off; Ask Kredo then receives only your question.

12 Analytics and tracking

Kredo's released app contains no third-party analytics, attribution, or advertising SDK. It does not use the advertising identifier (IDFA), shows no App Tracking Transparency prompt, and declares no tracking domains. Kredo does not track you across other apps or websites, and does not sell your information.

Kredo measures how the app is used with its own first-party product analytics — no vendor is involved. When you are signed in, the app records events such as which screens were opened and which features were used, and stores them in Kredo's own database linked to your account. Events carry coarse labels (for example a card count bucket or a card's issuer), never amounts, balances, limits, email addresses, names, or free text, and our database strips any such field before it is stored. We use them to understand and improve the product, not to advertise to you. They are deleted with your account. If we ever share them with a vendor, we will update this policy first.

Separately, our infrastructure providers keep the ordinary operational logs any hosted service keeps — request metadata such as timestamps, IP addresses, and error information — which we use to keep the service running and secure. These are security and reliability logs, not product analytics: they are not used to build a profile of you, to measure feature usage, or for marketing.

13 Data retention

Account-associated Kredo records — your account record, card records, saved promos, AI settings, and product analytics events — are retained while your account remains active, and are deleted when you delete your account, except where retention is reasonably necessary to comply with law, resolve disputes, prevent fraud or abuse, enforce our agreements, or maintain the security of the service.

• Card figures, transactions, payments, and statement-import records stay on your device until you delete them or remove the app. We hold no copy.
• Personal context sent with an AI request (card figures and spending totals) is used for that request only and is not stored by us.
• Statement content sent for AI reading is not stored by us: that endpoint performs no database writes and does not log statement text.
• Ask Kredo requests are not stored by us as conversation records. What remains is the operational log line described in section 4.6, which contains no question text, answer text, amount, or balance.
• Sign-in codes expire 10 minutes after they are issued.

Operational logs and email delivery records held by our infrastructure providers follow each provider's own platform retention. We do not currently operate a separate, fixed retention schedule on top of those, and we will not state a number here until one exists. If we adopt a defined schedule, we will state it in this section.

Data held by our AI model provider after a request is delivered is governed by that provider's own terms. DeepSeek's published terms for its developer platform do not set a fixed retention period and do not commit to excluding requests from model training; its privacy policy says personal data is kept as long as needed to provide the service and refers to an option to opt out of training. Kredo cannot recall or delete a request once DeepSeek has received it. This is why personal context is off until you turn it on, and why it is limited to capped totals rather than raw transactions.

14 Deleting your account and data

You can delete your Kredo account from inside the app, under Privacy & Data → Delete Account (also reachable from your profile). Deletion is permanent and is not reversible.

Deleting your account removes:

• your Kredo account and sign-in identity;
• your card records;
• your saved promos;
• your AI and personalization settings;
• your product analytics events.

The account deleted is always the one your active session belongs to — the request carries no account identifier that could name someone else. The app clears its local data only after our server confirms the deletion actually happened. Data held on your device, such as transactions, is removed with it or by deleting the app.

We may retain a limited record where retention is reasonably necessary to comply with law, resolve a dispute, prevent fraud or abuse, or maintain security. Operational logs already written by our infrastructure providers age out under those providers' own retention, as described in section 13.

You can also request deletion by writing to support@getkredo.app from the email address on the account.

15 Security

Measures actually in place:

• All traffic between the app and our backend uses HTTPS; the app rejects a backend address that is not an https:// URL.
• Every stored record is scoped to its owner by database row-level security policies: an account can read and write only its own card records, saved promos, and settings, and there is no path by which one account can read another's.
• Our backend functions re-verify your session with the authentication service on every request rather than trusting the request body for identity.
• Privileged database credentials exist only in our server environment and are never present in the app.
• Sign-in is rate limited, and email codes are six digits, expire in 10 minutes, and are subject to a per-address resend cooldown.
• Kredo holds no card numbers, security codes, PINs, or banking credentials to lose.

We describe the controls we actually operate and do not claim certifications we do not hold. No method of electronic storage or transmission is completely secure, and no service can promise perfect security.

16 Personal data breaches

If Kredo becomes aware of a personal data breach, we will investigate and take reasonable measures to contain and address it. Where notification is required by applicable law, Kredo will notify the National Privacy Commission and the affected data subjects within the period the law requires.

17 Your rights under Philippine data-protection law

If Philippine data-protection law applies to you, you may have the right to:

• be informed about the processing of your personal data;
• object to certain processing, and withdraw consent where processing is based on consent;
• access the personal data Kredo holds about you;
• request correction or rectification of inaccurate personal data;
• request erasure, blocking, or destruction where the legal requirements for that are met;
• obtain or request portability of qualifying personal data;
• seek damages where provided by law; and
• lodge a complaint with the Philippine National Privacy Commission (privacy.gov.ph).

Several of these you can exercise directly in the app at any time:

• see and edit every card and figure you entered — the figures live on your phone, and the card records we hold are shown in the app;
• turn AI access to your data on or off, in Privacy & Data;
• delete your account and its stored records.

For anything else — a copy of what we hold, a correction, an objection, or a question about this policy — write to support@getkredo.app from the email address on your account. We may need to verify your identity before acting on a request. We will respond within the period required by applicable law, and if we cannot fully grant a request — for example where the law permits or requires us to retain something — we will tell you why.

18 Children's privacy

Kredo is intended for adults aged 18 or older. It is not directed to children, and we do not knowingly permit persons under 18 to create a Kredo account. If we learn that personal data has been collected from a person who is not permitted to use the service, we will take appropriate steps to delete or otherwise handle that information as required by applicable law. If you believe this has happened, contact support@getkredo.app.

19 Changes to this policy

We may update this Privacy Policy when Kredo's features, providers, processing activities, or legal obligations change. When we do, we will revise the "Last updated" date at the top of this page.

If a change materially affects how we process personal data — a new category of collected data, a new service provider, a new AI provider, or a new purpose — we will provide appropriate notice in the app before the change takes effect, and we will obtain your consent where consent is required. We will not treat continued use of Kredo as consent to a new optional purpose for processing your personal data.

20 Contact

Kredo — support@getkredo.app

Personal Information Controller: Akkram Bederi.

If you believe your rights under the Data Privacy Act have been violated, you may also contact the National Privacy Commission at privacy.gov.ph.