GRmoto Command Centre

Privacy policy

Last updated: 12 November 2026

This notice describes GRmoto Command Centre, a private, self-hosted planning tool operated by Emanuel Parker for GRmoto director work and personal organisation. For questions, corrections or removal requests, contact emanuel@grmoto.co.uk.

Information the tool uses

The owner connects accounts he is authorised to use. Connected information can include correspondence about customers, suppliers, colleagues and personal contacts.

Purpose and separation

Information is used to organise the owner's day, identify decisions and business risks, retain commitments, check availability, and prepare follow-ups. Suggested priorities, ownership and completion need review against their sources.

Work and personal tasks and context are separated by domain and project. Busy intervals from the other domain can help avoid calendar conflicts; the other view does not receive those event labels or mailbox details through the planning overview.

The tool has no advertising, data-selling or model-training feature. Imported Google information is used for the planning features described here, rather than advertising or training general-purpose AI models.

Optional AI processing

AI execution requires configuration and owner approval. A job sends its instructions, acceptance criteria and selected, approved source text to the configured OpenAI or Anthropic API. An independent review sends the saved draft and approved evidence to the other configured provider.

Approval is tied to the source's domain, project, revision and content. Syncing new evidence does not automatically approve it for an AI job. The app retains job specifications, selected evidence, drafts, reviews, status and usage/cost records.

AI providers process submitted data under their applicable API terms and settings. The owner should review those arrangements before enabling a provider. This notice does not promise that a provider retains no data.

Optional WhatsApp reminders

When configured, paired and enabled, Meta's WhatsApp Business API receives the owner's verified phone number and reminder text, which can include task details. The tool stores send attempts, provider references, delivery information and received replies. Reminders target the paired owner; they do not automatically contact colleagues or customers.

Meta can grant the app access and deliver webhook events at the WhatsApp business-account level, which can include other numbers in the same account. The application checks the configured business account, dedicated sender and paired owner before using message events; it does not treat another number's messages as Command Centre replies.

Optional urgent phone calls

When configured, consented to and enabled, the tool can use Twilio to call the owner's verified number about a concise urgent project question. Twilio receives the sending and receiving numbers and a spoken prompt, which can include the project name, its significance and the question. The call first asks the recipient to press a key before hearing project details.

Call recording is disabled by the application. A recipient can answer with a keypad choice or short spoken update. Twilio returns speech-recognition text for a spoken update; the application retains that text, the response choice, question and project references, call events, provider status and budget/cost records. Responses are saved for review and do not automatically approve project action. Pressing 9 pauses phone calls.

Hosting and access

The application runs on owner-controlled hosting, with a sign-in requirement for the dashboard and private APIs. The owner and authorised hosting administrators can access retained server data and backups. Connection secrets saved in the app's database are encrypted; the owner also controls host-level settings and backup protection.

A necessary sign-in cookie maintains the private dashboard session. These public information pages contain no analytics, advertising or third-party scripts. Hosting and server systems may maintain operational or security logs.

Retention, disconnection and removal

Unresolved tasks are kept across syncs. A message or card disappearing from a recent search does not erase its imported record or prove that the work is complete. Source versions, audits, AI records, reminder history and phone-call response and event records remain until the owner removes them. This version has no automatic retention purge or one-click complete-erasure feature.

The owner can disconnect a connection in dashboard settings and revoke Google authorisation in Google Account connections. Disconnecting disables use of the connection in this app; it does not automatically remove previously imported records, environment-based settings or backup copies.

Complete removal requires owner-administered deletion of the relevant retained records and credentials, plus handling any separate backup copies. Copies already submitted to external providers are also subject to those providers' processes. Contact the operator to request a review, correction or removal; no automatic deletion schedule is asserted here.

Changes and contact

The owner updates this notice when the tool's data handling changes. The date above identifies this version. Contact emanuel@grmoto.co.uk about the tool or its data.