Your information, explained

Privacy notice

Last updated November 13, 2026 · Applies to this website and the described RemoteCode preview

RemoteCode is independently developed and operated by Jared Ringenberg, based in the United States (“I”, “me” or “the developer”). For website operations and support correspondence, Jared Ringenberg is responsible for the personal information described here. Contact uzyrexthet@gmail.com. Instagram: @jaredringenberg.labs. Email is the preferred channel for privacy requests.

1. Visiting this website

This static website does not include advertising, developer analytics, tracking pixels, embedded social feeds, external fonts, forms, accounts or a newsletter. The website code does not set cookies or use browser local storage. An Instagram or other external link contacts that service only when you follow it; the destination's policies then apply.

Hosting: this website is hosted on Cloudflare Pages. Cloudflare processes network and request information, which may include your IP address, requested URLs, timestamps, browser/device headers, referring information when supplied, and security signals. This is used to deliver the site, protect it and operate the hosting service. Limited traffic or security information may be available to the site operator through the hosting account. This notice does not claim that hosting is anonymous or that Cloudflare keeps no logs.

Cloudflare may process information in multiple countries. Its processing and retention are described in the Cloudflare Privacy Policy. The site's no-tracking design is separate from Cloudflare's own website policies. Optional Cloudflare Web Analytics, advertising and third-party tracking are not part of this site's configuration. Any future change to that design requires a privacy review and, where necessary, consent controls.

2. App connections and local information

Information you configure: saved computer names, endpoint addresses, selected project directories, certificate pins and address hints, preferences, session pin/review markers and opaque identifiers are stored on your device as needed for the features you use. Connection credentials use platform secure storage. Some non-secret profile metadata uses ordinary app storage; not every stored field is a credential or encrypted by the same mechanism.

Conversation information: the app retrieves session titles, messages, tool activity, questions, permissions and other relevant content from your configured OpenCode backend. Recent chat pages are cached in bounded app memory rather than a developer-run chat database. Unsent drafts and attachment bytes stay in app memory and may be lost if the app process closes. OpenCode retains its own server-side history separately.

Sending: prompts, follow-ups, answers and explicitly selected attachments go to the backend you choose. That backend and its configured AI providers or tools may process, store or transmit them according to their own settings and policies. RemoteCode's local cache behavior does not limit those providers' retention. Use only information you have permission to submit.

Connections: supported local access uses approved HTTPS with certificate pinning. Remote access can use your separate Tailscale setup. Your network operators and service providers may process connection metadata. Encryption in transport is not a promise of anonymity, end-to-end encryption against your AI provider, or protection from a compromised device.

The current app code has no developer analytics, advertising or automatic crash-reporting integration. It does not automatically send your conversation content to Jared Ringenberg. This does not exclude operating-system, app-store or separately configured service diagnostics governed by those providers.

3. Permissions and actions you choose

• Camera: used with your permission to scan pairing QR codes. The app does not upload camera footage to the developer or use the microphone for pairing.
• Files and sharing: selected files or text can be staged in a draft using Android's picker or share sheet. They are sent to your configured backend only when you send the prompt.
• Clipboard: explicit copy actions write the selected content to the system clipboard; the app does not automatically inspect existing clipboard contents. Clipboard visibility and history depend on your OS and other apps.
• Notifications: optional and subject to device permission. Generic alerts may be visible on a lock screen or paired device depending on your settings.
• Diagnostics: an explicitly copied/shared safe report includes allowlisted version, platform, connectivity and feature-status information. Review any report or screenshot before sending it to someone.

4. Optional push notifications and Wear OS

Local phone alerts use app-side observations while relevant screens are active and do not need Firebase. Background push is a separate, optional setup requiring a Firebase-configured app build and a notification helper on your computer.

When enabled, your helper stores phone registration identifiers, push tokens and delivery state. Google Firebase Cloud Messaging processes the token and delivery information. Payloads contain generic alert text and opaque routing/deduplication identifiers, such as computer, session or request IDs and alert kind. The helper does not put prompts, source code, project paths, computer names or session titles in those notification payloads. Opaque identifiers and tokens can still be personal information; “generic” does not mean anonymous.

The helper observes session information on your computer to determine which alerts to send. Unsent alerts expire after one hour; deduplication records are retained for 14 days. Registrations remain until revoked, replaced or invalidated. Google may retain its own service data under its policies. See Firebase privacy information and Google's Privacy Policy. The operator of the Firebase project and notification helper depends on your installation; this website does not operate a public notification relay.

