Privacy Policy

Effective August 25, 2026

Uart Debug is an experimental browser-based AVR and UART tool. This policy explains what the project processes when you use the site, Google sign-in, compilation, or the AI assistant.

Who is responsible

The Uart Debug project operator is responsible for this service. For privacy questions or data requests, email uartdebug@gmail.com.

Information we process

• Google sign-in. Google provides a stable account identifier, email address, and email-verification status. Uart Debug stores a keyed pseudonymous form of the identifier, a masked email, and account timestamps. It does not store Google access tokens or refresh tokens.
• Sessions and installation identity. Signed cookies identify the browser installation and login session. The installation cookie can last up to 400 days; the session cookie can last up to 30 days. They support authentication, AI Credits, and abuse prevention.
• Local project data. AVR files, guide edits, interface preferences, and the reviewed Project instruction are stored in your browser's local storage. AI chat history is kept in page memory.
• AI requests. Your message, selected MCU, current project source and guide, recent conversation, and Project instruction are sent to OpenAI to answer or generate requested project material. A stable pseudonymous browser safety identifier and a per-request ID are also sent for abuse prevention and operational tracing. Google identifiers, email, and authentication cookies are not included.
• Usage and security records. The service records request identifiers, model and token usage, AI Credit accounting, timestamps, and pseudonymous account/device links. Web-server logs may include IP address, requested URL, time, referrer, and user agent.
• Compilation and serial access. Compilation source is written to a temporary server directory and removed after the job. Web Serial data stays between your browser and the selected device and is not sent to Uart Debug servers.

Why we use it

We process this information to provide the requested tools, authenticate users, allocate and account for AI Credits, keep project updates consistent, secure the service, investigate failures, and prevent abuse.

Service providers

DigitalOcean hosts the service. OpenAI processes AI-request content with API storage disabled for application responses; OpenAI may retain limited data for abuse monitoring under its API data controls. Google provides authentication. These providers process data under their own terms and privacy commitments.

We do not sell Google user data, use it for advertising, or send it to OpenAI. Uart Debug does not use Google identity data to train a general AI model.

Retention

• OAuth login transactions expire after about 10 minutes.
• Login sessions expire after up to 30 days.
• Browser installation cookies expire after up to 400 days.
• Operational web and service logs are normally kept up to 14 days.
• Server-side AI draft specifications become eligible for automated cleanup about 30 days after their last write. Cleanup runs with later draft activity, so deletion may occur after that point rather than at an exact deadline.
• Pseudonymous account, device, and AI Credit ledger records are retained while needed to operate access and prevent repeated free-limit abuse. Automated expiry for these records is still under development.

Your choices and deletion

You may use the non-AI AVR and UART tools without Google sign-in. You can sign out at any time, clear site cookies/local storage in your browser, and revoke Uart Debug in your Google Account connections. To request access, correction, or deletion of server-side account data, email uartdebug@gmail.com. Because the service stores only a masked email, the operator will provide verification steps and may ask for recent session or request details. Some minimal accounting or security records may be retained where necessary to prevent fraud or comply with law.

Security and international processing

The service uses HTTPS, signed opaque cookies, restricted server secrets, and pseudonymous identifiers. No online system is completely secure. Hosting and providers may process information in the United States or other countries where they operate.

Children

The service is not directed to children who cannot legally consent to this processing. A parent or guardian should supervise use where local law requires it.

Changes

Material changes will be reflected here with a new effective date. If a change introduces a new use of Google user data, Uart Debug will provide notice and request any required consent before that use begins.