Privacy Policy

Most privacy policies are dense walls of legalese designed to protect a company while exploiting your data. This privacy policy is different. It is written to protect you, respect your time, and codify a simple truth: Your work belongs to you, and we have no business looking at it.

1. The Core Philosophy: Zero Asset Storage

Callistra is built as a private, local-first sandbox environment. Our infrastructure ensures that the tools you interact with process your files directly on your machine rather than in our databases.

• No Accounts: You do not need to sign up, log in, or provide an email address to use any tool on Callistra.
• No File Uploads: When you use a tool to manipulate an asset, code snippet, or design file, that file is never uploaded to a remote backend server.
• No Asset Storage: Because your production items remain localized, we cannot store them, catalog them, or review them.
• No AI Training: We do not track your outputs, and we never use your proprietary work to train generative language or design models.

2. Technical Architecture: How It Works

Every application on Callistra runs exclusively within your web browser’s local sandbox environment.

If you disconnect your internet entirely after loading a tool page, the tool will still function flawlessly. Your workspace assets remain completely bound to your local machine.

3. Cookies and Third-Party Analytics

To evaluate traffic metrics and steadily optimize application behavior, Callistra interfaces with external analytics utilities.

• Google Analytics Cookies: We utilize Google Analytics to capture aggregate, non-identifiable usage statistics. Google Analytics deposits first-party cookies (such as _ga) in your browser memory to monitor user sessions, track popular tools, and evaluate site navigation.
• Asset Isolation: While Google Analytics documents metadata like page visits and technical browser types, it has zero visibility into the files, code structures, or media objects processed through our interface. Your actual inputs never cross into Google's tracking pipeline.

4. Server Logs and Hosting Infrastructure

Like all web pages, the server infrastructure hosting Callistra automatically receives basic, non-identifiable technical packet headers required to transmit core site files to your layout engine (such as your network IP address, browser distribution profile, and temporal timestamps).

This tracking occurs solely to monitor overall host performance, block distributed network attacks, and maintain platform stability. These system logs are kept isolated from the utilities themselves and are never merged with your tool interactions.

5. Local Autonomy & State Persistence

Certain interactive tools may offer to retain your layout preferences or persistent syntax configurations for local convenience.

• Any custom parameters saved between your platform visits are logged solely inside your browser's native Local Storage or Session Storage.
• This tracking records data locally, never migrates off your physical machine, and can be deleted instantly by purging your temporary browser cache.

6. Intellectual Property & Sovereignty

Everything you input into Callistra, modify with Callistra, or generate using Callistra remains entirely under your sovereign ownership. We claim zero rights, titles, or interest in any work you process through our toolbox.

7. Changes to This Policy

We won't sneakily alter this policy to pivot our business model toward data monetization. If we build new tools, they will adhere strictly to this client-side manifesto. Should technical delivery mechanisms change, any updates to this policy will be clearly posted on this page with an updated timestamp.

8. Contact

If you have questions about our local-first architecture or want to review our open philosophy, you can contact us directly via our public repository channel on GitHub or reach out through the contact channels listed on our main page.