ELSEWHEN

EFFECTIVE AUGUST 8, 2026

Privacy Policy

This policy explains what Elsewhen handles, why it is needed, and the controls available to you.

1. Summary

Elsewhen is an Android application that turns a configured Inject selection into a narrated audio note, stores that note in Google Drive, and creates a linked Google Calendar event. Elsewhen does not sell personal information and does not include advertising trackers.

Google Drive files are private by default. Anyone-with-the-link sharing happens only when you choose that option for a routine.

2. Information Elsewhen handles

  • Your Google account identifier and email address when you sign in through Firebase Authentication.
  • The Inject identifier you enter and the current selection returned by that service.
  • Your ElevenLabs API key, voice and model choices, and text sent for audio generation.
  • Routine settings, generated transcripts, local audio files, transaction status, and identifiers for the Drive files and Calendar events Elsewhen creates.
  • Operational errors necessary to show you whether a connection or transaction succeeded. Elsewhen does not operate a separate analytics or advertising backend.

3. Google user data

Firebase Authentication

Elsewhen uses Google sign-in through Firebase Authentication to establish an app session. Firebase processes the Google identity token and returns an account identifier and email address.

Google Drive

Elsewhen requests the drive.file scope. This allows it to create an Elsewhen folder, upload generated audio, read metadata for those app-created files, optionally create an anyone-with-the-link permission when you explicitly select it, and delete an app-created file when you undo a transaction. The scope does not allow Elsewhen to browse unrelated Drive files.

Google Calendar

Elsewhen requests the calendar.events.owned scope so it can add private events directly to the main Google Calendar owned by the connected account. This permission applies to events on calendars you own. Elsewhen uses it only to create its own events and to delete a specific Elsewhen event when you explicitly request cleanup; the app does not list, read, or edit unrelated events. Event fields can include a title, description, location, date and time, and a link to the generated Drive file.

How Google user data is shared or disclosed

Elsewhen does not share, transfer, or disclose data received from Google APIs to ElevenLabs, Inject, advertisers, data brokers, or any other third party. Google and Firebase process the account, Drive, and Calendar data needed to complete the actions you request. Elsewhen has no developer-operated server that receives this Google user data.

Drive files and Calendar events are private by default. If you explicitly enable anyone-with-the-link sharing for a routine, Google Drive makes only that app-created file available to people who receive its link. Elsewhen may otherwise disclose Google user data only with your explicit consent or when legally required.

Limited use

Information received from Google APIs is used only to provide and improve the user-facing Elsewhen workflow described here. It is not transferred for advertising, sold, used to determine creditworthiness, or used to train generalized artificial-intelligence models. Elsewhen's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

4. Other service providers

ElevenLabs

Elsewhen sends the rendered note text, selected voice and model settings, and your ElevenLabs API credential directly to ElevenLabs to generate audio. ElevenLabs processes that information under its own terms and privacy policy.

Inject

Elsewhen sends the Inject identifier you configure to the Inject endpoint at gg0.us to retrieve the current selection. The returned value is processed on your device and used to build the note.

Google and Firebase

Google processes authentication, Drive, and Calendar requests under its applicable terms and privacy policy.

5. Storage, retention, and security

  • ElevenLabs credentials and Inject identifiers are encrypted on the device using Android Keystore-backed AES-GCM encryption.
  • Google access tokens are short-lived and are not persisted by Elsewhen.
  • Routine settings and transaction metadata remain in app-private device storage until you clear them, uninstall the app, or reset the app.
  • Generated audio remains locally until app data is cleared and remains in Drive until you delete it or use Elsewhen’s undo cleanup.
  • Calendar events remain in your calendar until you delete them or use Elsewhen’s undo cleanup.

No security method is perfect, but Elsewhen limits stored credentials and uses platform-provided encryption to reduce exposure.

6. Your choices and controls

  • Disconnect Google from Elsewhen to sign out and revoke the app’s Google authorization.
  • Revoke Elsewhen from the security settings of your Google Account.
  • Keep Drive sharing private, which is the default, or explicitly enable link sharing for a routine.
  • Clear stored credentials and local history from Elsewhen settings or Android app storage.
  • Delete Drive files and Calendar events directly in Google’s products.

7. Children

Elsewhen is not directed to children under 13, and we do not knowingly collect personal information from children.

8. Changes to this policy

This policy may be updated when Elsewhen’s features or service integrations change. The effective date at the top of this page will be updated when material changes are published.

9. Contact

For privacy questions, support, or deletion assistance, open an issue through the Elsewhen project repository.