Privacy Policy

Altace has separate actions for screen capture, selected text, queued screenshots, and the configured rolling video and rolling audio buffers. The material processed depends on the action you deliberately invoke. A recent interaction may also provide continuity when a request is a follow-up. Your issued access key authorizes the application.

Altace processes the material you point it at. It is not presented as a continuously recorded archive of your screen or of conversations around you.

A request goes to Altace systems when you invoke and submit an Altace action. It carries the context selected for that request so server-side AI processing can interpret it and produce an answer. The capture modes are not described as one automatic combined upload.

Submitted captures may be processed by third-party AI service providers acting on Altace's behalf in order to interpret the material and generate an answer. Those providers are configured not to use submitted content to train AI models.

Recent desktop audio is held in a rolling buffer on your machine. You select the buffer duration in settings: 30, 60, 90, or 120 seconds. The buffer replaces older audio as new audio arrives, so the moments just before you trigger Altace are available with your request.

The buffer supplies audio only when you decide to ask. It is not a searchable conversation record and it is not delivered unless you include it.

You can pause or disable rolling audio capture in the desktop app. That choice persists after the app restarts.

Altace can also hold a recent screen recording, together with system audio, in a rolling video buffer on your machine. You select the buffer duration in settings: 30 or 60 seconds. The buffer replaces older video as new video arrives.

Rolling video has its own dedicated hotkey. The recent clip is used only when you press that hotkey to ask. It is not a continuous screen recording archive and it is not delivered unless you invoke it.

You can pause or disable rolling video capture in the desktop app. That choice persists after the app restarts.

Your questions and answers are grouped into sessions so that a follow-up can be understood in the context of the interaction it belongs to. A recent interaction can inform a related follow-up instead of treating it as isolated. This does not mean every earlier capture or interaction is automatically attached to every new request.

An access key authorizes the desktop application. On this website the key is held only in the page while you validate it. It is never written into a page address, browser storage, a cookie, or an analytics event.

Answers are delivered through Telegram. You choose where they land: your own chat, up to five team groups, or team groups alone with your personal chat muted.

Anything delivered to a Telegram group is visible to that group's participants and stays subject to Telegram's terms and privacy practices. Altace does not control how Telegram stores those messages.

The website has no accounts, no sign-in, and no user profile to build. The access form is a third-party Google Form: information submitted there is handled by Google under Google's terms, and this site does not store it directly.

Raw screenshots, captured text, raw video recordings, and raw audio submitted with your requests are stored for 90 days and then deleted, or sooner when you request deletion.

Redis interaction history and recent context are retained for 24 hours to support relevant follow-up questions. This temporary context is separate from the archived user questions and generated answers described below.

User questions and generated answers are archived and retained until you request deletion. They are not deleted when the 24-hour Redis interaction context expires.

On your machine, the configured rolling audio buffer replaces older local audio as new audio arrives according to the selected 30, 60, 90, or 120-second duration. The configured rolling video buffer likewise replaces older local video as new video arrives according to the selected 30 or 60-second duration.

Operational, security, and diagnostic logs are retained for up to 7 days for monitoring, troubleshooting, and security purposes, after which they are deleted in accordance with applicable retention practices. This period does not apply to information retained separately under the data-retention periods described in this policy.

Altace does not currently maintain a configured backup-retention schedule. If backup copies are created through other systems or services, their retention and deletion practices may differ. Deletion from active systems does not necessarily mean that copies in backups, if any, are immediately deleted.

Altace also stores access-key information, session identifiers, and usage and quota records to authorize access, maintain session continuity, and administer usage limits and top-ups.

Access-key information is retained as a record of issued keys and kept for as long as needed to administer access and handle disputes. When you request deletion, the key is revoked and can no longer be used.

Session identifiers expire after 90 minutes of inactivity, or immediately when a session is reset. A copy of the session identifier is also stored alongside each archived question and is removed with that question when it is deleted.

Usage and quota records, including records of paid top-ups, are retained for as long as needed for payment, refunds, and disputes.

You can ask for your data to be deleted at any time by emailing altace.contact@proton.me or contacting the Altace team through Telegram at @altace_bot. Include your access key, or another identifier the team can use to locate the records associated with you. You never need to send a password or any similar secret.

On request we delete your question and answer history and any stored screenshots, video, or audio recordings, and revoke your access key. Access-key, usage, and billing records are retained as long as needed for payment, refunds and disputes.

Requests are reviewed before they are carried out, and some information may need to be retained where applicable law requires it. Uninstalling the desktop application does not by itself delete records held on Altace systems; a deletion request is the way to have those removed.

Captured material is used to interpret your request and produce an answer, to maintain continuity for follow-up questions, and to operate, secure, and diagnose the service.

Altace does not train or improve AI models using your captured material. Third-party AI providers used to process a request are configured not to use submitted content to train AI models.

Submitted material passes through Altace systems and answers delivered through Telegram also pass through that third party. No claim of end-to-end encryption, local-only processing, or a particular compliance certification is made here.

For a privacy question, a deletion request, or a data-handling clarification, email altace.contact@proton.me or reach the Altace team through Telegram at @altace_bot.