Privacy Policy

SaveMy75 ("we", "our", or "us") operates the SaveMy75 mobile applications (iOS and Android), the product web app at app.savemy75.com, and this marketing website at savemy75.com.

This Privacy Policy describes what information we collect, why we collect it, how we use and protect it, and the choices you have. By using SaveMy75, you agree to the practices described here. If you do not agree, please do not use the service.

SaveMy75 is an independent student attendance planning tool. We are not affiliated with, endorsed by, or connected to HITAM, WebProsIndia, or any educational institution. Your college portal remains the sole official source of academic records.

Depending on how you use SaveMy75, we may collect the following categories of data:

• Account profile information. When you sign in with Google, we receive your name, email address, and profile photo via Google / Firebase Authentication.
• User identifiers. A Firebase user ID and an internal SaveMy75 account ID used to secure your data and keep sessions consistent across devices.
• Institution ERP credentials. If you link your college portal, you provide your roll number (or username) and password so we can fetch attendance on your behalf. Credentials are encrypted at rest and are not returned to the client after linking.
• Academic and attendance data. Subject-wise attendance, day-by-day history, timetables, internal marks, branch/program details, and related academic metadata retrieved from your institution’s ERP when you authorize a sync.
• Profile photos. If photo sync is enabled for your environment, a profile image may be retrieved from your institution’s portal for display in the app.
• Device and diagnostics information. General device metadata (for example OS version and device model), crash logs, performance metrics, and app interaction events used for analytics and reliability.
• Support communications. If you email support, we receive the content of your message and any account details you include so we can help you.

We do not sell your personal information. We do not use your ERP password for advertising. We do not collect precise location for tracking purposes.

Account creation and sign-in are handled through Firebase Authentication with Google Sign-In (OAuth). We do not offer a traditional username-and-password registration system operated by SaveMy75.

• Google provides us with identity tokens that prove you control the Google account you used to sign in.
• Our backend verifies Firebase ID tokens on protected API requests. Tokens are short-lived and refreshed by the Firebase SDK.
• Guest Mode uses Firebase Anonymous Authentication so you can try core features without linking a Google account. Guest sessions are local-first; see Guest Mode below.
• Google’s own processing of your Google account is governed by Google’s Privacy Policy.

We process your information only as needed to operate and improve SaveMy75:

• Authenticate you and secure your account across sessions and devices.
• Log into your college portal on your behalf (with credentials you provide) to retrieve attendance and related academic data.
• Calculate attendance percentages, buffers, recovery plans, and planning insights shown in the app.
• Cache data securely so the app loads quickly and can work offline where supported.
• Diagnose crashes, measure reliability, and improve product quality using analytics and diagnostics.
• Respond to support requests and enforce our Terms of Service.
• Comply with applicable law and protect the security of our systems and users.

Academic data is the core of SaveMy75. When you link your ERP and sync:

• We retrieve attendance records and related academic information from your institution’s portal using the credentials you provided.
• That data is stored in our database so you can view history, trends, and planning tools without re-scraping every time.
• Displayed percentages and predictions are estimates for planning. Your institution’s official portal remains authoritative for exams, detention, and academic decisions.
• Unlinking your ERP or deleting your account removes stored credentials and associated academic records from our systems as described under Account Deletion.

With your permission, SaveMy75 may send push and in-app notifications about attendance updates, college messages, and product-related alerts.

• Notification delivery uses platform push services (for example Firebase Cloud Messaging on Android / APNs on iOS when configured) and device push tokens.
• You can disable notifications in your device system settings or in-app notification controls where available.
• Notification content may include message titles, short previews, and deep links into the app. It does not include your ERP password.

Some college messages and announcements may include rich media such as banner images, photos, PDFs, or external links.

• Media files may be stored in secure cloud object storage and delivered via short-lived signed URLs.
• When you open an attachment, the app may download the file to temporary on-device cache so it can be viewed offline or with the system viewer.
• Profile photos (when photo sync is enabled) may be retrieved from your institution’s portal for display in the app.
• Cached media can be cleared by normal app data cleanup, signing out, or uninstalling the app.

We use PostHog for product analytics and diagnostics. Analytics helps us understand feature usage, fix bugs, and improve the experience.

• Events may include screen views, button interactions, sync success/failure, crash traces, and coarse device metadata (OS, model).
• We design analytics to avoid sending ERP passwords, full academic record dumps, or other highly sensitive free-text credentials.
• Device identifiers or installation identifiers may be used by analytics SDKs to understand sessions and reliability. These are not used for third-party advertising.
• Analytics collection is optional for product improvement and is not required solely to view this Privacy Policy page.

