Effective date: This policy takes effect on the date it is published.
Publisher / data controller: AJJ HAUS, individual app developer in Thailand
Privacy contact: support.memtempo@gmail.com
This policy describes the current MemTempo app behavior visible in its source code. It is not a statement about features or services that have not been enabled in the released build. "MemTempo," "we," and "our" refer to AJJ HAUS, the individual app developer in Thailand.
1. Information and purposes
| Information | Where it is handled | Why |
|---|---|---|
| Google account sign-in information, including the Google account identifier and the name, email address, and profile photo made available by Google | Google Sign-In and Firebase Authentication; the app uses the Firebase user ID to associate the user account with local study data | Sign in, maintain the MemTempo account, associate the correct on-device study data, reauthenticate before account deletion, and show account details |
| Study materials and files created or imported by the user, including PDFs, images, folders, notes, annotations, Seeds, review marks/history, and related metadata/settings | Primarily in the app's private on-device storage and SQLite database; a copy is sent to the user's Google Drive app data area only when the user starts a backup | Provide study organization, review, and backup/restore features |
| Reminder times and schedules | On the device, through local notification scheduling | Schedule reminders requested by the user |
| Google Play purchase details used to recognize Remove Ads, including the signed purchase record cached by the app | Google Play Billing and a signed receipt cache in app preferences on the device | Check whether the user owns the Remove Ads product and maintain that entitlement in the app |
| Network and device information processed by service SDKs | Google/Firebase services and, when an ad is requested, Google Mobile Ads | Authentication, service delivery, security/abuse prevention, and ad delivery or measurement as described by those providers |
| A message the user chooses to submit through Contact Us, and any attachments the user adds in their email app | The user's email application, the email provider selected by the user, and the MemTempo support mailbox | Respond to a report or feature request |
MemTempo does not operate a general-purpose server for user study files and notes. The app's source does not integrate Firebase Analytics, Crashlytics, Firestore, or a MemTempo-operated advertising/analytics backend. This statement must be checked again if the release configuration or SDKs change.
2. On-device storage and retention
Study files and notes, profile, preferences, imported copies of files, reminder configuration, and purchase receipt cache are stored in private app storage on the device. They remain there until the user deletes the relevant content/account or removes the app, subject to the platform's storage behavior. Android app backup is disabled in the current manifest. Files selected from another app or storage location are copied for MemTempo's use; deleting the MemTempo copy does not delete the original source file.
The app stores the signed Google Play purchase record locally to check Remove Ads. Deleting a MemTempo account clears that local receipt cache. It does not cancel, refund, or revoke the Google Play purchase. The user manages the purchase through Google Play.
3. Sign-in and Firebase Authentication
The app lets the user sign in with Google and uses Firebase Authentication to create and manage the corresponding authentication account. Google and Firebase receive the information needed to authenticate the user and operate their services. Firebase may also process technical information such as IP address, user agent, and service/security logs under Google's own terms and retention practices.
MemTempo does not receive or store the user's Google password. Google sign-in tokens are used by the sign-in flow and are not used to access the user's general Google Drive files.
Provider information: Firebase privacy and security and Google Privacy Policy.
4. Google Drive backup and restore
Backup and restore are user-initiated. To provide them, MemTempo requests the restricted drive.appdata scope and stores backup archives in the app-private appDataFolder of the Google account connected to the signed-in MemTempo account. A backup can contain a database snapshot, study metadata, notes/review data, and imported PDFs/images. The app does not request access to the user's general Drive files for this feature.
The user controls whether to create a backup and can manage app data through Google account settings. After a completed backup is uploaded and verified, MemTempo keeps the two newest completed backups and attempts to delete older ones. If cleanup fails, extra backup copies may remain. Google stores and processes Drive data under Google's policies and may process it in locations outside the user's country. Restore requires access to the matching account and a valid MemTempo backup.
Provider information: Drive app data folder and Drive API authorization scopes.
5. Advertising and Remove Ads
The app integrates Google Mobile Ads for interstitial advertising associated with successful imports. The current Android configuration uses Google's sample test app and ad unit identifiers; it does not use production ad identifiers. Test ads are for testing and do not represent the final production advertising setup. If production identifiers or different ad or consent settings are introduced, this policy and the applicable store disclosures must be reviewed and updated to match.
When the Google Mobile Ads SDK is active, it may automatically collect or share information such as IP address, app interactions, diagnostics, and device or account identifiers for advertising, analytics, fraud prevention, and related purposes, including while using test ads. Google's handling is described in its policies. Remove Ads is a one-time Google Play product; when recognized, the app suppresses its ads. The purchase receipt cache is separate from the purchase entitlement held by Google Play.
Provider information: Google Mobile Ads data disclosure and Google Ads privacy.
6. Google Play Billing
The app uses Google Play Billing to display, purchase, and query the Remove Ads product. Google Play processes the transaction and retains purchase records according to Google Play's policies. MemTempo does not operate its own purchase-processing server. A signed purchase record may be cached locally for entitlement checks. Removing that cache during account deletion does not alter the Google Play transaction or entitlement.
Provider information: Google Play Terms of Service.
7. Reminders, permissions, fonts, and support
Reminders are scheduled locally by the operating system. The app may request notification permission and exact-alarm capability where the platform requires it. Reminder schedules are not sent to a MemTempo notification server. Account deletion cancels the app's scheduled and displayed local notifications.
Most included fonts are bundled with the app. Some optional fonts are obtained through Google Fonts when selected; in that case, the request may disclose network/device information such as an IP address to Google. Google's policies apply to that request.
Contact Us opens a draft in the user's email application addressed to support.memtempo@gmail.com. The user chooses whether to send it and which attachments or other information to include. The selected email provider processes the message. Support emails are kept in the support mailbox until manually deleted.
8. Account deletion and retention after deletion
The user can start account deletion in the app. The app requires recent Google reauthentication and checks that the Firebase account being deleted is still the active account. The deletion process removes the matching Firebase Authentication user, that account's scoped local database and imported copies, related settings/profile and study data, local notifications, local purchase receipt cache, and MemTempo Drive backups that can be verified as belonging to that account.
The user may also request account and cloud-data deletion by emailing support.memtempo@gmail.com from the website. Support will verify account ownership before processing the request. Sending an email submits a request; it does not delete the account automatically. Deletion is not complete until the request has actually been processed. The website cannot remotely delete the app's SQLite database or files stored on the user's device. Users who can still open the app should use MemTempo → Settings → Delete Account to run the app's existing account and local-data deletion process. If the app cannot be opened, Android's Settings → Apps → MemTempo → Storage → Clear storage removes local app data from that device; this does not by itself delete the Firebase account or Drive backups. Clearing storage permanently removes local data, so users should check any backup they want to keep first.
\nEach signed-in account has a separate local database and file folder identified by that account's Firebase UID. Account deletion removes the database and folder for the account being deleted and leaves other accounts' separate databases and folders in place. It does not delete files outside MemTempo's app storage or unrelated Google Drive files. Drive deletion is limited to verified MemTempo backups in the connected account's app data area.
A temporary deletion journal may be retained on the device only while deletion is incomplete, to support safe recovery and retry. It is removed after the deletion flow completes. The app must not report successful deletion while a required step has failed. If Drive access, ownership verification, or another required step fails, the request remains incomplete and the app presents a recovery/retry path; the user may need to restore network access or reconnect the matching Google account.
Deleting the Firebase Authentication user sends a deletion request to Firebase. Firebase states that authentication information other than logged IP addresses is removed from live and backup systems within 180 days after the Firebase customer initiates deletion of the associated user. Firebase separately states that Firebase Authentication keeps logged IP addresses for a few weeks. These are Firebase-specific retention periods and do not mean that all Firebase data is retained for 180 days. Other records retained by Google under its own policies or legal obligations, Google Play purchase records, and email already sent are outside MemTempo's deletion control.
Provider information: Firebase data deletion and retention.
9. Sharing and international processing
MemTempo shares information only as needed for the services described above: Google/Firebase for sign-in and authentication; Google Drive for an explicitly requested backup or restore; Google Mobile Ads when an ad is requested; Google Play for billing; Google Fonts for optional font downloads; and the user-selected email provider for messages the user sends. These providers may process information in countries other than the user's country, under their own terms and safeguards. MemTempo does not sell the user's study content.
10. Security and user choices
MemTempo uses Firebase account identity to scope account data, requests limited Drive app-data access for backups, verifies Drive backup ownership before deletion, disables Android app backup in the current manifest, and uses the platform's private app storage. No storage or transmission method can be guaranteed completely secure.
Google sign-in is required to use MemTempo's core account and study features; the current app does not provide a guest mode. Users can choose whether to import materials, create a Drive backup, enable reminders, select optional online fonts, submit support email, or purchase Remove Ads. Users can request account deletion in the app. They can also manage Google account permissions, Drive data, advertising settings, and Play purchases through Google's controls.
11. Children and age restrictions
MemTempo is not designed or targeted specifically to children under 13. The app currently does not set a minimum age.
12. Changes and contact
We may update this policy when the app's behavior or service providers change. The current version and effective date are shown on this Privacy Policy page. For privacy questions or deletion assistance, contact support.memtempo@gmail.com.