HCP Phone · Updated: October 6, 2026
Privacy Policy
Audio calls
Internal audio calls use WebRTC with microphone permission and preferential direct device connections and, when needed, the operator-configured coturn TURN fallback. HCP does not record or store audio. Encrypted audio travels between the devices. Network addresses may become visible to the other participant. The configured Cloudflare STUN service discovers reachable network addresses and processes network metadata for this purpose; it does not carry conversation audio. Call history and missed calls store the server profiles, timestamps, status, ending reason and connected duration. Encrypted SDP signaling expires after 90 seconds, can no longer be retrieved after expiration and is removed at the next cleanup; connection or ending removes it immediately. Short-lived reachability information supports access, busy status and disconnection handling. Team test calls also require actual ER:LC presence. Technical diagnostics contain call references, client type/version, connection states, selected route, controlled error codes and bounded timings, but no audio, SDP signals or network addresses. Diagnostic rows expire after seven days and are deleted at the next cleanup. The operator’s coturn fallback on 82.39.212.76 forwards encrypted media when selected and processes the peers’ network addresses. Network conditions may prevent connections.
Controller and contact
Paul Brucks · c/o Online-Impressum #8873 · Europaring 90 · 53757 St. Augustin · Deutschland. E-Mail: [email protected]. Send data access, correction and deletion requests to this email.
Website and hosting
A necessary PHP session supports login, language, CSRF and OAuth state. Your manually selected language is also saved in browser local storage and the hcp_lang cookie, which expires after one year. Without a saved choice, the website starts in English. Cloudflare handles website requests in front of the PHP/database host. IP addresses, request paths, timestamps and technical errors may be processed. This phase adds no advertising or analytics cookies.
Discord customer accounts
Discord OAuth associates the Discord ID, username, display name and avatar reference with an HCP account. Licenses, team roles and support records belong to that account. HCP Phone does not ask for your Discord password.
Roblox verification
Roblox OAuth confirms the intended Roblox account. Alternatively the ER:LC API sends a private verification code to the detected player. The code is stored as a hash with expiration and attempt limits. A player-list match alone does not prove ownership.
ER:LC DNS resolution
The backend can resolve api.erlc.gg through Cloudflare DNS over HTTPS. The resolver receives the domain name and hosting server IP, not messages, Roblox identities or API keys. The operator can select the hosting DNS resolver instead.
Server and presence data
Owners store an encrypted ER:LC key, server name and configuration. The backend reads server/player lists for detection and caches time-limited presence. Installation UUID, client version and short-lived grants support access control. Keys and grants are not exposed as public configuration.
Internal team testing
Authorized team members can use a dedicated browser test profile without ER:LC presence for up to 30 minutes. Test messages and read state use the regular server-scoped messaging system. The team session binds team account, server, test identity and profile. Starts, ends, server changes and sent message IDs are audited, not full message text. Internal profile search is limited to the selected server; other users are not impersonated.
Profiles, contacts and messages
Each verified player receives a separate profile and virtual number per server. Numbers do not reach public telephone networks. Contact names, favorites and notes are stored for that profile. Direct conversations and text messages are server-scoped and available only to participants. Messages are not end-to-end encrypted; backend operations can technically process stored content.
Live delivery and read state
Short-lived delivery events contain server/profile scope, event type, resource IDs and timestamps, not message histories or text. Events have a 24-hour retention; cleanup is checked on feed requests at most once every five minutes. Messages are stored separately. Each conversation member has a last-read message cursor and read timestamp. Unread counts are calculated from these. In-Phone banners temporarily use sender and preview text in the client; locked Phones hide content by default. Reconnect state and event cursors stay in session memory. Request limits store installation ID, time window and count; inactive entries are removed after one hour during cleanup.
ER:LC Public Application
The backend adds the private global application key to requests using the encrypted stored server key. The owner opens the official ER:LC authorization page with the internal server ID and public HCP application ID. ER:LC handles authorization in its own interface. HCP stores the internal server ID and the outcome and timestamp of an actually accepted required API operation.
Moderation and logs
Reports store message IDs, involved profiles, reason, an optional description of up to 500 characters and review status. Restrictions record profile, reason, period and responsible owner/staff actor. Profile restrictions do not automatically block a server license. Audit records contain IDs and actions, not full message content or keys. Soft deletion hides a message but does not immediately erase its database record.
Local media
Unshared photos and videos stay on the PC. Explicitly attaching a photo/video or choosing a profile photo creates a private server copy. Attachments are accessible only to chat participants; profile pictures are visible to authorized profiles on the same server. Explicitly recorded audio messages and voicemail greetings are also uploaded privately; active calls are not recorded automatically. Voicemail is available to its owner and recipient, custom greetings to authorized non-blocked profiles on the same server. Camera attachments are not additionally saved to the photo library. Deleting voicemail removes recipient access but does not automatically erase its uploaded file. Photos and audio are limited to 2 MB, videos to 8 MB, and total media to 64 MB per profile. Display names, emoji, profile colors, reactions, private pins, blocks and delivery/read cursors are stored within the server profile. Unneeded uploads are currently not automatically deleted; the operator handles deletion requests.
Purposes and legal bases
Requested account, license and Phone functions support service delivery under GDPR Article 6(1)(b), where a contract exists. Access protection and abuse prevention support legitimate interests under Article 6(1)(f), taking account of users’ interests, particularly younger users. Legal retention duties rely on Article 6(1)(c). Using the service or completing login does not replace consent where consent is required.
Recipients and international processing
Chat participants receive necessary conversation data. Authorized operations process reports and security data. Cloudflare, hosting, Discord, Roblox and Police Roleplay Community process data according to their functions. The actual hosting entity, contracts, recipient countries and transfer safeguards must be confirmed before publication; EU-only processing is not promised without verification.
Storage and erasure
Verification requests, grants and presence have limited validity; expiration does not always mean physical deletion. No invented retention duration is asserted for profiles, contacts, messages, call history, reports, backups or logs. Operators must establish a retention/erasure policy and handle erasure requests; soft deletion alone is insufficient.
Your rights
Where applicable, you may request access, correction, erasure, restriction and portability, object to legitimate-interest processing, withdraw consent prospectively and complain to a competent data-protection authority. Contacts and your own messages can already be removed or hidden in the app. Contact the controller for other requests.
Required information and minors
Identity and server access checks are necessary for personal Phone functions. Automated license/grant/presence/app checks provide technical access control. The actual responsibilities of server owners and requirements for younger users must be established before public operation.
HCP PHONE