Scope of This Policy
linkThis Privacy Policy explains how AgileBudget collects, uses, stores, discloses, and protects personal information when you use our website, mobile applications, customer support channels, and related services.
The exact information we collect depends on how you interact with AgileBudget, what features you use, whether you join shared boards, whether you subscribe, and whether you choose to use AI or third-party sign-in.
Information We Collect
linkWe collect information you give us directly, information created through your use of AgileBudget, information received from providers you choose to connect, and limited technical information collected automatically from your device or browser.
- Account and profile data, such as name, email address, avatar, account identifiers, preferences, and referral information.
- Workspace data, such as boards, periods, tasks, recurring items, comments, collaborators, due dates, amounts, account labels, and activity history.
- Attachments and uploaded files, such as receipts, screenshots, PDFs, and other files you decide to store in AgileBudget. This does not include temporary AI scan source files that are processed without retained storage.
- Subscription and transaction metadata, such as plan level, entitlement status, renewal state, store product identifiers, and RevenueCat customer identifiers.
- Device, app, and website usage data, such as IP address, browser type, device type, app version, locale, timestamps, and diagnostic logs.
Google User Data
linkIf you sign in with Google, we may receive your name, email address, profile photo, and a stable account identifier from Google. We use that information only to authenticate you, create or maintain your AgileBudget account, secure access, and support your use of product.
We do not sell Google user data, we do not use Google user data obtained through sign-in for advertising, and we do not use that Google user data to train generalized AI or machine-learning models.
Workspace Data, Comments, and Files
linkAgileBudget stores budgeting and collaboration data you add or generate, including shared board structure, tasks, comments, recurring items, member roles, and uploaded files. This allows invited members to collaborate inside shared boards.
Because AgileBudget is collaborative, information you place in a shared board may be visible to other members of that board based on the permissions and roles supported by product.
AI Prompts, Context, and Output
linkIf you use AgileBudget AI features, we may process your prompts, recent message history, selected workspace context, generated output, and temporary file inputs such as statement or receipt images or PDFs to provide AI responses, suggestions, previews, exports, scans, abuse prevention, and feature reliability.
AI scan source files are processed only to complete your request and are not stored by AgileBudget after processing, except for brief transient handling required to deliver request to our AI provider and return result.
AI output in chat features may be stored in your account so you can revisit or export it later, but AI scanner source files and scanner-only extracted rows are not retained by backend unless you confirm creation of tasks or other saved records.
We do not use your AI prompts, AI file inputs, workspace context, or AI responses to train generalized AI or machine-learning models for AgileBudget or third-party providers.
Avoid submitting unnecessary sensitive personal data, confidential credentials, or regulated information into AI features.
How We Use Information
linkWe use personal information to operate AgileBudget, authenticate users, power shared budgeting workflows, support purchases, secure accounts, respond to support requests, and improve reliability and design.
- Create and manage accounts, boards, invitations, and access permissions.
- Store and sync budgeting data, files, comments, and activity across devices and members.
- Process subscriptions, track entitlements, and provide account or billing support.
- Detect abuse, investigate incidents, prevent fraud, and maintain service security.
- Provide notifications, password resets, legal notices, and important product communications.
- Analyze usage patterns to improve stability, performance, features, and support quality.
Third-Party Services and Data Sharing
linkWe share information with service providers only as needed to run AgileBudget, meet legal obligations, protect rights and safety, or support a business event such as financing, acquisition, or merger.
Providers may process data under contracts or platform terms that limit how they can use information on our behalf. Their handling of data is also subject to their own policies and applicable law.
- Supabase: authentication, database, storage, and backend execution.
- Google: sign-in, account identity, and related platform flows when you choose them.
- RevenueCat: subscription entitlement management and subscription event syncing.
- Apple App Store and Google Play: purchase processing, billing records, renewals, and refunds.
- Vercel: website hosting, web delivery, and some rendered-output infrastructure.
- OpenAI: AI assistant, AI scan processing, and related response-generation services. We send only data needed to fulfill your request and do not use your AI inputs or outputs to train generalized AI models.
- Expo and mobile platform tooling: updates, linking, and push-notification support.
- Other vendors we may use from time to time for infrastructure, storage, delivery, diagnostics, support, security, and legal compliance.
Retention
linkWe keep personal information for as long as reasonably necessary to provide AgileBudget, maintain shared boards, support subscriptions, detect abuse, resolve disputes, comply with legal obligations, and keep appropriate business records.
Retention periods vary by data type, account state, legal obligations, and operational needs. We may retain limited records after deletion requests when required for fraud prevention, security, tax, accounting, or legal compliance.
Security
linkWe use reasonable administrative, technical, and organizational safeguards intended to protect personal information. No method of storage, transmission, or software operation is perfectly secure, so we cannot guarantee absolute security.
You can help by using strong login credentials, keeping your devices updated, reviewing who has access to shared boards, and avoiding unnecessary sensitive uploads.
Your Choices and Rights
linkDepending on where you live, you may have rights to access, correct, export, delete, or object to some uses of your personal information. You may also be able to manage parts of your data directly in app, such as profile details, invitations, comments, and uploaded content.
To request help with privacy rights, deletion, or Google-user-data questions, contact us at support@agilebudget.cc from email tied to your AgileBudget account when possible.
International Transfers
linkYour information may be processed in countries where we or our providers operate. Those locations may have data-protection laws different from laws in your home jurisdiction.
Where required, we take reasonable steps intended to support lawful transfers and appropriate safeguards.
Children's Privacy
linkAgileBudget is not directed to children under 13, and we do not knowingly collect personal information from children under 13 without consent where law requires it. If you believe a child submitted personal information to us, contact us so we can review and respond.
Changes to This Policy
linkWe may update this Privacy Policy from time to time. When we do, we will update last-updated date on this page and may provide additional notice for material changes.
Your continued use of AgileBudget after changes take effect means revised policy applies to future use of service, subject to law.
Contact Information
linkQuestions, privacy requests, deletion requests, and Google-user-data questions should be sent to our support inbox.
Email: support@agilebudget.cc
Questions about this page?
Reach out and we will point you to the right place. Legal and privacy questions should go through our email inbox first so we can route them properly.
