Privacy & data handling

What is stored

Your sign-in email, account identifier and display name are handled through the configured Supabase project. Your private budget may include salary, expenses, chit fund receipts and contributions, cash settings, guest split records, subscription-tracker settings, and imported personal IOUs. Shared entries contain the amount, currency, original date, description, participants, approvals, and repayment history.

Who sees what

Your private budget, guest names, subscription tracker and automatic private-book history snapshots are restricted to your account by database access rules. A shared bill's participants can see the bill, shares, display names and approval history. Detailed repayment rows are visible to the debtor and creditor, not unrelated group participants. Accepted friends can see your display name and account code, not your email through Pocket's profile interface.

The deployment operator and authorized service administrators can access the configured infrastructure. This app does not provide end-to-end encryption. Hosting and database providers may retain operational logs. Do not describe any service as independently audited unless it has been audited.

Sign-in and device storage

Email ownership is checked through one-time sign-in codes. A verified email is not verification of a person's real-world identity. Confirm the name and account code privately before accepting a friend request.

The browser stores an authentication session so that you can stay signed in. The app's service worker stores only website files, not financial API responses. Financial data is loaded into memory while signed in. If you enable push notifications, Pocket stores that browser/device's Web Push subscription endpoint and encryption keys so the device can receive alerts. Sign-out removes the current device subscription. Exported backups are unencrypted and should be stored securely. Guest splits are not sent to the named guest and do not create an account or notification for them. Lock your device and sign out on shared devices.

Push notifications

Push notifications are optional and are used only for actions that need attention, such as a split-bill approval, loan approval, friend request, repayment or settlement confirmation, or cancellation request. Notification text is intentionally generic and does not include transaction amounts, salary, private expenses, or other private-budget details.

Temporary push-delivery jobs are operational reminders, not financial records. They are configured to expire after about 24 hours. The underlying bill, loan, approval, repayment, or other shared record remains according to the normal financial-history rules. Browser push subscriptions remain stored only while notifications are enabled for that device or until the push service reports the subscription invalid.

Sharing and retention

Friend invitations expire after seven days and can be claimed once. The creator must approve the claimed account. Shared entries are retained with their approval and repayment history. The app does not automatically forgive debts or erase someone else's financial record when an account is deleted. No money is transferred by this application.

Records remain until you delete private entries or your account, or until the operator applies a documented retention policy. Pocket keeps up to 30 automatic private-book history snapshots so accidental private-budget changes can be restored; older snapshots are pruned automatically. Infrastructure backup and log retention, data region, and international transfer arrangements depend on the operator's providers and settings; confirm these with the operator before entering sensitive data.

Deletion and exports

In Settings, export a private backup and shared audit history. Settings also provides Delete my account. This deletes your private budget, automatic private-book snapshots and sign-in identity, removes current friend connections and invitations, and changes your profile name to Deleted member. Shared records remain for other participants. Free-text titles and notes are not automatically scrubbed and may still contain identifying information.

Contact the operator for requests involving shared descriptions or infrastructure backups. No automatic time limit for removal from provider backups is promised by this application. The operator must define and communicate the actual policy before public launch.

Services and limits

The live build uses the operator's Supabase project for authentication, database storage, updates and the server-side Edge Function used to send Web Push. Its configured SMTP service sends sign-in emails, and the website is hosted on the operator's configured host (for example Cloudflare Pages). Browser push delivery is ultimately handled by the push service selected by the user's browser or operating system. The Supabase JavaScript library is loaded from jsDelivr. This code does not add advertising or analytics trackers.

This is an experimental personal bookkeeping app, not a bank or money-transfer service. There are no automated payments, collection attempts, interest calculations, or guarantees that participants entered accurate information. Public App Store distribution requires separate review, policies, testing and submission.