# Privacy
Last updated: October 1, 2026
This Privacy Notice explains what information the service may process, why it is processed, and how it is used to provide schema, data, and API features.
## Information you provide
The service may process information that you provide directly, including:
- account and profile information;
- schemas, classes, properties, validation rules, and documentation;
- data objects created from schemas;
- object versions and schema version history;
- API requests, examples, and integration metadata;
- messages or contact requests sent through the website.
You should avoid submitting sensitive personal data unless the service explicitly supports that use case and you have the right to process it.
## Information collected automatically
When you use the service, technical information may be collected automatically, including:
- IP address, user agent, device and browser information;
- request paths, timestamps, API methods, response codes, and latency;
- authentication and session events;
- diagnostic logs and error reports;
- security events related to access, rate limits, and abuse prevention.
This information is used to operate, secure, debug, and improve the service.
## How information is used
The service may use information to:
- provide web and API access to schemas and data;
- validate, store, version, and retrieve structured objects;
- generate documentation and API contracts;
- maintain account access and permissions;
- monitor reliability, performance, and security;
- investigate abuse, errors, or unauthorized access;
- communicate about support, changes, or service-related notices.
## API and published data
Some schemas, objects, examples, or API responses may be public or accessible to users with a link, depending on how the service is configured.
Before publishing data through API endpoints, make sure it is intended to be shared and does not include private or regulated information.
## Data retention
The service may retain schemas, objects, versions, logs, and related metadata for as long as needed to provide the service, preserve version history, comply with obligations, resolve disputes, or maintain security.
When data is deleted, it may be removed immediately or marked as deleted first, depending on the feature and the need to preserve integrity, auditability, or version history.
## Security
The service uses reasonable technical and organizational measures to protect data. No online service can guarantee absolute security.
You are responsible for protecting account access, API credentials, and any systems that connect to the service.
## Third-party services
The service may rely on infrastructure, authentication providers, analytics, communication tools, or hosting services. These providers may process information only as needed to support the service.
External links and integrations are governed by their own terms and privacy practices.
## Your choices
The service does not currently provide a complete self-service account export or account-deletion control. You can request access, correction, export, or deletion through the contact form linked on the website. Include enough account information for the operator to identify and verify the request, but do not send passwords or API-token secrets.
Object API responses are not a complete account export. A deletion request may require ownership transfer and may leave soft-deleted rows and append-only Action history. Some information may also remain for security, legal compliance, backup expiry, audit, or other legitimate operational needs. The operator should explain any retained categories when responding to a request.
## Changes
This Privacy Notice may be updated as the service evolves. Material changes should be reflected by updating the date above or by another reasonable notice.
## Contact
For privacy questions or requests, use the `/contacts` page. The application does not currently expose request status; the service operator handles and tracks the request operationally.