What the current build does
OverServed lets you select a contact or phone number locally so Android's call-redirection role can recognize a selected outgoing call during an active session. The selection remains on the device and is not uploaded to OverServed.
The Android app does not change the entries owned by your Contacts app or account provider. Removing the app clears OverServed's local selections and session data; it is not a contact-recovery method.
If contacts appear to be missing
-
Confirm which OverServed build you used
The current Android release cannot remove or restore contact rows. Record the app version, phone model, and Android version before changing anything. If you used an earlier prototype that experimented with contact mutation, say so when contacting support.
-
Preserve an older prototype until you have guidance
If an older prototype may have changed contacts, do not uninstall it, clear its app data, or factory-reset the phone while seeking help. Those actions can remove app-private data that might be useful for diagnosis.
Reinstalling the app is not a supported recovery path. Android normally removes an app's private data on uninstall, so do not assume a reinstall can recover anything. -
Check the contact account that owns the records
Contacts can be shown or hidden by account, sync state, filters, and the contact provider itself. Use the recovery and sync tools supplied by the account that owns the records, or contact that provider's support. Menu names vary by phone and provider, so this page does not invent a universal path.
Before using a provider-wide rollback, understand that it may reverse unrelated contact edits. Follow the provider's own current instructions. -
Contact OverServed support without sending contact data
Email support@overserved.app with the app version, phone model, Android version, approximate time of the issue, whether you used the current Android release or an older prototype, and which contact account or provider owns the records.
Support
Include diagnostic context only:
- Phone model and Android version.
- The OverServed version shown by Android's app information screen.
- Whether this was the current Android release or an earlier prototype.
- Approximate time of the issue and whether the phone or app restarted.
- The contact provider or account type, without account credentials.
Do not send names, phone numbers, contact exports, passwords, or screenshots containing them. OverServed has no server-side contact backup.
If you need to reach someone right now
Do not rely on OverServed for urgent communication. Use your phone's system emergency interface, the system dialer, another device, or local emergency services as appropriate. If call redirection behaves unexpectedly, disarm the session and revoke OverServed's call-redirection role using Android's system controls.
Do not factory-reset a phone as a first recovery step.
A reset removes local app data and can complicate diagnosis. Follow the contact provider's recovery guidance or obtain qualified device support first.
The contact-data boundary
The current Android app uses contact selection locally for protected-call matching. It does not upload the address book, and no OverServed server holds a contact backup. The public homepage links directly to Google Play and has no email signup form. Legacy waitlist records and support messages are separate from the app; the privacy policy below explains their retention and your access and deletion controls.
The full detail is in the privacy policy.