Privacy Policy
Community Program Management. Effective date: 2026-10-25.
The responsible developer is TARUN GERA. Contact: communityprograms.help@gmail.com.
Information and purposes
- Accounts and authentication: Administrator-provisioned email address, display name, role and account identifier let us sign you in and enforce access permissions. Passwords are transmitted over HTTPS to Supabase Auth for verification; Auth stores password hashes, not readable passwords. Access and refresh tokens authorize your session. The current app keeps its Supabase session in memory rather than persistent app storage.
- Scheduling: Teacher and center details, region, manually supplied coordinates, availability, requests, assignments, notes and workflow history support scheduling, recommendations and role-specific views. User-selected CSV imports send applied records to the backend. Initial scheduling records are fictional; real organizational onboarding is not yet open.
- Technical information: Hosting and authentication providers may process IP addresses, request timestamps, endpoint/status information, device/browser information and security logs to deliver the service, diagnose failures and prevent abuse.
- Support: If you email us, we process your address, message and any information you choose to include to investigate and respond. Do not send passwords, authentication tokens or sensitive personal documents.
Administrators access organizational schedules; teachers and center coordinators access information permitted by their roles. We do not sell personal information, use advertising or track you across other companies' apps or websites. This release has no app analytics or advertising SDK integration.
Providers and safeguards
We require service providers receiving personal data on our behalf to provide protection no less protective than this policy and applicable App Store privacy requirements, including appropriate security, limited access and assistance with deletion requests. We review their published commitments and applicable terms, limit the information sent, and will stop or change a data flow if we cannot maintain these protections.
- Supabase hosts authentication, the database and backend functions. Its security commitments describe encryption in transit and at rest. Authentication and row-level policies restrict app access. The current backend is hosted in the United States.
- Expo provides cloud build and distribution tooling; we do not send scheduling database records to Expo as part of app workflows. Automatic over-the-air updates are disabled for this release.
- Apple handles App Store/TestFlight distribution and related platform information under its own privacy policy and your device/account settings.
- GitHub Pages hosts these public pages and processes website request information to deliver and secure them. We do not publish account or scheduling records on this site.
- Google's Gmail service processes support email. Contacting support is optional; never email your password.
API traffic uses HTTPS, and backend administrative credentials are not included in the mobile app. Provider-controlled platform information is also governed by the linked providers' policies. No service can guarantee absolute security.
Files and device access
The system file picker accesses files you choose, not your whole library. Imported records are sent to the backend only when you apply them. The picker may create a local cache copy that remains until app/operating-system cleanup or app removal. The iOS release candidate attempts to remove its temporary export copy after the share sheet finishes, is cancelled or fails, and reports cleanup failures. Interrupted operations can leave cache copies until later cleanup or app removal.
Files you explicitly save or share outside the app remain under your control and the recipient's control; account deletion cannot recall those copies. Protect them and delete them when no longer needed. The app does not request device location, contacts or photo-library access.
Retention and deletion
- Live accounts: Account information is retained while the account is active. In My profile, confirm permanent deletion with your current password. When the server reports success, it has removed the Auth account/profile and cleaned linked teacher personal fields, personal attribution and related notification data. A failed or interrupted request is not confirmation of deletion.
- Organizational history: Shared schedules and internal references may remain to preserve organizational records, with linked teacher names and personal fields removed. We do not claim every retained reference or arbitrary free-text entry is irreversibly anonymous. Contact support if retained content still identifies you; verified requests include review of that content.
- Manual database dumps: Our operator procedure removes them within 30 days of creation unless a documented recovery need or legal obligation requires longer. They are restricted from routine use. A restore must reapply completed deletions before service resumes.
- Support correspondence: Our operator procedure removes it within 90 days after resolution unless an ongoing dispute or legal obligation requires longer. A minimal restricted record of a completed deletion may be kept while a recoverable backup could otherwise restore the account.
- Provider records: Security/operational logs and provider-controlled recovery records follow each provider's applicable retention rules and legal obligations, which can differ from our live database deletion. We do not promise immediate erasure of those records. Contact us to identify the relevant provider and request available assistance.
Your choices and requests
You can decline optional imports, exports or support contact. Essential authentication and scheduling processing is needed to use the account-based service. To stop participating, stop submitting information and use in-app account deletion, or contact support if you cannot sign in. Signing out or uninstalling alone does not delete server records.
For access, correction, deletion or withdrawal of consent where processing relies on consent, email communityprograms.help@gmail.com with the request and account email. We review the inbox at least weekly, verify control of the account or use a trusted administrator-assisted process, clarify the scope, and explain the action taken or any necessary retention. We never ask for your password. We respond within applicable legal deadlines; weekly review is not a guaranteed resolution time. If identity cannot be safely verified, we explain the limitation rather than disclose or delete another person's information.
The app is intended for adult organizational users and is not directed to children.
Changes
We update this page when practices change, including before real organizational onboarding. The release candidate's changes reach installed devices only through a new approved build; older TestFlight builds may not contain them.