Effective date: May 27, 2026

Privacy Policy

ZiplyFriend helps users organize daily spending, subscriptions, receipts, bills, invoices, warranties, shared plans, contacts, and assistant conversations. This policy explains what information the app may handle, why it is used, and what choices users have.

Who this policy is for

This policy applies to the ZiplyFriend mobile app, the ZiplyFriend assistant features, the public website at `aiguardian.my`, and related backend services used to answer AI requests. If the app is used in demo or mock mode, data is mainly stored locally on the device. If live AI mode is enabled, relevant request data may be sent to the backend and AI service providers so ZiplyFriend can respond.

Information we may collect or process

Chat and voice requests Messages, transcribed speech, assistant replies, and limited context needed to answer the user’s request.

Spending records Amounts, categories, notes, dates, meal or plan labels such as breakfast, lunch, dinner, drinks, groceries, travel, utilities, shopping, and shared contacts selected by the user.

Subscriptions and renewals Service names, prices, billing cycles, renewal dates, data service details, reminders, notes, and cancellation or refund planning information.

Receipts, bills, and invoices Images selected or captured by the user, extracted merchant names, totals, dates, categories, warranty notes, and AI-generated draft plans.

Contacts Contact names and selected details after permission is granted, used so users can tag or share spending with friends. Contacts are not imported unless the user allows it.

App settings and diagnostics Preferences such as mock or live AI mode, local settings, feature state, basic error information, and backend health status needed to keep the service working.

Device permissions

ZiplyFriend asks for permissions only when a feature needs them. Microphone and speech permissions support voice conversations and voice spending. Camera and photo permissions support bill, invoice, and receipt capture. Contacts permission supports friend-based spending and shared plans. Users can deny or revoke permissions in iOS or Android settings; some features may stop working until permission is restored.

How information is used

To provide chat, voice, receipt reading, and spending organization features.
To calculate daily, weekly, and monthly spending summaries.
To create draft plans from bills, invoices, receipts, meals, drinks, and data services.
To track renewal, warranty, and subscription dates selected by the user.
To prepare user-approved drafts for refunds, cancellations, support messages, or safety checks.
To maintain security, prevent abuse, troubleshoot errors, and improve reliability.

AI processing and third-party services

Live AI mode sends the user’s request and relevant context to the ZiplyFriend backend. The backend may use OpenAI API services to generate chat replies, analyze uploaded bill images, or create voice output. API keys are handled server-side and should not be stored inside the mobile app. AI-generated output can be incomplete or incorrect, so users should review all summaries, dates, totals, and recommendations before acting on them.

Sharing and selling data

ZiplyFriend does not sell personal data. User information should not be shared with banks, merchants, app stores, advertisers, or unrelated third parties unless the user asks for a specific action or a future production feature clearly explains that sharing. Service providers may process data only to operate the app, backend, hosting, AI, analytics, support, security, or delivery features.

Storage, retention, and deletion

The current app includes local demo storage on the user’s device. Users can reset local demo data in Settings. For production accounts, the service should provide account export, deletion, retention, and support workflows before full public launch. Hosted backend logs, if enabled, should be retained only as long as needed for security, debugging, legal compliance, and service operation.

Security

Production deployment should use HTTPS, secure backend storage, encrypted database connections, least-privilege service credentials, rate limiting, access control, audit logging, and secret management. Users should not enter passwords, OTP codes, full card numbers, CVV codes, bank login details, government IDs, or highly sensitive documents unless a future production feature explicitly supports secure handling of that data.

Children

ZiplyFriend is intended for general personal productivity use and is not directed to children. If a parent or guardian believes a child provided personal information, they should contact support so the information can be reviewed and removed where applicable.

International users

Users may access the app from different countries. Data may be processed where the backend, hosting provider, AI provider, or support tools operate. Users are responsible for using the app in a way that complies with local laws and workplace or family privacy rules.

Contact

Privacy questions, access requests, deletion requests, and support requests can be sent to the support email configured for the App Store and Google Play listing. Before launch, replace this placeholder with your final public support email.

This page is a practical draft for product launch preparation and should be reviewed by a qualified legal professional before public release.

Back to home