The experimental Wear OS companion requires explicit phone-side approval. It can receive bounded session context and supported questions through the phone and send explicitly submitted answers back. The watch does not receive the computer's pairing QR or backend credentials. The phone stores approved watch identities and necessary connection material; conversation context is memory-only. Google's Wear OS/Data Layer services may transport phone/watch messages over the internet when devices are not directly connected. Review Google service settings and revoke watch approval if a device is lost or no longer trusted.

5. Email, Instagram and support

If you email me, I receive your email address, display name, message, attachments and normal email metadata. Gmail/Google processes that correspondence. If you contact me on Instagram, Meta processes your account information and messages under its policies. I use information you provide to answer questions, resolve problems, handle privacy or security requests and keep relevant support records. Merely contacting me does not sign you up for marketing.

Do not send passwords, access tokens, private keys, pairing codes, unredacted QR codes or confidential projects. Share only the minimum needed. If you voluntarily send a log, screenshot or diagnostic report, it becomes part of the support correspondence. I may ask you to redact it or provide a safer report. Email and social messages are not a secure secret-submission service.

6. Purposes, legal grounds and recipients

Information is processed to deliver and secure the website, provide requested app functions, respond to support and rights requests, prevent misuse and meet legal obligations. Where EU/UK data protection law applies, the relevant grounds may include legitimate interests in providing a secure informational site and responding to enquiries, steps requested before or performance of an agreement, legal obligations, or consent for genuinely optional processing where required. Device permissions alone do not determine the legal ground for every processing activity.

I do not sell personal information or use this site for cross-context behavioral advertising. Information may be processed by hosting and communication providers as described above, disclosed when legally required, or shared as necessary to investigate abuse or protect rights. There is no advertising audience upload or data-broker integration in this site.

App connections primarily involve you, the operators of your chosen computers, and the services you configure. If you use an employer's computer or another person's backend, their administrator may control access and records. They are responsible for their processing; contacting the developer cannot delete records held only by those operators.

7. Retention, location and security

Saved device settings remain until changed or removed. Memory-only drafts and caches do not persist across process replacement. Removing a saved computer removes its local profile and credentials, but does not delete OpenCode history or AI-provider records. Revoke background push while the helper is reachable before removing its connection. Clearing app data or uninstalling is not a substitute for revoking remote credentials and registrations. Platform backup or restore behavior can vary.

Support correspondence is retained while needed to respond, resolve ongoing issues, handle disputes or meet legal obligations; its necessity should be reviewed when the matter is complete. Hosting, email and other providers apply their own operational retention and backup schedules. I do not promise immediate removal from all provider backups.

Cloudflare, Google, Meta and configured backend/AI providers may process data outside your country. Applicable safeguards and transfer arrangements depend on the provider and deployment. Contact me for information about the arrangements relevant to information I control. No security measure eliminates every risk; protect your devices and backend, and promptly revoke access after loss or compromise.

8. Your choices and privacy requests

Depending on your jurisdiction and the processing involved, you may have rights to access, correct, delete or obtain a portable copy of your personal information, restrict or object to processing, withdraw consent, or complain to your data protection authority. Applicable exceptions and identity verification may apply. There is no sale or targeted-advertising activity on this site to opt out of, including when a browser sends a Global Privacy Control signal.

Email uzyrexthet@gmail.com with “RemoteCode privacy request” and enough information to identify the relevant correspondence. Do not send an identity document unless a necessary, proportionate verification method has been agreed. Requests will be handled within applicable legal deadlines. If you disagree with a response, reply to request a review or appeal; you may also contact your competent regulator.

For local app data, use the device/app controls. For server history, contact the relevant backend operator. You can disable notification permissions, revoke helper registration and watch approval, and stop using optional services. I cannot remotely access your private devices to export or erase their records.

9. Children and changes

RemoteCode is a developer tool, not a service directed at children under 13. I do not knowingly collect children's information through this website or support. If you believe a child supplied personal information, contact me so it can be reviewed and deleted where appropriate. Local age requirements may be higher.

This notice will be updated as the website, app or optional services change. The date above identifies the latest revision. Material changes will be highlighted on the website and, where required, communicated or presented for consent before the new processing begins.