The marketing website (savemy75.com) is primarily static content. It may use browser local storage to remember preferences such as light/dark theme. Essential cookies or similar technologies may be used by our hosting and security providers (for example Cloudflare) for delivery, performance, and abuse protection.

The mobile and product web apps store authentication tokens and local caches in secure on-device storage (for example Secure Store / platform secure storage) so you stay signed in and data loads offline. You can clear local app data by signing out, exiting Guest Mode, or uninstalling the app.

We use trusted service providers to operate SaveMy75. They process data only as needed to provide their services to us:

• Google / Firebase — authentication (Google Sign-In, anonymous guest auth) and related identity infrastructure.
• PostHog — product analytics and crash / interaction diagnostics.
• Cloudflare — DNS, CDN, security, and hosting for marketing and product web surfaces.
• Infrastructure hosting — our API and databases run on managed / self-hosted server infrastructure with access controls.
• Your institution’s ERP / portal — when you link an account, we access the portal solely to retrieve the academic data you requested. That portal is operated by your institution (or its vendor), not by us.

Third parties may have their own privacy policies governing their processing. We do not control policies of Google, Firebase, PostHog, Cloudflare, or educational institutions.

We implement technical and organizational measures designed to protect your data:

• Encryption in transit. API and website traffic use HTTPS/TLS.
• Encryption at rest for ERP credentials. Institutional passwords are encrypted (AES-256 class encryption) before storage and decrypted only when needed to perform a sync on your behalf.
• Access control. Application data is scoped to your authenticated account so other users cannot access your records through normal API flows.
• Local caching. Attendance and related data may be cached on your device for performance and offline use.
• No security system is perfect. We continuously improve controls, but we cannot guarantee absolute security of any system connected to the internet.

If you use SaveMy75 in Guest Mode:

• Your session is designed to be local-first on your device for credentials and cached guest data.
• We do not permanently attach a full Google-linked profile to guest-only usage the way we do for signed-in accounts.
• Exiting the guest session clears local secure storage and guest caches on the device.
• Limited anonymous authentication identifiers may still exist on Firebase for the guest session while it is active.

We do not sell, rent, or trade your personal information for advertising money.

We may share data only in these limited cases:

• Service providers who process data for us (authentication, analytics, hosting) under contractual or platform terms.
• Legal requirements if we are required to disclose information by law, regulation, legal process, or governmental request.
• Safety and rights to protect users, prevent fraud/abuse, or defend our legal rights.
• Business transfers if SaveMy75 is involved in a merger, acquisition, or asset sale, with notice where required.

• Account and academic data are retained while your account is active so the product can function.
• When you delete your account in-app, core account data, Google linkage, encrypted ERP credentials, and associated attendance/academic records are deleted from our primary systems promptly.
• Manual deletion requests emailed to support are processed within 48 hours after we verify the request.
• Limited operational logs (for example system audit logs or short-lived technical failure logs) may be retained for security, debugging, and reliability — typically on the order of days to about 30 days depending on log type — and then pruned.
• Analytics events retained by PostHog follow that provider’s retention configuration.

Depending on where you live, you may have rights to access, correct, delete, or restrict processing of your personal data, or to object to certain processing. You can exercise many of these rights directly in the product:

• View and manage your profile and linked ERP data in the app.
• Unlink ERP credentials to stop future syncs and remove linked portal credentials.
• Delete your account and associated primary data from Profile → Delete Account.
• Contact us at support@savemy75.com for access, correction, or deletion assistance.

If you believe we have not adequately addressed a privacy concern, you may also have the right to contact a data protection authority in your jurisdiction.

In-app (recommended):

• Open the SaveMy75 app.
• Go to Profile → Actions → Delete Account.
• Confirm deletion. This permanently removes your Google account association with SaveMy75, encrypted ERP credentials, and historical attendance/academic data from our primary servers.

Manual request: Email support@savemy75.com with subject line "Data Deletion Request" and include the Google email used for the account (and roll number if linked). We process verified requests within 48 hours.

Additional step-by-step instructions may also be available at app.savemy75.com/delete-account.

SaveMy75 is intended for college and higher-education students. We do not knowingly collect personal information from children under 13 (or the minimum age required in your region). If you believe a child has provided us personal data, contact support@savemy75.com and we will take appropriate steps to delete it.

SaveMy75 may be accessed from multiple countries. Our servers and service providers may process data in locations different from where you live. By using the service, you understand that your information may be transferred to and processed in those locations, subject to this Privacy Policy and applicable law.

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page. Material changes may also be communicated in the app or on the website. Continued use of SaveMy75 after an update means you accept the revised policy.

Questions about this Privacy Policy or our data practices:

• Email: support@savemy75.com
• Website: https://savemy75.com
• Related: Terms of Service