Effective Date: January 1, 2026 · Last Updated: April 2026
This policy explains how aTownRides communicates with you — what kinds of messages we send, how we send them, and how you can manage your communication preferences.
This Communication Policy describes how aTownRides communicates with its users — including riders, drivers, and applicants — across all channels including push notifications, email, and in-app messaging.
We are committed to communicating clearly, respectfully, and only when necessary. We do not engage in spam or unsolicited marketing without your consent.
These are messages directly related to your use of the platform and cannot be opted out of while you maintain an active account. They include: account verification emails and OTPs, ride request status updates (matched, accepted, cancelled), order updates and confirmations, driver application status notifications (pending, approved, rejected), and payment link communications for driver registration.
aTownRides uses Firebase Cloud Messaging (FCM) to deliver real-time push notifications to your device. Notification types include: new ride requests (for online drivers), ride match notifications (for riders), order status changes, and administrative messages. You may manage push notification permissions through your device's OS settings. Disabling notifications may affect your ability to receive timely ride updates.
Certain alerts and status messages are delivered directly within the app interface. These include real-time status chip updates, error messages, and success confirmations.
We send emails for: account creation and email verification, password reset, driver application updates, and payment-related correspondence. We do not send unsolicited promotional emails without your explicit consent.
On first use, the app may request permission to send push notifications. Granting permission enables real-time ride alerts and status updates, which are essential for a smooth ride experience.
You may revoke push notification permissions at any time through your device settings (iOS: Settings → Notifications → aTownRides; Android: Settings → Apps → aTownRides → Notifications). Note that revoking permissions means you will no longer receive ride alerts on your device.
Device tokens (FCM tokens) used for notifications are stored securely in our database. When you sign out of the app, your device token is removed to prevent unwanted notifications. Multiple devices can be registered simultaneously.
During the driver application process, you will receive status notifications as your application progresses through review stages: pending, payment sent, paid, approved, or rejected.
If a driver registration fee applies, you will receive a payment link via email or in-app notification from an administrator. This link is secure and specific to your application.
Once approved and online, drivers receive push notifications when new ride requests become available. These are real-time alerts and require push notifications to be enabled.
aTownRides facilitates connections but does not currently provide an in-platform messaging feature between riders and drivers. Contact information may be shared (such as phone numbers) once a ride is matched to allow coordination.
All users — riders and drivers alike — are expected to communicate respectfully when using any contact information provided through the platform. Harassment, threats, or abuse communicated through any channel violates our Terms of Service.
Administrative users may send system-wide or targeted communications through the admin platform for important service updates, policy changes, or safety alerts.
Certain deployments of aTownRides may restrict account creation to specific email domains (e.g., university .edu addresses, or custom domains). This is a deliberate trust-and-safety feature to keep communities verified and safe.
All accounts require email verification. A one-time passcode (OTP) is sent to your registered email address to confirm ownership before full access is granted.
We do not sell your email address, phone number, or device tokens to third parties for marketing purposes.
We use Firebase (Google) for email authentication, push notifications, and messaging infrastructure. These services are governed by Google's privacy and security standards.
We may update this Communication Policy as our platform evolves. Material changes will be communicated to users via in-app notification or email. Continued use of the Service after changes are posted constitutes acceptance.
If you have questions about our communication practices or wish to update your communication preferences, please contact us through the aTownRides app.