Pre-release document for review

Privacy Policy

Effective date: to be confirmed before launch · Draft updated October 19, 2026
Pre-release notice: These pages are available for review during commercial setup. Contact channels, data-handling practices, retention and payment terms must be confirmed before public launch or app-store submission.

1. Operator and scope

Vibe Supply Products LLC operates Monthly Finances, a service for manually recording household budgets, financial trackers, recurring payments, and receipts. This document concerns the commercial Monthly Finances service, not the operator's separate personal household application.

2. Information used by the service

  • Account and authentication: email address, account identifiers, sign-in and security events, and applicable access permissions.
  • Financial information you supply: account or tracker names, budgets, paydays, planned bills, transaction descriptions, categories, amounts, dates and recurring schedules.
  • Receipts: photos, attachments, extracted merchant and total information and associated notes when you choose to upload them.
  • Household sharing: member invitations, role settings and explicitly granted tracker access.
  • Technical records: limited operational and security logs needed to protect and maintain the service.

3. How information is used

To provide account sign-in; organize transactions and receipts; calculate user-requested forecasts and reports; process AI features you initiate; deliver essential service notices; protect against abuse; and respond to support and deletion requests. Financial forecasts are estimates based on available entries and are not guarantees of actual bank balances.

4. Access and sharing

Financial entries and receipts are scoped to authorized financial trackers. Access may be given to another household member only through permissions granted in the application. Operational providers may process data on behalf of the service for hosting, authentication, AI features, payment processing or support as appropriate. An internal operator console should show aggregate usage metrics rather than unrelated customers' expense details.

5. Hosting and third-party processing

The current design uses Cloudflare for website delivery and Supabase for authentication, database and private receipt storage. AI features may send selected receipt images or finance-related text to an AI processing provider to respond to your request. The specific AI vendor(s), geographic processing locations and any applicable data-use settings must be verified and disclosed before public launch. If payments are enabled, app stores and payment processors will also process payment details under their own policies.

6. Retention and deletion

Financial information is kept to provide the service while your account is active. You can request removal of receipts, entries or your account. Some records may need to be retained for legitimate billing, security or legal reasons; backup systems may have separate deletion cycles. Exact retention periods and the full multi-member household deletion procedure must be confirmed before launch. See account deletion.

7. Security

The service uses authenticated access, database row-level policies and private receipt storage. No online service can guarantee absolute security. Enable available account protections and do not share passwords or recovery codes.

8. Your choices

You may ask for access, correction or deletion of information as applicable. You can manage household membership and account sharing in the application. Optional AI features and notifications should be presented with appropriate choices and permissions.

9. Contact and changes

Use the support page for questions. Material changes to this policy will be reflected in an updated version and, where appropriate, communicated to existing users.