Privacy Policy

Last updated: October 9, 2026

This policy describes the Xentropy website and hosted platform operated by Detextit. Draft editing happens in browser memory until saved to the platform or explicitly exported. Saving a workflow sends its service definitions, instructions and selected context to the platform. Simulated calls are processed by Eve; real calls originate from your browser or local runner.

Browser drafts and website visits

Drafts contain service instructions, selected context, graph configuration and test cases. Editing a draft does not upload it. Opening an example loads its starter files into a draft without starting a workflow run. Saving a workflow uploads its selected content to your account.

Website hosting processes technical request information such as IP addresses, request URLs, and browser information. The current application includes no advertising tracker or third-party analytics SDK. This does not replace the hosting provider’s own privacy practices.

Accounts and sign-in

When Clerk is configured, Clerk handles sign-in, account creation, profile management, and sessions. The platform verifies the session and associates a persisted account, workflow graphs, and credits with the Clerk instance and user ID. Local runners use scoped, expiring credentials created by a signed-in human.

The browser uses the deployment’s configured endpoint. It obtains current Clerk session tokens for API requests and does not save those tokens in workflow drafts. Private account details are cleared from the page when the signed-in account changes or signs out.

What execution sends

Simulation requests make selected service context and input available to Eve and its model provider. Test assertions are kept outside the agent context. Real-service calls originate from the user’s browser or local runner.

The hosted API and Eve process selected service instructions, files and incoming inputs. The platform retains account-scoped definitions, graph snapshots, request IDs, outputs, timing, credit usage and execution evidence. Model and hosting providers may retain private traces according to their own policies. Real-service observations originate from the browser or local runner.

Use only information you are authorized to process. Avoid personal information and secrets unnecessary for a test. Services operating the endpoints your code contacts may receive requests under their own privacy practices.

Providers and use of information

Information is used to authorize accounts, save service definitions and graphs, simulate service requests, inspect test results, and operate the platform. Clerk provides identity services, Neon stores account data, Vercel hosts the API and Eve runtime, and the selected model provider processes simulation inputs. Contacting us by email provides your address and message to Detextit and its email provider.

Providers may process information outside your country. We do not promise a specific processing region, zero provider retention, or a particular model-training setting. Review the configured providers’ terms and controls, including Clerk’s Privacy Policy, Vercel’s Privacy Notice, and, when OpenAI is used, OpenAI’s Privacy Policy and API data controls.

Cookies and session storage

Clerk manages its authentication cookies and session state. Browser drafts use local storage. An operator-issued browser credential stays in the current page’s memory and is cleared on disconnect or reload; it is not stored with drafts. The Python helper saves its credential in an owner-only file outside the repository.

Retention and removal

Unsaved drafts remain in browser memory. Exported workflow files remain on your device until you remove them. Saving to the platform retains an account-owned copy; closing a browser does not delete it.

The platform retains service definitions, workflow versions and historical run evidence. Ending a run clears active simulated-service state and schedules resource cleanup, but does not delete saved definitions, outputs, traces or provider records. Contact the service operator about removal of retained data.

Questions, requests, and updates

Contact Detextit at info.detextit@gmail.com about information held by the Xentropy service or to make a privacy request. Include enough context to identify the relevant interaction, without sending passwords or tokens. Depending on applicable law and your circumstances, privacy rights may apply; we assess requests and may need to verify your identity. Detextit cannot directly remove data stored only on your device or in services you control.

We update this policy when processing changes and communicate material changes where required.