Privacy Policy
Last updated: November 10, 2026
REM:Code is operated by Alexander Suslov, the data controller, in Spain. Public contact address: C/ Almirante Cadarso 26, Bajo, 46005 Valencia, Spain. For privacy questions or requests, email hello@remcode.app.
What we process
- Account and access: Google, GitHub, or Apple identifier, email, display name when provided, sign-in sessions, and authentication token hashes. Device linking also temporarily stores a secret and an issued token.
- Subscriptions: for an App Store or Google Play subscription, the store’s transaction identifiers, product, price and currency, trial, renewal, and expiry status, linked to your account. Apple or Google takes the payment; we never receive card or bank details.
- Devices and connections: linked agents and clients, operating system, agent version, activity timestamps, IP addresses in operational logs, and approximate country/city derived from IP. This is not GPS location.
- Technical telemetry: account-linked model and CLI details, outcome, error classification/fingerprint, a salted session identifier, and timings. It excludes prompts, file paths, and project or session names. Disable it with
REM_TELEMETRY=0or"telemetry": falsein the agent configuration. - Optional features: push tokens and notification payloads; voice recordings and transcription results; shared-build metadata, owner, size, source reference, and expiry.
- Support: information you send us when requesting help. Do not send passwords, API keys, or private project files.
Messages and files
The relay forwards messages, files, diffs, and history between your devices. TLS protects each connection, but the relay can read this traffic. It does not maintain a conversation archive. To handle reconnections, it temporarily buffers pending messages and caches session summaries in memory. Your computer, phone, browser, and coding providers may retain their own history or caches. Coding tools send data to their AI providers under your separate account and that provider’s terms.
Why we use data
Account, access, connection, and subscription data provide the service you request (GDPR Article 6(1)(b)). Security logs, approximate location, and technical telemetry support security, troubleshooting, and reliability (Article 6(1)(f), legitimate interests). Voice input and notifications are optional and used when you enable them (Article 6(1)(a)); stop using voice or disable notifications to withdraw that choice. Necessary records may be retained to comply with law (Article 6(1)(c)).
Providers
AWS hosts the relay and service database. Cloudflare and AWS CloudFront handle network delivery and protection. Google, GitHub, and Apple handle the sign-in method you choose. Apple and Google process subscription payments under their own terms. OpenAI processes voice recordings for transcription under its API data controls. Apple, Google, or your browser’s push provider deliver notifications, whose text may include project names or request details. Public pages load fonts from Google Fonts, which receives the browser’s connection metadata.
Primary hosting is in the EU. Global delivery and some providers may process data outside the EEA. Contact us for details about the providers and applicable international-transfer arrangements.
Retention
- Account, agent, device, and location records: until account deletion or removal of the relevant record. Disabling notifications does not by itself erase the stored push token.
- Authentication: browser sessions expire after 7 days without renewal; bearer tokens after 90 days without renewal. Device-linking records expire after 15 minutes.
- Subscriptions: linked to your account until account deletion. Deletion unlinks the store record from your account; the unlinked record is kept for accounting, refunds, and tax obligations. Deleting your account does not cancel a store subscription.
- Telemetry: expires after 30 days.
- Shared builds: links expire within one hour and can be revoked sooner. New shares keep the file on your computer and register its metadata with the relay. Expired cloud records and any previously uploaded encrypted files are removed by periodic cleanup. Account deletion removes shared-build records and any stored cloud files; local copies remain yours to remove.
- Connection buffers: pending messages and session summaries expire after up to 24 hours in relay memory. Delivery receipts expire after five minutes. Account deletion clears these buffers.
- Recordings: temporary relay upload files are removed after processing. OpenAI’s processing is subject to its own terms.
- Operational logs: removed through hosting log rotation and storage limits; relevant records may be retained for a security investigation or legal obligation. Support correspondence is retained to handle the request and any related follow-up.
Cookies and device storage
Sign-in uses necessary session and security cookies. Apps and browsers also store credentials, settings, cached session content, and pending messages. These pages do not load advertising or Google Analytics trackers. Google Fonts still connects to Google to load the typeface.
Your choices and rights
You can request access, correction, deletion, restriction, or portability of personal data, object to legitimate-interest processing, or withdraw consent where applicable. Contact hello@remcode.app; we respond within one month, with extensions where the law permits. You may complain to the Spanish Data Protection Authority (AEPD).
Delete your account in Settings of the iOS or Mac app, or follow the account deletion instructions. This removes active account records and revokes shared-build links; operational logs follow their retention above. It does not delete files or coding-tool history on your own devices.
The service is for users aged 16 and over. We update this page when data handling changes; material changes will be communicated before taking effect.