Privacy Policy

Last updated 13 October 2026

This policy explains what information FeeOne processes, why it is used, which service providers may process it, and the choices available to you. It applies to the FeeOne Android app and this website.

FeeOne is operated by Abhoy Pramanick as a sole proprietorship in West Bengal, India. In this policy, "FeeOne", "we" and "us" refer to that business.

1. Account and profile information

Depending on how you sign in and configure the app, FeeOne may process:

• Your email address, account identifier and authentication status.
• Your display name and profile photo where you provide them or receive them through supported Google sign-in.
• Your teacher or academy name, app preferences, language, plan and subscription entitlement.

2. Teacher-created records

FeeOne stores records you create for tuition administration, which can include:

• Student names and phone numbers.
• Batch names, subjects, schedules and routine information.
• Fee records such as amount, fee month, payment date, payment method, UTR where entered and receipt number.
• Attendance records such as date, batch and Present, Absent, Late or Excused status.
• Reminder, promise-to-pay, report and export related information where those features are used.

3. Contact import

If you choose Import from contacts, FeeOne requests contact permission so you can select students from your device address book. The full contact list is not uploaded to FeeOne. Only the names and phone numbers you explicitly select are saved as student records.

FeeOne does not intentionally upload unselected contacts or modify your device contacts.

4. Community information

If you use Community, FeeOne processes the messages and replies you post, your display name and profile photo where available, timestamps, regional Community context and moderation or reporting information needed to operate and protect the feature.

Community content is user-generated and can be visible to other users in the relevant Community area. Do not post confidential student records, financial credentials, identity documents, medical information or other sensitive personal information.

5. Notifications and Notification Center

If notifications are enabled, FeeOne may obtain and store an Expo push token together with device installation information such as an installation identifier, platform, project identifier, time zone and app version. This allows FeeOne to deliver teacher-facing reminders and product notifications.

Notifications can include fee, attendance, routine, account and product messages. FeeOne may also store Notification Center entries, delivery-related information and whether an item has been read.

You can deny or revoke notification permission through your device settings. Some notification-related records may remain long enough to keep delivery state, security and subscription logic consistent.

6. WhatsApp reminders and messaging

Individual WhatsApp reminders can be prepared for you to review and send. Where automatic WhatsApp reminders are offered and explicitly enabled, FeeOne may process the destination phone number, approved template, message metadata and delivery status through Meta or WhatsApp infrastructure.

We do not use student phone numbers for our own advertising.

7. AI tools

If you use FeeOne AI, the subject, topic, instructions, requested settings and related test or worksheet content are processed to generate the requested material. Usage counters and generation metadata may also be stored to apply plan allowances and prevent abuse.

Do not include student names, phone numbers or other unnecessary personal information in an AI prompt.

8. Billing and subscription information

Google Play processes paid subscriptions. FeeOne may receive and store purchase status, entitlement information, product identifiers and purchase references needed to activate, verify and support your plan.

FeeOne does not receive your card number, UPI PIN, CVV or bank password.

9. Diagnostics and security information

FeeOne uses privacy-filtered crash reporting to diagnose technical failures. Diagnostic data can include the app version, device model, operating system version, crash details and limited technical tags.

Crash reporting is designed to remove account identity, student records, contact data, payment references, authentication tokens and breadcrumbs before events are sent.

FeeOne uses Firebase Analytics to count broad app areas and fixed feature-success categories, such as Home, Batches, attendance saved or payment recorded. Analytics does not receive raw route values, account or student identifiers, student names, phone numbers, fee amounts, notes or record contents. Automatic native screen reporting, advertising storage, ad personalization and advertising-ID collection are disabled. Privacy-minimal usage analytics are a required part of operating and improving FeeOne.

10. Why we process information

We process information to:

• Authenticate users and operate accounts.
• Store, sync, restore and display your records.
• Generate receipts, reports, exports and AI material you request.
• Deliver notifications, routine reminders and messaging features you enable.
• Apply plan limits, subscription entitlements and AI allowances.
• Operate Community, moderate abuse and protect users.
• Prevent fraud, diagnose failures and improve reliability and security.
• Respond to support, deletion and legal requests.

11. Service providers

FeeOne uses a limited set of service providers. Depending on the feature you use, these can include:

• Supabase: authentication, database, storage, server functions and account-scoped application data.
• Google: Google sign-in where used, Google Play billing, Gemini processing for AI generation, and Firebase Analytics for aggregate feature usage.
• Expo and platform notification services: app build/update infrastructure and push notification delivery.
• Meta / WhatsApp: automatic WhatsApp messaging where configured and enabled.
• Sentry: privacy-filtered crash diagnostics.
• Resend: account or service emails where that email workflow is used.

Each provider is used only for the function it supports. We do not sell your personal information to advertisers and FeeOne does not use behavioural advertising trackers.

12. Student data and your responsibility

Please enter only what is reasonably needed for tuition administration.

13. Security

FeeOne uses account-scoped access controls, encrypted network connections and database-level security controls. No internet service can guarantee absolute security, but we design access so one normal user cannot read another user's private teacher records.

14. Retention and account deletion

Core account and teacher-created records are generally kept while your account remains active. A paid plan ending does not by itself delete your existing register.

You can request account deletion from inside FeeOne. If you cannot access the app, use our account deletion page. Verified support requests are processed according to the deletion process described there.

Some information may remain for a limited period in backups, security logs, abuse-prevention records, billing references or records that must be retained for legal or dispute purposes. We keep such information only as long as reasonably required for those purposes.

15. Your choices

Depending on the feature, you can:

• Change supported profile and app preferences.
• Control notification permission through your device.
• Remove eligible Community content you posted.
• Archive students and manage active roster limits.
• Export supported records and reports.
• Request account deletion.
• Contact us to ask about, correct or obtain a copy of information associated with your account where applicable.

16. Changes to this policy

We may update this Privacy Policy as FeeOne changes. The date at the top will be updated, and significant changes may also be communicated in the app or by email.

17. Contact

Privacy questions can be sent to support@nivya.in. Postal address and phone details are available on our Contact page.