1. Summary
Elsewhen is an Android application that turns a Quick Pick or configured Inject selection into a narrated or written note and creates a related Google Calendar event. Narrated notes are stored in Google Drive. Elsewhen does not sell personal information and does not include advertising trackers.
Google Drive files created by Elsewhen remain private in the connected account.
2. Information Elsewhen handles
- Your Google account identifier, email address, and any basic display name included by Google when you sign in through Firebase Authentication.
- Authentication-related device, app, and network metadata processed by Google and Firebase, such as IP address, operating-system and device model, Firebase app identifier, and authentication SDK version. This is used to provide sign-in, maintain the service, and prevent abuse—not for Elsewhen advertising or analytics.
- Your Google Play purchase status and purchase token when you buy or restore the optional professional integration. The token is used to verify the purchase and is not retained by Elsewhen after verification.
- The Inject identifier you enter and the current selection returned by that service, if you unlock and use the optional integration.
- Your ElevenLabs API key, voice and model choices, and text sent for audio generation.
- Routine settings, Quick Pick or Inject choices, generated transcripts, generated voice recordings, transaction status, and identifiers for the Drive files and Calendar events Elsewhen creates.
- If you enable Performance backup, the names and account labels of visible writable calendars configured on the phone so Elsewhen can select a suitable backup destination.
- Operational errors necessary to show you whether a connection, purchase verification, or transaction succeeded. Elsewhen does not operate an 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 stores the account identifier, email address, and basic Google profile fields supplied by the sign-in response. Elsewhen retains the Firebase user ID and email label needed to manage the account. If you unlock a paid add-on, the Firebase account also receives an entitlement flag so the purchase can be restored on another Android device.
Firebase Authentication also processes IP address, user-agent and device/app metadata, and the Firebase Android app identifier to provide and secure authentication, prevent abuse, maintain compatibility, and improve the Firebase service. Elsewhen does not use that metadata for its own analytics, profiling, or advertising.
Google Drive
Elsewhen requests the drive.file scope only when the selected routine uses a recorded note. This allows it to create an Elsewhen folder, upload generated audio, read metadata for those app-created files, check an app-private transaction marker so a retry does not upload a duplicate, and delete app-created test files when you explicitly run test cleanup. 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, check an app-private transaction marker so a retry does not create a duplicate, and delete a specific Elsewhen test event when you explicitly run test 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.
Optional phone Calendar backup
If you explicitly enable Performance backup, Android asks for Calendar read and write permission. Elsewhen reads the list of visible writable calendars configured on the phone—the calendar ID, display name, account label and type, primary status, and sync status—so it can prefer the connected Google account when available. It does not read the titles, descriptions, attendees, or contents of existing events. Only after the normal cloud delivery fails following a captured choice, Elsewhen can insert one private written backup event through Android's Calendar provider. The phone's calendar service may then sync that event to its account provider.
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. This includes data received from Google Drive and Google Calendar APIs. Google and Firebase process the account, Drive, and Calendar data needed to complete the actions you request. Elsewhen's purchase-verification function receives your authenticated Firebase user ID and Google Play purchase token, but it does not receive your Google Drive files, Calendar events, Google password, or Google access token.
Drive files and Calendar events created by Elsewhen remain private in the connected Google account. 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 and Firebase process authentication, Google Play Billing, server-side purchase verification, Drive, and Calendar requests under their applicable terms and privacy policies. They act as service providers for the account, purchase, and Google features you request.
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.
- The Firebase account stores whether the professional integration is active, its entitlement source, product identifier, and grant date. The Google Play purchase token is checked by the verification function but is not stored in Firebase custom claims or app analytics.
- Routine settings and transaction metadata remain in app-private device storage until you clear them, uninstall the app, or reset the app.
- If you choose Save setup backup, Elsewhen writes routines, Quick Pick packs, history receipts, and the backdrop to the file location you select. The backup excludes Google sessions, ElevenLabs keys, and Inject identifiers. Because it can contain performance content and account labels, you should keep it private.
- Generated audio remains locally until you delete the local copy or clear app data, and remains in Drive until you delete it. A clearly marked connection-test file can also be removed with Elsewhen's test cleanup.
- Calendar events remain in your calendar until you delete them. A clearly marked connection-test event can also be removed with Elsewhen's test 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 Calendar and Drive without signing out of your Elsewhen account, or sign out of Elsewhen separately.
- Use Restore purchases to ask Google Play to recheck an eligible add-on purchase without charging you again.
- Delete your Elsewhen Firebase Authentication account and erase app-local data from Settings → Privacy. See the account deletion instructions.
- Revoke Elsewhen from the security settings of your Google Account.
- Leave Performance backup disabled, or revoke Elsewhen's Calendar permission in Android settings, without affecting the normal Google OAuth Calendar route.
- Elsewhen-created Drive recordings remain private in the connected Google account.
- 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 deletion instructions, see Delete your Elsewhen account. For other privacy questions or support, email joestraightmagic@gmail.com.