Dibsly is a local-first personal finance tracker for iOS. A Dibsly account is optional: with it, your data is kept in your account and on all your devices, on the website and, if you connect one, in your AI assistant (Claude, ChatGPT or Codex); you can also keep an account together with other people.
Data Stored by the App
Dibsly stores the financial information you enter in the app, including accounts, categories, transactions, transfers, currencies, notes, monthly plans and allocations, recurring payment schedules and their expense links, savings goals, payment drafts received through Shortcuts and their confirmation state, investment assets and activity, the sole-trader (FOP) settings described in “Sole Trader (FOP) Taxes”, debts and their pay-back days (“Debts and Debt Links”), credits — loans, mortgages, instalments, microloans and your credit cards' limits — with their terms and payments, and data imported from Dibsly, Monefy, Freedom Finance, or Interactive Brokers files, from bank statement files, or from the monobank personal API. Imported operations are stored together with a record of each imported statement row (its identity, date, amount, and what it became in Dibsly), the merchant categories you asked Dibsly to remember, and the mapping between monobank cards or jars and your Dibsly accounts. This information is stored locally on your device. If you sign in to a Dibsly account and sync is on, it is also kept in your account on Dibsly's server, as described in “Dibsly Account, Sync, Website and AI Assistants” below.
Data Collection
Without a Dibsly account, Dibsly does not collect personal data, financial data or tracking data on Dibsly-operated servers, and nothing leaves your device except as described in this policy. The only data the app sends on its own is the anonymous usage statistics described in “Usage Statistics”, which you can turn off. It also makes a few requests that carry none of your data: when Dibsly comes to the front, at most every six hours, it asks Apple's App Store which version of Dibsly is the latest (only the app's identifier and your device's region are sent), reads dibslyapp.com/app-config.json when a newer version is out, to learn the oldest version that still works, and downloads the table of sole-trader (FOP) tax rates by year from my.dibslyapp.com. These servers receive standard network metadata such as an IP address.
The app does not require a Dibsly account and contains no third-party analytics, advertising or tracking service. Only if you sign in to a Dibsly account does Dibsly's server receive your account details and, with sync, your finance data. If you choose Google Drive for backups, the encrypted backup files go from your device straight to your own Google Drive, never through Dibsly's server (see “Optional Backup & Recovery”). Signing in to a Dibsly account with Google is separate; what Dibsly receives then is described in “Dibsly Account”.
Usage Statistics
To learn which parts of Dibsly people use and which they never find, the app counts how many times a day its screens are opened and some of its buttons are tapped, such as adding an expense, switching an Analytics section or importing a statement. Once a day it sends the counts of the previous days to Dibsly's server: only the names of those screens and actions with their numbers, the date, and whether the app came from the App Store or TestFlight. Nothing you type or see is counted — no amounts, names, categories, accounts or notes — and the counts carry no account, no device identifier and no advertising identifier, so they cannot be linked to you or to your other data; the server adds them to totals per day and keeps no copy of what a device sent. Cloudflare receives standard network metadata such as an IP address, which Dibsly does not store with the counts. The totals are kept for about 13 months and seen only by the developer. You can turn this off in Settings → Preferences → “Share usage statistics”; the counts not yet sent are then deleted. Nothing is counted while the app shows test data.
Dibsly Account, Sync, Website and AI Assistants
The account (free). You sign in with Apple, with Google, or with an email address and a password — in the app or on Dibsly's website (my.dibslyapp.com); you can add or remove these ways in your profile while one stays. With Apple, Dibsly receives from Apple a stable identifier for you, the email address Apple gives (your own or a private relay address) and, the first time only, your name, and keeps a token Apple issues so the sign-in can be revoked when you delete the account. With Google, Dibsly asks Google only for your basic profile and receives a stable identifier for your Google account, its email address if Google has verified it, and your name; Dibsly gets no access to your Google data, such as your mail or files. With an email and a password, Dibsly keeps the address and a salted hash of the password, never the password itself; to confirm that the address is yours (when you sign up, set a new password or add the address in your profile), Dibsly sends a one-time code to it through Cloudflare Email Service; the code is kept only as a hash for 15 minutes. Dibsly never joins two accounts because their email addresses match. Dibsly keeps these details and an optional profile photo you choose. For each device signed in — an iPhone, a browser, an AI assistant's connection — Dibsly keeps its name (such as “iPhone” or “Chrome · Mac”), its kind, the app version, when it was last seen, and a random key the device keeps itself; sessions are kept only as hashes of their tokens. The account also keeps the language your app last used, so the website opens in it, and whether you may use a language offered only on request. The website keeps its session in a cookie that page scripts cannot read, and your choices of language, theme and similar display settings in your browser; it has no analytics or advertising cookies.
Sync and the website (Dibsly Premium). With sync, your finance data — the records listed in “Data Stored by the App”, the app's settings that belong to the account, and what you enter on the website or through your AI assistant, such as monthly savings, salary and sole-trader records, rates, goals and your own instructions for the assistant — is kept in your account's space on Dibsly's server, so every device you sign in to and the website show the same data. Dibsly's server computes the figures the website shows (balances, the portfolio, dividends, savings and taxes) from that data. To value your investments it fetches the last market price of the symbols you hold from Yahoo Finance; only the symbols are sent, and these prices are kept as shared market data, not as part of your account. To check Premium, the app sends the App Store's signed record of your subscription; Dibsly keeps its transaction identifier, product, environment and expiry, never payment details.
Shared accounts (Dibsly Premium, one member's subscription is enough). You can make one of your accounts shared and invite people with a link (dibslyapp.com/join/…); an unused link can be withdrawn and stops working once used or expired. Everyone who joins sees that account's balance and records — its operations, transfers, planned payments and the goals that use it — with the name and profile photo of the member who added each, and can add, change and delete them; family goals and splits made in the shared space are shared the same way. These records are kept in the shared space on Dibsly's server, not in your personal space. Your other accounts stay private unless you choose to show one: it stays in your personal space, and the other members see its total (for an investment account, its value and positions) and its operations only if you allow that. You can leave a shared account at any time; what you added stays with it for the others, and when the last member leaves, the shared space and everything in it is deleted.
Push notifications. If you are signed in to a Dibsly account (a free account is enough) and allow notifications, your iPhone gets a push token from Apple and gives it to Dibsly's server together with the app's language and whether you want to hear about operations others add. The server then sends short notifications through Apple Push Notification service: in a shared account, when another member adds an expense or an income, puts money into the shared account or takes it out, sends a request or answers yours, splits the account or changes a family goal (a notification names the member and the operation's title and amount); in Debts, when the other person records a movement for you to confirm, answers yours or reminds you of a debt (see “Debts and Debt Links”). You can switch off the notifications about others' operations in the app, and every notification in iOS Settings. The token is deleted when you sign out, remove the device, delete the account or turn notifications off for Dibsly.
Where it is kept. Dibsly's server runs on Cloudflare. Your account, its devices and sessions, and your space's data are stored in Cloudflare's European Union locations and encrypted at rest. Dibsly's server logs only the address of a request, its result and a short reason, never its content; Cloudflare receives standard network metadata such as an IP address. Dibsly does not use your data for anything other than providing the service to you: it does not look at it, sell it, or use it for advertising or for training AI. The developer can technically reach the stored data, and does so only to keep the service running and secure or when you ask for help with your account.
AI assistants (optional, Dibsly Premium). You can connect your own AI assistant to your account — Claude (Anthropic), ChatGPT or Codex (OpenAI); Dibsly asks you on its own page and shows the connection among your devices, where you can remove it at any time. A connection reaches only your own account. Once connected, the assistant can read, when you ask it to, your accounts, operations, plan, payment calendar, goals, investments, debts, credits and sole-trader records. After you confirm in the chat it can record, change or delete your expenses and incomes, import a bank statement, record or remove broker trades, change the month's plan, calendar payments, goals, categories and your accounts' names, icons and visibility, record a debt, and save the records described above (savings months, salary and sole-trader records, rates, your notes) — every such change is kept in your account's AI journal, where you can undo it; balances, credits and other transfers are read-only for it, and no tool moves real money. What the assistant reads is processed by its provider under your agreement with that provider and its privacy policy; Dibsly sends nothing to an assistant you have not connected. The connection's tokens are stored only as hashes, and its grant (which account and connection it belongs to, encrypted with a key only the token unlocks) in Cloudflare's global key-value store.
Deleting. “Remove from this iPhone” signs that device out and keeps your account. Removing a device or an assistant's connection, in the app's profile or on the website, ends its access. “Delete account” in the app erases your account, its devices and sessions, your profile photo and every record of your space on Dibsly's server, revokes Sign in with Apple, and signs out every device; the data on your devices is erased too.
The “What are you missing?” form and “I want this” on dibslyapp.com. No account needed. When you send the form, Dibsly's server keeps the text, your e-mail if you leave it, the language and the page, and a hash of your IP address to limit messages per hour; only the Dibsly team sees the text and the e-mail, and a copy goes to the support mailbox. The “I want this” button keeps a random ID and your votes in your browser; the server keeps only a hash of that ID and the item you voted for. To have your message deleted, write to dibslysupport@gmail.com.
Market Data Requests
When you search for an investment symbol, refresh a quote, or open portfolio history, Dibsly contacts public market-data endpoints, currently including Nasdaq services and Yahoo Finance historical chart data. A request can include the ticker, search text, requested date range, chart interval, and standard network metadata visible to the provider, such as an IP address. Dibsly does not send account balances, transaction history, notes, or imported broker files with these requests.
Currency Rate Requests
Dibsly retrieves current reference exchange rates from the National Bank of Ukraine. This request does not include account balances, transactions, plans, notes, or imported files. The provider can receive standard network metadata such as an IP address.
Sole Trader (FOP) Taxes
Dibsly 1.0.2 and later can keep the taxes of a Ukrainian sole trader (ФОП, 3rd group), if you turn it on in Settings → Features → FOP. Its settings — the tax group, who pays the social contribution (ESV), which of your accounts are the FOP's, when you pay, the hourly rate and the payout conditions with each month's hours and figures, the declarations you marked filed and the region and community you chose for payment details — are stored like your other records: on your device, in encrypted backups and, with sync, in your Dibsly account. The taxes, deadlines and declaration figures are worked out on your device from the incomes you recorded. The rates by year — the minimum wage, the single tax, the military levy, ESV and the income limit — come with the app and are updated from a table on my.dibslyapp.com, which the app downloads without sending anything about you (see “Data Collection”).
To value an income in another currency, Dibsly asks the National Bank of Ukraine's public statistics service for the official rates of that currency over a range of days and keeps them on the device. The request contains the currency and the dates only — no amounts, account names, tax numbers or other records — and the provider can receive standard network metadata such as an IP address.
Payment details (the State Tax Service's recipient, code and IBAN for each payment) come from the tax service's open data on tax.gov.ua (CC BY 4.0), bundled in the app: choosing a community sends nothing. Dibsly only shows and copies these details; it never pays a tax, files a declaration or connects to your tax account or e-cabinet. FOP reminders are local notifications, like payment reminders below; they can include the quarter, the deadline and, where shown, the amount, and Hide amounts does not redact their previews.
Debts and Debt Links
Dibsly 1.0.2 and later keeps debts — who owes you and whom you owe — as people and shops with their loans, returns and pay-back days. They are your records like any other: on your device, in encrypted backups and, with sync, in your Dibsly account. Finding a returned debt among your bank's notifications compares the sender's name with your people's names on your device.
Credits (Dibsly 1.0.2 and later) — a loan, a mortgage, an instalment, a microloan or a credit card's limit — are kept the same way, as your own records: their terms (the amount, rate, term and payment day) and the payments you record. The schedule, the interest and what an early repayment would save are worked out on your device; the reminders of a payment are local notifications your iPhone shows by itself. A monobank card's limit comes with the data of your monobank connection; nothing about your credits is sent to your bank or anyone else.
If you are signed in to a Dibsly account (a free account is enough) and tap Share on a person's page, Dibsly's server keeps a link to that debt with what is between the two of you: the currency, the amount and each movement's day, amount and note (up to 100) — never your accounts, balances or other records. Whoever opens the link and signs in sees your account's name and those amounts and notes. A link that nobody accepts expires after 30 days. Once accepted, each of you sees the other in Debts, and every movement either of you records on that person is sent to the server once — its amount, day and note — for the other to confirm or decline; the other person gets a push notification with your name and the amount, and you get one with their answer. Once the link is accepted, Share becomes Remind: it sends the other person a push through Dibsly's server with your name, what they owe now and, if you write them, your own words (up to 200 characters). The words go only into that push and are not kept on the server; the server keeps only when you last reminded, so you can remind once an hour. These links and movements are deleted with either person's Dibsly account.
Recurring Payments and Local Notifications
Recurring schedules and their links to recorded expenses stay on the device and are included in optional encrypted backups. Searching past expenses to suggest a payment name, category and estimated amount happens on the device; it does not send transaction history to a search service.
If you grant notification permission and enable a reminder, Dibsly schedules local notifications through iOS. Their text includes the payment name, estimated amount/currency and expected date. App Lock and Hide amounts do not redact these notification previews. You control notification permissions and lock-screen previews in iOS Settings. Opening Dibsly from a reminder still respects App Lock. These reminders are local: no Dibsly server or bank connection is involved.
The sole trader's deadlines and the credits' payments (three days before and on the day, and a credit card's grace period) are reminded the same way: local notifications with the deadline or the credit's name, the amount and the day, worked out on your device.
Apple Pay Drafts through Shortcuts
If you enable Apple Pay capture and configure a personal automation in iPhone Shortcuts, the Dibsly action stores the inputs supplied by that automation: available amount and currency, merchant, selected Dibsly account, optional card name and payment date, and a derived retry key when a source event identifier is supplied. Dibsly does not directly read your Wallet transaction history or connect to your bank. The automation is configured and managed in Apple’s Shortcuts app.
Payments wait locally as drafts until you confirm or link them to an expense. Note/category suggestions search recent expenses on the device. Drafts and handled-payment receipts are included in optional encrypted Dibsly backups; iOS personal automations are not included. Capture returns a generic result without payment details, while viewing and confirming payments follows the app’s existing lock and amount-privacy settings. Without a Dibsly account this feature adds no server or remote recipient; with sync, drafts are also kept in your account, so the website shows them and you can record or discard them there.
Turning Apple Pay off stops new captures and hides Activity while keeping existing drafts. It does not disable the iOS automation. Discarding or confirming a draft retains a local receipt, including its captured details and retry key, to prevent explicit event retries from recreating it. To remove all draft and receipt data, use Delete All Data; existing cloud backups remain governed by the backup/deletion controls below.
Data Sharing
Dibsly does not sell or rent your data and does not share it for advertising or cross-app tracking.
Financial records can leave your device only when you choose to export, share, enable backup, sign in to a Dibsly account with sync, connect an AI assistant, or use Dibsly's AI features. The account, sync and the assistants are described above; optional iCloud Drive and Google Drive backup and the AI features are described below. Market-data requests are limited as described above.
Optional Backup & Recovery
Dibsly supports optional encrypted backup to iCloud Drive and Google Drive. Backup is not live synchronization, and the app remains usable without it.
You choose the iCloud Drive folder for backups through Apple's file-provider interface; the backup files stay visible there in the Files app. Apple may receive the encrypted backup file and standard account, device, and network information under your Apple agreement and privacy settings. Dibsly has no server in between and does not use iCloud to synchronize your finance database.
Google Drive. If you connect Google Drive, Dibsly asks Google only for access to the files Dibsly itself creates in your Drive (the drive.file permission) and for your basic profile, so the app can show which Google account is connected; Dibsly cannot see or open any other file in your Drive. Backups go to a visible folder named “Dibsly Backups”. The access Google grants is kept only in this device's Keychain (available after first unlock, this device only); it is never included in a backup or export and is never sent to Dibsly's server, which receives neither your Google Drive data nor your backups. Connecting Google Drive is separate from signing in to a Dibsly account with Google: one does not give the other any access. Google receives the encrypted backup files and standard account, device and network information under Google's terms and privacy policy. Disconnecting Google Drive in Dibsly revokes this access at Google; you can also remove it at any time in your Google Account under third-party connections. Dibsly's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: that information is used only to save, list, restore and delete your Dibsly backups and to show the connected account; it is not used for advertising, not sold or transferred to others, not used to train AI models, and not read by people.
Backup files are encrypted and integrity-protected before upload. The recovery password is not stored beside a backup; when automatic backup is enabled, the routine credential is stored only in this device's data-protection Keychain. Automatic backup is opt-in and best-effort: after setup, eligible Daily or Weekly attempts run when the app becomes active and, when iOS allows it, in the background (usually while the device is idle), only if backed-up data has changed; setup or an explicit retry can also trigger an attempt. iOS decides when background attempts run, so exact timing is not guaranteed.
Automatic retention keeps the newest 5 automatic backups created by this installation in each backup location when cleanup succeeds. Automatic backups made by another device or an earlier installation, manual backups, and files not recognized as Dibsly automatic backups are never removed by this cleanup. Provider failures may delay cleanup.
Disconnecting iCloud Drive or Google Drive in Dibsly stops backups there but does not delete existing backup files; “Delete all Dibsly backups & disconnect” first deletes Dibsly's backup files from Google Drive. Deleting all local Dibsly data turns automatic backup off and does not delete existing cloud backups.
Before managed restore or CSV Replace mutates local data, Dibsly creates and verifies an encrypted emergency snapshot in the app's local Application Support storage. Its local-only encryption credential is held in the device Keychain. Dibsly does not upload these emergency files or their credentials. After a new snapshot is verified, Dibsly keeps the five newest Dibsly-managed emergency snapshots on a best-effort basis and does not remove unrelated files. Only exact pre-restore-<UUID>.dibslybackup and pre-replace-import-<UUID>.dibslybackup names are eligible for this pruning.
File Import and Export
Dibsly can import and export CSV files and import supported broker CSV/XLSX reports when you explicitly select those actions. Files selected through the iOS document picker remain under your control.
Bank Statement Import
Dibsly reads the statement files of four banks itself (monobank CSV, XLS and PDF; UKRSIBBANK, PrivatBank and KredoBank PDF). This section covers those files; a statement of any other bank is read by the AI, as described in “Statements of other banks” under “AI Features”. A file of these four banks is read entirely on your device: it is never uploaded, and no part of it is sent to Dibsly or to any other service. Dibsly reads only the fields it needs — dates, operation details, amounts, currencies, balances, card masks and the account IBAN — and never parses the tax number, passport data, date of birth or registration address that bank statements print in their headers. The account holder's name is used in memory only, to recognize transfers between your own accounts, and is then discarded. Card masks and a masked form of the IBAN (country code and the last digits) are stored so later imports recognize the same account; full card numbers and full IBANs are not stored. Import History keeps the bank, the file name you chose, the period and the counts, not the operations themselves. You can also open a statement in Dibsly from another app (Share or Open In); the file is handed to Dibsly on your device and read the same way.
monobank Connection
If you connect monobank, Dibsly uses the personal token you create yourself at api.monobank.ua. The token is stored in the Keychain of that device only (available after first unlock, this device only). It is never included in a backup, a CSV export, Import History, a diagnostic report, or anything sent to Dibsly; Dibsly has no server that could receive it.
Synchronization starts only when you connect monobank or tap Sync; a longer history import you started can continue in the background, paced by monobank's request limits. Dibsly calls api.monobank.ua directly from your device with your token and asks for your accounts and jars and for the operations of the accounts you mapped, within the period shown on screen. monobank receives the request and standard network metadata such as an IP address; it does not receive anything you entered in Dibsly. The answer — your cards, jars, balances and operations — stays on the device and is shown in a preview before anything is written.
Disconnecting deletes the token and the card and jar mapping from the device; operations already imported stay in your data. Revoking the token itself is done in your monobank cabinet at api.monobank.ua.
AI Features (optional)
Dibsly's AI is OpenAI (the maker of the GPT models), reached through Dibsly's own relay server. Receipt photos use it in the free version (10 receipts a month); statements of other banks read by the AI are free for 3 statements in all; the chat for 20 questions a month; bank notifications read by the AI, AI categorization, up to 300 receipts a month, up to 25 statements of other banks a month, voice entry with the AI and more questions in the chat are part of Dibsly Premium. Nothing is sent until you allow it on one page that says what is sent and who receives it, with its own switch for the AI features and for the chat: Dibsly shows it during the first setup and, if you chose “Not now”, again the first time a feature or the chat needs the AI. Everything else in Dibsly works without it. The switches, “AI in Dibsly” and “Ask Dibsly”, are in Settings → Features → “AI in Dibsly” (in Dibsly 1.0.1 and earlier, in Settings → Preferences); turning one off withdraws its permission; without Premium the AI is used only for receipts, statements of other banks and the chat, within their free limits. Reading the statements of monobank, PrivatBank, UKRSIBBANK and KredoBank, Investments, Apple Pay through Wallet and voice entry your phone understands by itself work without the AI.
AI categorization (Dibsly Premium). AI categorization helps with the operations Dibsly could not categorize itself: imported operations when you tap Sort with AI, and new payments captured from bank notifications or Apple Pay, whose category it proposes before you save them. Once you allow the AI, Dibsly sends to OpenAI, through Dibsly's own relay server, the names of those merchants as your bank wrote them (for a bill paid to a company through internet banking: the company and the service, without an address, a phone number or an account number), the names of your categories, and up to eight merchants you already filed under each category. Long numbers are removed from every name before it is sent. Amounts, dates, accounts, balances, notes, card or account numbers are never sent, and transfers to and from people are never sent at all: Dibsly files them as transfers itself. Your device proves it runs a genuine copy of Dibsly through Apple's App Attest. Dibsly's relay, run on Cloudflare, passes each request to OpenAI and keeps none of its content — only an anonymous key of your device and how many requests it made this month and today, to hold the AI's limits; the relay and OpenAI receive standard network metadata such as an IP address. Requests are sent with storage off; under OpenAI's API terms the data is kept for at most 30 days for abuse monitoring and is not used to train models. With Premium, the app also sends the relay the App Store's signed record of your subscription; the relay checks Apple's signature and keeps none of it, only whether Premium is active and until when inside its short-lived session token.
Bank notifications read by the AI (Dibsly Premium, iOS 27 or later). If you set up the Dibsly automation for your bank apps in Shortcuts and allow Dibsly's AI, each notification from those apps that names an amount with a currency is saved on your device and its text is sent the same way to OpenAI, which reads the amount, the currency, the merchant or sender, the card's last digits and any fee. Full card numbers, IBANs and phone numbers in the text are replaced before it is sent; the rest of the notification — which can include your balance and the name of a person who sent you money — is sent as it is. Notifications without an amount, such as codes and offers, are not sent. The result becomes a draft in Activity that you confirm or discard; a notification that could not be read yet waits on your device for up to a week. The same OpenAI terms apply: the data is kept for at most 30 days and is not used to train models.
Voice entry (free; the AI with Dibsly Premium). When you tap the microphone or ask Siri to record in Dibsly, Apple's speech recognition turns what you say into text — on your device when your iPhone supports it for the chosen language, otherwise through Apple's servers under Apple's privacy policy. Dibsly asks for the microphone and speech recognition only for this and keeps no recording. The text is read on your device first; only when Dibsly cannot find the amount or the category itself, and only with Dibsly Premium and the AI allowed, the phrase is sent the same way to OpenAI together with the names of your accounts and categories (no balances, amounts or history). The result is saved as an operation you can undo or edit at once.
Statements of other banks (3 in all for free, up to 25 a month with Dibsly Premium). Dibsly reads the statements of monobank, PrivatBank, UKRSIBBANK and KredoBank — and their sole-trader statements — on your device, without the AI. A statement file of any other bank (PDF, CSV, XLS or XLSX) that you choose is read by the AI after you allow it: its text page by page, and a page without text (a scan) as a picture, is sent the same way to OpenAI, which returns the account, the period, the balances and each operation — its date, amount and currency, the merchant or the other side with its account or card number as printed, and a category. Every page goes as the bank printed it, the header included: your name, your address, tax number and date of birth if the bank prints them, full account and card numbers, and balances. Dibsly removes nothing from it before it is sent. After you import, Dibsly keeps only the operations and the account from the preview, with card numbers and IBANs masked; the rest of the file is not kept. Neither Dibsly nor its relay keeps the file or its content; to hold the limits the relay keeps only an anonymous key of your device (or your account's identifier when you are signed in), a random identifier of the file, how many pages and scanned pages it had and how many statements you read. The result is shown as the usual preview to check before anything is imported, marked as read by the AI. The same OpenAI terms apply: the data is kept for at most 30 days and is not used to train models.
Receipt photos and split bills (10 receipts a month free, up to 300 with Dibsly Premium). Receipts are read by the AI in the free version too, after you allow it. A receipt you photograph or choose, or a photo or screenshot of one you share to Dibsly from another app (it waits in Dibsly's own storage on your device until Dibsly reads it), is straightened on your device, and the photo and the names of your expense categories are sent the same way to OpenAI, which returns the shop, the date, the total and each item with its category; neither Dibsly nor its relay keeps the photo. The result becomes drafts in Activity that you confirm or discard. If you share a split bill, the receipt itself — the shop, the items, their amounts and the total, not your accounts — is sent to Dibsly's server, which keeps it for 30 days under a short code so the link you send (dibslyapp.com/s/…) can open it; nothing else is stored with it, not your account or device. Without the network the app shares a longer link that carries the receipt inside the part of the address after #, which browsers do not send to any server. Dibsly's page that opens either link runs in your friend's browser, and the items they tap stay on their device. The same OpenAI terms apply: the data is kept for at most 30 days and is not used to train models.
Chat with Dibsly (20 questions a month free, more with Dibsly Premium). The chat has its own switch on the same permission page. Your question and the earlier messages of the conversation are sent the same way to OpenAI; to answer, the AI asks your device for what it needs and your device sends only that — totals, the operations it found (their dates, titles, amounts, categories and accounts), your plan's limits, your accounts' names and balances, your categories' names, the people and shops of your debts with what is between you, and your credits with their terms, payments and schedule. Nothing is changed by the AI: a change it proposes (operations, a category or an account, a plan's limit, a debt, a credit's payment) is made on your device only when you tap Save, and you can undo it. The conversation itself is kept only on your device — it is not synced, not in your backups and not on Dibsly's server — and is deleted with “Clear the conversation”; turning the chat off withdraws its permission. Dibsly's relay counts your questions and their cost for the chat's limits, and how long each answer took (kept 120 days, without your account's name), and keeps none of their content. A card you share from the chat is a picture made on your device and shared only where you choose. The same OpenAI terms apply: the data is kept for at most 30 days and is not used to train models.
Chat with Dibsly on the website (Dibsly Premium). On my.dibslyapp.com the chat asks for your permission before the first question. Your question and up to ten earlier messages of the conversation go to Dibsly's server, which sends them on to OpenAI through Dibsly's relay in the same way; to answer, the AI asks the server for what it needs, and the server sends only that — totals by category, the operations found (their dates, titles, amounts, categories and accounts), accounts with their balances, the plan, payments, goals, investments, debts and credits. The chat changes nothing by itself: a change it proposes (operations moved to another category, renamed, or one operation's amount, day or account) is shown as a card, saved only when you press Save, and kept in your account's AI journal, where you can undo it. The conversation is kept only in that browser, not on Dibsly's server, and the Clear button deletes it; the server and the relay count your questions and their cost for the chat's limits by your account's identifier and keep none of their content. The same OpenAI terms apply: the data is kept no longer than 30 days and is not used to train models.
The answers (a category, a confidence and a readable merchant name per merchant, which Dibsly shows in lists instead of the bank's text) and a record of which operations the AI filed are kept on your device only; they are not part of backups or exports and are erased by Delete All Data. Usage counters for the AI allowance (numbers of merchants, phrases and receipts, not their contents) are kept in the device Keychain. You can switch the AI off at any time in Settings → Features → “AI in Dibsly” (in Dibsly 1.0.1 and earlier, in Settings → Preferences); without Premium nothing goes to the AI except receipts, statements of other banks and the chat's questions, within their free limits. Every category the AI chose can be changed like any other.
Dibsly Premium Subscription
Dibsly Premium (sync of your account across devices, the website and your AI assistant; shared accounts; bank notifications of any bank read by the AI; up to 25 statements of other banks a month read by the AI; AI categorization; up to 300 receipts a month; voice entry with the AI and more questions in the chat) is an auto-renewable subscription sold through the App Store. Apple processes the purchase, the payment and the renewals under your Apple account; Dibsly never receives your payment details, and the purchase does not give Dibsly your name or email. On your device Dibsly reads only whether the subscription is active and until when, through Apple's StoreKit. You manage and cancel the subscription in iOS Settings → your name → Subscriptions. Everything else, including Investments, goals and the account itself, is free. Your data stays on your device whether or not you subscribe: when Premium ends, the Premium features stop — sync, the website and the assistants for your own data, while a shared account keeps syncing as long as another member has Premium — receipts return to 10 a month, and nothing is deleted from your devices or your account.
Data Retention and Deletion
Local data remains on your device until you edit it, delete it, remove the app, or use Dibsly's Delete All Data action. Data in a Dibsly account remains until you delete it or delete the account; a shared account's records remain while anyone is still in it; shared split bills are deleted after 30 days; a debt link nobody accepted expires after 30 days. Cloud backups remain in your iCloud Drive until you delete them there, from Dibsly's backup list, or through automatic retention described above. Dibsly does not control Apple's own retention practices.
Your Choices
You can use Dibsly without an account, turn off the usage statistics, use it without backup, disable automatic backup, disconnect iCloud Drive or Google Drive, delete Dibsly backups, export your data, or delete all local Dibsly data from the app. With an account you can remove any device or assistant's connection, leave a shared account, switch off notifications about others' operations, and delete the account with everything in it. Bank statement import, the monobank connection and the AI features are optional: you can use Dibsly without them, disconnect monobank at any time, and revoke its token in your monobank cabinet.
Contact
For privacy questions, contact:
Public policy: https://dibslyapp.com/privacy.html