Developer
Effective October 26, 2026.
KACHING is operated by Krapht & Khode Foundry LLC ("we," "us"). Contact us about this policy or your data at support@kraphtandkhode.com.
Read KACHING!'s Terms of Use.
What KACHING does
KACHING lets you connect supported payment, seller, or bank accounts and view eligible transactions in an income ledger. It can send payment alerts and let you set goals. Availability depends on the providers enabled in your version of the app. KACHING does not move money or receive your provider password.
Information we handle
- Account and sign-in: an Apple account identifier or the email address used to request a sign-in code, KACHING account and session identifiers, and authentication records needed to protect the account. If email sign-in is available, our email delivery provider receives the address and one-time code to deliver the message. If Apple sign-in is available, Apple handles your Apple credentials.
- Passkeys: if you add a passkey, we store its public key, credential identifier, account association, creation/use timestamps, and verification metadata needed to authenticate your account and revoke access when you remove it. KACHING does not receive the passkey's private key or your Face ID or Touch ID biometric data.
- Connected services: provider account and connection identifiers, account or shop labels, authorization tokens, connection status, and the permissions you grant. Authorization tokens are stored encrypted on our service. You authorize each provider through its own flow.
- Financial activity: provider transaction identifiers, source, amount, currency, timestamp, status, and related account labels needed to display payments, calculate totals, prevent duplicates, and send alerts. Depending on the provider, a platform receipt may be gross sales before fees, tax, shipping, refunds, or disputes; a bank credit has a different meaning. KACHING does not collect your full card number or your bank sign-in password.
- KACHING Plus subscriptions: our service assigns a random subscription account identifier associated with your KACHING account. When you buy Plus, the app provides that identifier to Apple so the purchase can be linked to the correct KACHING account. The app sends signed subscription transaction records to our service for verification, and our service also accepts signed subscription updates from Apple. We store selected details, including transaction and original transaction identifiers, product, purchase environment, purchase and expiry dates, refund or revocation status, signing time, and any applicable billing grace period. Apple processes your App Store purchase and payment details; KACHING does not receive your full payment-card details through this subscription integration.
- Alerts and device information: a push token and alert preferences when you allow notifications, including whether amounts should be hidden outside the app.
- Support and site requests: information you choose to send us in a support request, and technical request information processed by our website and service host to deliver pages, protect the service, and diagnose failures.
Your ledger, goals, preferences, and any profile photo are also stored on your device. The profile photo crop is saved locally; KACHING does not upload that photo to its service. CSV exports are created on your device and can be shared to destinations you choose. Copies you export are outside KACHING's control.
Bank connections through Plaid
Bank features, where available, use Plaid's Transactions service. New bank connections are unavailable in this release; existing bank connections can continue syncing and may need reconnection through Plaid.
For an authorized bank connection, Plaid processes the account's available transaction history, including purchases and other activity, before KACHING filters eligible incoming credits for its ledger. That history may include physical transaction locations, including latitude and longitude where available. KACHING's ledger service does not retain those coordinate fields. KACHING stores account labels and masked account-number characters.
Plaid's returning-user flow may ask for your phone number to recognize saved connections. Plaid processes device, network, connection-event and error information for service delivery, security and Link analytics. Its default institution suggestions may use approximate location to personalize bank selection. Plaid also describes service improvement and financial insights in its End User Privacy Policy. These partner practices are separate from KACHING's own ledger filtering and do not mean the app requests GPS access.
How we use information
We use this information to create and protect your account, connect and refresh the services you authorize, display and reconcile your ledger, calculate goals, deliver requested alerts, respond to support requests, prevent abuse, and operate the service. Subscription records are linked to your KACHING account and used to verify and restore access, apply renewals and refunds, prevent unauthorized access, and enforce account allowances. We do not use your financial activity or subscription records for advertising or cross-app tracking.
Service providers and sharing
Our service is hosted by Cloudflare. Depending on the features you use, information is also processed by Apple for sign-in, push delivery and in-app purchases/subscription management; Resend for email sign-in; Zoho Mail for messages sent to our support mailbox; and the financial or marketplace service you choose to connect, such as Stripe, Plaid, Etsy, eBay, Square, or Shopify. We provide Apple with the subscription account identifier and receive transaction information needed to associate a purchase with your KACHING account and verify its status. Apple maintains its own records under its own privacy practices. These services have their own privacy practices. We share only what is needed to provide the selected feature, comply with law, or protect the service. We do not sell your financial records.
Storage, retention, and deletion
We keep account and connected-service records while your account is active or as needed to provide the service. This includes subscription records for expired or refunded purchases used by the current verification system; there is no automatic deletion schedule based solely on a subscription’s expiry. When deletion of your KACHING account successfully completes, its associated records, including subscription records, are removed from the active KACHING service. Account deletion can remain pending while external connection revocation is retried.
Cloudflare’s SQLite recovery history may retain an earlier state for up to 30 days. Deletion from the active service does not immediately erase that recovery history. We do not return a historical database to live service unless confirmed deletions and revoked sessions can be reapplied and verified. If that cannot be verified, we stop the proposed restore. If email sign-in is enabled, Resend states that email and log data is retained for 30 days on its Free, Pro and Scale plans, with backups retained for 7 days; Enterprise plans can have different retention. These are provider retention terms, not a guarantee that all KACHING or support-mail records share those limits. Sign-in codes expire after ten minutes. Account sessions expire after 30 days and may be ended earlier by sign-out, revocation, or deletion. Expiry prevents use of a record; it does not imply that all service-provider logs are immediately erased.
Signing out hides the account’s ledger from the app while retaining its separate local files and subscription security records for the next sign-in. The app saves a subscription account binding and hashes used to recognize subscription-verification attempts that have not been accepted in protected Keychain storage, rather than copies of the signed transactions.
After you explicitly request account deletion and our service acknowledges that request, the app can remove that account’s local ledger and associated subscription records as part of closing its local workspace, even while service-side deletion remains pending. Records belonging to another KACHING account are preserved. If secure storage or local files are unavailable, or a record cannot be read safely, local cleanup remains pending and is retried; the app does not treat that failure as completed erasure. No automatic time-based expiry is applied to the local subscription records.
Another device learns about revocation when it reconnects. Local session expiry locks account access but does not by itself erase every previously saved local file. Device backups and CSV copies may also contain earlier records. This local cleanup does not erase Apple’s own subscription records. Deleting your KACHING account or the app does not cancel an Apple subscription; manage or cancel it through your Apple account.
Support correspondence is processed and stored by Zoho Mail. Deleting a KACHING account does not automatically delete prior support correspondence. Contact support@kraphtandkhode.com to request help with support-mail access or deletion. We may need to verify the requested address and retain correspondence where needed to meet legal obligations, resolve disputes, prevent abuse, or address an unresolved request. We do not promise a fixed automatic deletion period for support mail. Moving a message to Trash does not establish permanent erasure of all provider copies.
You can disconnect a provider in the app and initiate deletion of your KACHING account from Profile. Disconnecting stops new imports; prior non-bank records may remain in your ledger, while disconnecting a Plaid bank removes its imported bank transactions. Deletion stops new imports and alerts and removes the account's stored sessions, connection tokens, and provider records from our active service. A Plaid connection is revoked as part of the deletion process; an Apple sign-in token is revoked when applicable. If an external revocation fails, deletion remains pending so it can be retried. Provider accounts themselves remain open, and you can revoke KACHING's access in the provider's own settings. We may retain records where required by law. Delete exported files from the places where you shared them separately.
You may request help with access, correction, export, or deletion at support@kraphtandkhode.com. We may need to verify that you control the account before acting on a request.
Security
We use access controls, encrypted connection credentials, and encrypted transport to protect information. No service can guarantee absolute security. Keep your device and provider accounts secure, and contact us if you suspect unauthorized access.
Children and changes
KACHING is intended for people operating a business or earning income, not children. We may update this policy as the app changes. The current version and effective date will appear on this page.
Website
KACHING's information pages do not use an account form, advertising tracker, or analytics script. Our site host processes technical requests to deliver the pages. The app's financial-data practices above apply when you use KACHING's connected features.