1. Summary
Most features of 1Mile can be used without signing in. Google sign-in is used primarily to validate community transit contributions, route edits, user profiles, and account-linked actions. The app requests foreground device location permission only when you explicitly search for nearby transit configurations. The app does not track buses in real time and does not track or log user location in the background.
We do not sell personal or sensitive user data.
2. Data We Collect Or Access
Account And Sign-In Data
When you sign in using Google, we receive and store account identifiers such as your unique user ID and email address. This is used to attribute bus data contributions, manage modification histories, prevent spam or abuse, and handle profile configurations.
Transit Contribution Data
When you add or edit bus transit structures, we collect and store:
- Contributor user ID and account-linked metadata.
- Contributor profile name, email, and display avatar when provided by the account system.
- Bus names, registration numbers, route paths, direction variables, stop names, stop ordering, schedules, linear coordinates, and route geometric polylines.
- Algorithmically projected village, stop, and map-coordinate fields used to map paths on the base map.
- Contribution IDs, draft tokens, app version numbers, database version parameters, publish statuses, review notes, changed tracking values, and audit logs.
- AI extraction session parameters and draft data generated during document analysis.
A subset of this data becomes visible to other users within the public application tracking framework, including map interfaces, search entries, reference elements, and editor history timelines.
Background Weather Sync
The app uses a background service (WorkManager) to refresh weather data for the Purulia region approximately every 24 hours. This service runs when the device has network connectivity and does not access your personal location or any personal data. It only fetches and caches regional weather forecast data.
Location Data
When utilizing location-based lookup features, the application requests explicit foreground fine or coarse device location permission. This coordinates localized tasks to set map discovery points and fetch nearby transit corridors or station points.
1Mile completely omits background tracking permissions and does not use device tracking to track active transit vehicles.
Map overlays interface with the Google Maps platform. The station nodes, village coordinates, lines, and directional paths rendered are built using community inputs and predictive projections, which may not always align with native ground positions or verified geographic markers. For structural errors or misplaced coordinates, please contact our support desk immediately to initiate data modifications.
Weather, Calendar, And Local Data
Environmental data and seasonal metrics render using localized app caches and pre-configured regional indices. Weather functionality serves the Purulia zone and operations execute without accessing individual personal location streams. The application stores temporary performance files locally to preserve quick load times and support offline lookup states.
Local Medicine Interest
Hyperlocal pharmaceutical delivery features are currently paused. If an authenticated user chooses to register demand markers for prospective service options, the system logs your user token, verified email, name tag, telephony endpoint, and optional message strings.
Technical And Diagnostic Data
To secure system boundaries and resolve execution errors, the platform captures current app versions, database schema markers, API request pathways, server error logs, and performance statistics.
3. How We Use Data
Information assets are processed to fulfill specific operational parameters, including:
- Delivering integrated application experiences, encompassing map visibility, environmental monitoring, regional schedules, public healthcare indexes, account management, and history records.
- Validating account verification vectors.
- Attributing administrative edits and route enhancements.
- Mitigating the injection of redundant, malicious, falsified, or inaccurate database entries.
- Converting graphical transit documentation into structural data arrays via automated pipelines.
- Reviewing, authenticating, correcting, or archiving public route inputs.
- Calculating distance metrics relative to nearby stops upon explicit user request.
- Managing voluntary registrations for future operational options.
- Protecting infrastructure security, resolving software exceptions, and satisfying regulatory constraints.
4. Sharing And Service Providers
We leverage foundational infrastructure subprocessors to run the application components, restricted exclusively to the following service boundaries:
- Supabase Inc. — Hosts core data layers, relational databases, user authentication frameworks, profiles, and media storage spaces.
- Google LLC Services — Processes Google Sign-In authentications, base-map layout rendering, and foreground location APIs. Google is entirely independent from individual data paths, coordinate lines, or arrival estimations deployed by 1Mile contributors.
- 1Mile Weather API Node — Delivers localized environmental indicators for the Purulia region.
- Native Operating Handlers — Switches tasks to native device subsystems, such as firing up the phone dialer, upon explicit button selection.
Engaged service providers handle data strictly to maintain infrastructure security, service continuity, or feature deployments. We do not sell personal or sensitive user data.
Data resources may be disclosed to third parties only if instructed by binding legal warrants, regulatory processes, terms of use investigations, public safety enforcement, or legitimate corporate structural reorganizations with explicit user notifications.
5. Transit Data Visibility
Transit structures, schedules, timetables, and coordinate geometries added by users populate a shared lookup database intended for public reference. This includes bus metrics, estimated arrival blocks, directional lines, geometry lines, along with contributor profile names and system edit logs.
Do not submit any transit updates or text fields if you do not want them permanently integrated into the shared community transit map.
6. Data Retention
Data profiles remain active inside our systems only for the timeline required to fulfill functional lookup tasks, matching these parameters:
- Authentication credentials and session tokens persist alongside active user profiles.
- Profile identities remain stored until updated, anonymized, or removed by user request.
- Local cache configurations persist until overridden by fresh server assets or cleared manually via device settings.
- Transit contribution sequences are archived indefinitely to protect mapping historical health, resolve dataset duplication, track modifications, and handle security audits.
- Validated public transit facts remain active as long as they serve utility for community tracking paths.
7. Account Deletion
The application features a termination workflow directly within the user account settings. Initiating deletion anonymizes individual personal identities from system records and invalidates active session tokens. Validated transit route facts, map configurations, and database updates persist to preserve collective mapping data health, enforce tracking protections, and prevent spam history.
For data removal inquiries or verification queries, users can contact us at 1mile.support@gmail.com.
8. Security
We deploy standard procedural protections to insulate data operations, including mandatory HTTPS transmission protocols and excluding temporary storage files from regular Android cloud backup sequences. However, no digital transmission channel or storage network can provide absolute safety from external exploits.
9. Children
The platform is not built for or intentionally marketed to individuals under the age of legal majority. Minors using the service should do so only under the supervisor guidance of a parent or legal guardian.
10. Healthcare Disclaimer
Medical center and professional directory paths serve strictly as an informational reference index. 1Mile is not certified as a medical device and is entirely unsuited for clinical diagnostic tasks, pharmaceutical assignments, or emergency triage routing. It does not replace expert advice or formal hospital intervention. Practitioner parameters remain variable; users must verify points directly with physical provider desks.
11. Your Rights Under Indian Law
Under the Digital Personal Data Protection Act, 2023 (DPDP Act) and applicable Indian regulations, you have the following rights:
- Right of Access: You may request a copy of the personal data we hold about you.
- Right of Correction: You may request correction or updating of inaccurate personal data.
- Right of Erasure: You may request deletion of your personal data, subject to legal retention requirements.
- Right of Grievance Redressal: You may raise complaints regarding data processing and expect timely resolution.
- Right to Nominate: You may nominate another individual to exercise your rights in the event of your incapacity or death.
Users may also request account and data deletion via our web portal: https://rampadamatrix.github.io/1Mile_Legal-Usability/Account-Deletion-Request.html
To exercise any of these rights, contact us at 1mile.support@gmail.com. We will respond within the timeframes prescribed by applicable law.
12. Changes
We adjust this Privacy Policy dynamically as application elements expand or legal constraints evolve. Updates become binding immediately upon the revision of the timestamp documented at the top of this page.
13. Contact Information
For explicit complaints, data queries, or standard operational assistance concerning this statement, you can connect directly with our support lines:
- Email Support: 1mile.support@gmail.com
- WhatsApp Support Line: +91 8942890161