Your account, your work and your choices in the mobile app.
This draft covers Merick, the ORM mobile application for team workspaces, projects and task management on iOS and Android. It describes the reviewed mobile application and backend code. Your organisation manages your workspace membership and permissions. This page does not describe every future ORM system.
When you accept an invitation, register or sign in, the app sends the information needed to identify and authenticate you, including your name, username, phone number, password, invitation details and verification codes. Your profile may also contain your email address, profile image, account identifier and workspace role. These details support account access, password recovery, profile updates and the permissions assigned to you. The backend also records changes to account details in activity logs. Verification-message logs may include your phone number and delivery results.
The app retrieves and sends information you use or contribute within your workspace: projects, tasks, task status, comments, attached images, daily standup responses, and whiteboard text, drawings, images and previews. It also displays work-related activity and progress statistics such as completed tasks and points. Content is processed to save your work, synchronise updates and support collaboration. Workspace members and administrators may access shared content according to their permissions; do not treat a shared task, comment or whiteboard as a private message.
You can choose a photo or take one to attach to a task comment, and choose images for a whiteboard. The selected content is uploaded when you submit the comment or save the board. Camera and photo access are requested through your device when needed. You can refuse or revoke permissions in device settings; the related feature may then be unavailable. The reviewed app does not request location, contacts or microphone access. It does not implement biometric sign-in in the reviewed version.
Merick uses Google Firebase Cloud Messaging to deliver notifications, with Apple push services involved on iOS. The app registers a messaging token, device platform and notification preference with the application server for your signed-in account. The server also records the request’s user-agent information and when the device registration was last updated. Firebase processes installation identifiers to route messages. Notification content may be shown on your lock screen according to your device settings. You can change notification preferences in the app and device settings. Turning alerts off does not, by itself, delete your account or erase service identifiers.
Account and work data are sent to the ORM application services. Notification delivery uses Firebase Cloud Messaging and, on iOS, Apple push services. Images are fetched from their configured hosts. The English typeface may be downloaded from Google Fonts when it is not already available on the device; that connection exposes normal network request information, such as an IP address, to the font host. The reviewed app does not include advertising, analytics or crash-reporting SDKs. The backend integrates OTPIQ for verification messages when configured, sharing the destination phone number and verification code. Delivery channels depend on the service configuration. Live comment updates use the configured real-time server. Deployment documentation identifies Hetzner hosting, but the active production provider, server location, delivery channels and any additional recipients still need confirmation before publication.
Firebase privacy information · Google Privacy Policy · Apple Privacy Policy
The app stores sign-in tokens and a copy of your account profile using the device secure-storage service so your session can resume. The appearance preference is saved locally, and displayed images may be cached on the device. Signing out clears the locally stored sign-in session; it is not an account-deletion request and does not remove shared work from the server. Device backups and caches are also subject to your operating-system settings.
You can update supported profile details, change your password, manage notification permissions and sign out. The current mobile version does not provide an account-deletion action. The reviewed backend includes password-confirmed account deletion through the web profile and a separate authorised administrator action. These actions do not establish complete erasure of uploaded files, activity logs, archived records or backups, and deleting an owner account can also affect shared projects and workspaces. Before publication, ORM must verify a user-accessible deletion process, how shared content is handled, and the removal or retention of remaining data, and provide a working privacy contact. Uninstalling the app does not delete server-held records. The placeholder contact below is not an operational request channel.
Account data, workspace content, uploaded files, logs and backups can have different retention requirements. The reviewed code has expiry limits for verification and sign-in tokens, but token expiry is not a promise to erase account data. No general scheduled cleanup for account content, uploaded files and backups was identified in the application scheduler. Retention periods, complete deletion procedures and any exceptions still require confirmation; this draft does not promise a deletion deadline. The app uses authenticated sessions and device secure storage, but production transport security, server access controls and backup handling must be verified separately. No claim of end-to-end encryption is made here.
Responsible entity: ORM. Application: Merick. Temporary privacy contact: privacy@example.com — placeholder only; do not send personal information to this address. The official contact and retention terms must replace the pending details before this page is used as the app’s published privacy policy. This draft was reviewed on 4 November 2026. It should be updated whenever the app’s data use, permissions or service providers change.