Privacy Policy

1. INTRODUCTION & SCOPE OF PRIVACY COMMITMENT

Accelerated Logic provides local browser tools alongside connections to cloud model providers and optional external services. “Local-first” describes where many workspace projects are stored; it does not mean every feature runs offline or that every request stays on this device.

2. BROWSER STORAGE AND SYNC

Chat history, files, settings, and tool projects are stored in browser-managed IndexedDB and localStorage by default. The app does not use a central account database to synchronize chat history, but requests to connected providers and optional integrations follow the data flows described below. Clearing browser site data may remove unsynced work.

3. LOCAL WORKSPACE STORAGE & INDEXEDDB SPECIFICATIONS

Workspace data is saved in browser storage on this device. Browser storage is not an encrypted vault against other scripts running with access to this site, and it can be removed by clearing site data. Export important work before clearing browser storage or moving to another device.

4. THIRD-PARTY INTEGRATIONS & API CREDENTIALS MANAGEMENT

Local WebGPU/Transformers models, Whisper transcription, and Kokoro voice generation run in the browser after runtime and model files download. When you use a connected model, the prompt and selected context are sent to that provider. Some remote-provider requests, including the required authorization header, pass through the Accelerated Logic server proxy before the provider receives them; local endpoints may be called directly. Provider retention and training practices are governed by that provider's policies. API credentials are stored in browser storage. If you connect Google Drive, the OAuth flow requests your account email and stores it locally so the app can label the connected account; it is not added to model prompts by this integration.

5. WORKSPACE PRIVACY VS. PUBLIC MONETIZATION COOKIES (ADSENSE)

The public site and private workspace have different purposes. Pages load Google Fonts and KaTeX from jsDelivr. The Security Policy page loads Tailwind CSS from its CDN. Blog posts that include a video load it from YouTube's privacy-enhanced embed host; interactive samples may load resources named with that sample. Optional connected model services, including Puter when selected, receive requests when you use them.

• Workspace pages: Chat and tool features can contact the provider or service you choose. Do not submit information you are not authorized to share with that service.
• Current ad status: As of September 27, 2026, public pages do not display Google ads.
• If Google-served ads are enabled: Google and its partners may use cookies to serve ads based on a visitor's prior visits to this site and/or other sites on the Internet. They may also use web beacons or similar technologies and receive IP addresses and browser or device identifiers to serve, measure, limit, and personalize ads, subject to available settings and required consent.

If ads are enabled, you can manage personalized advertising through Google Ads Settings or your browser controls. Google explains its data use in How Google uses information from sites or apps that use its services. We do not intentionally send chat prompts or API keys to advertising providers. Where Google requires a certified consent-management platform, personalized ads for affected users must remain disabled until that consent flow is configured.

6. COMPILING AND EXECUTION SANDBOX SAFETY

Python and generated-code previews run in browser sandboxes with restricted permissions. Sandboxing is a defense-in-depth measure; it is not a guarantee that arbitrary code is safe. Do not put secrets into code you plan to run or share.

7. DATA PORTABILITY & WORKSPACE DELETION

Use workspace export controls to download supported data. Clear All Data removes browser-stored app data and attempts to delete connected Google Drive backups; verify Drive if cleanup reports an error or if you use another connected account. Google Drive data remains subject to Google's account and retention controls.

8. AUTHENTICATION AND SECURITY LOGS

GitHub authorization uses a short-lived, HTTP-only SameSite=Lax state cookie to complete the OAuth callback; it expires after 15 minutes and is cleared when the flow ends. Server-side origin checks may write security-warning log entries containing a client IP address, request URL, or origin when a request is rejected. This repository does not set a retention period for deployment-provider access or security logs; those logs are handled under the hosting provider's terms.