1. Account information
Rema stores your email address, account identifier, account creation time, and records of your consent. The current sign-in implementation derives an identifier from your email and password on your device for an identifier-based backend. It does not provide standard server-side password storage, password recovery, or password changes. Your raw password is not stored in project records.
2. Profiles and projects
Your nickname, avatar, bio, optional location, published projects, photos, steps, and tags are stored to provide your profile and maker archive. Public profiles and works can be viewed by other signed-in users. Saves, applause, and related project activity may also be public. You provide optional profile information.
3. Challenge guesses
Rema stores your selected guess, any text you add, your sharing choice, and the challenge identifier. Unshared guesses use private records. Text you choose to share may become public after the challenge reveal.
4. Messages and calls
Text messages, photos you select, voice clips, read markers, and call signaling and status are stored to support conversations and one-to-one calls. Call audio and video are not recorded by the app, though call signaling is stored. Calls depend on network connectivity.
Access limitation: in the current implementation, message records use the backend's general public record scope with recipient filtering in the client. The backend does not restrict those records to conversation participants. Do not use the current development service to exchange confidential information.
5. Reports, blocks, and hidden conversations
Reports, your block list, conversation-hiding choices, and consent records use private records. Blocking filters what you see; it does not erase another person's public content. Hiding or clearing a conversation does not delete the original message records or change the other person's history. The app does not provide automated moderation or promise a response time.
6. Purchases and wallet records
Apple's App Store processes in-app payments. StoreKit verifies transactions on the device; the current app does not use a server receipt-verification service. Account records store product and transaction identifiers, purchase times, an account-binding identifier, revocation status, wallet balance, top-up and gift history, theme unlocks, and retry information for delivery and deduplication. Gift sender, project, and tier information may be public. The project does not store or upload signed transaction receipts and does not collect payment card details.
7. Device permissions and preferences
The app requests camera and microphone access for features you choose. The system photo picker provides access to media you select. Language and reminder preferences are stored by the app. The current version does not include a background push notification service. You can review system permissions in your device settings.
8. Retention and account closure
Closing an account in the app disables future sign-in through this client and clears the local session. It does not physically erase existing server records or uploaded files, and it does not revoke already issued backend tokens. Contact the address below to request access, correction, or erasure. The current account-closure action cannot complete server-side erasure.
9. Sharing and choices
Rema uses its storage and platform providers to operate the documented app features. The current project does not use advertising trackers or sell project user data. You can edit your profile, delete your works, hide messages, and change preferences in the app. Public material may already have been viewed or saved by others.
10. Adults and contact
Rema is intended for adults aged 18 and over. Do not upload personal information about children. For privacy questions or child-safety concerns, email EgansTraughber8985@outlook.com. This policy applies to the current development version and may change as the service implementation changes.