Privacy Policy

1. Overview

Eidos develops the open Eidos File ecosystem, Eidos Lite, the browser editor, command-line tools, and optional hosted services. This policy explains what information we process when you use eidos.space and those hosted services.

2. Local files

Eidos File and Eidos Lite are local-first. Files you create or open remain on your device unless you explicitly send data to a hosted service. You do not need an Eidos account to use the core local tools.

• We cannot access local files that you do not upload or sync.
• Your local files continue to work when you sign out or stop using a hosted service.
• You are responsible for backups of data kept only on your devices.

3. Account, authentication, and email preferences

If you create an account, we process information needed to identify and secure it. Depending on the sign-in method, this may include your name, email address, email-verification state, authentication-provider identifier, passkey metadata, session information, and security logs.

When registration offers an optional email preference, we record your selection and the related time, source, and policy version. If enabled, we may send occasional Eidos product news and offers. You can unsubscribe from marketing email at any time; account, security, transaction, and service messages are handled separately.

4. Payments and Credits

When you make a purchase, payment providers such as Creem process your payment details under their own privacy policies. Eidos receives the transaction identifiers, product, amount, status, and other information needed to grant Credits or a paid service period, prevent duplicate fulfillment, provide receipts, and support your account. Eidos does not store full card details.

5. Eidos Sync

Eidos Sync is an optional hosted service for end-to-end encrypted version synchronization and recovery. File contents, SQLite snapshots, file paths, branch names, and saved version messages are encrypted on your device before upload and decrypted on your devices. The Sync service does not receive your sync password or decryption keys and cannot read these encrypted contents.

The service still processes account and device identifiers, the cloud Space display name, repository identity and encryption profile, object sizes and counts, storage usage, request timing, opaque relationships between saved versions, and operational and security logs. End-to-end encryption does not hide this metadata or all activity. Do not put confidential information in a cloud Space display name.

The sync password is separate from your account password. If you choose to remember it and suitable operating-system secure storage is available, Lite protects it locally on that device; it is not stored with your synced files. Eidos cannot recover the sync password or decrypt your cloud copy for you. Resetting your account password does not restore encrypted contents. Preserve readable local copies and keep your sync password safe.

Sync encryption protects the encrypted cloud copy. It does not encrypt your local folders, working SQLite files, attachments, or decrypted caches. It does not extend to content you separately send to Eidos Publish. Local files remain independent of hosted access. Revoking a device blocks its service access but cannot erase copies or keys already held by that device.

6. Eidos Publish

Eidos Publish is an optional hosted service for sharing Eidos Files, Markdown documents, forms, and related attachments. When you publish, we process the uploaded source and attachments, content fingerprints, publication versions, slugs and hostnames, access and branding settings, account identifiers, storage usage, and operational logs needed to store, deliver, update, and protect the publication.

A public publication can be accessed by anyone with its address. Password-protected or account-restricted publications use additional access controls, but you should publish only information appropriate for the selected audience. People who receive public content may copy or cache it outside Eidos.

7. Forms and responses

When a publisher enables a Form, Eidos processes the form definition, submitted answers and attachments, submission time, and security information needed to prevent abuse. If the publisher requires an Eidos account, we also process the respondent's account identifier to enforce that setting and any response limit.

The publisher chooses the questions, purpose, audience, and use of responses and is responsible for providing any notice or obtaining any permission required from respondents. Eidos processes submissions to host, secure, and deliver the Form and to make responses available to the publisher. Eidos Publish is not designed for regulated sensitive personal data or services directed to children. Unless Eidos separately agrees in writing, do not use it to collect health, genetic, biometric, children's, or other data subject to special legal requirements.

8. Website data and cookies

We use essential cookies or similar storage for authentication, language preference, security, and request continuity. We may collect limited technical data such as browser type, approximate network information, requested pages, timestamps, and error logs to operate and protect the service. If analytics are enabled, we use them to understand aggregate product usage rather than to read your local content.

9. Sharing and service providers

We share information only with providers needed to run Eidos, such as hosting, authentication, email, storage, fraud prevention, and payment services; with a publisher or other recipient you direct us to share with; when required by law; or when reasonably necessary to address fraud, abuse, security, or legal claims. We do not sell your personal information.

10. Retention and security

Published content and Form submissions are retained while needed to provide the publication and collection features, subject to the applicable plan, service settings, and deletion actions. When content is deleted or a service ends, we remove it from active systems within a reasonable period, although limited copies may remain temporarily in backups, security records, or records we must retain by law. Deleting a public publication cannot remove copies made by other people.

We retain account, transaction, and operational data only as long as needed to provide the service, meet legal obligations, resolve disputes, and prevent abuse. No system is perfectly secure, but we use access controls, signed webhooks, scoped credentials, and other safeguards appropriate to the data being processed.

11. Your choices

You can use local Eidos tools without an account, disable optional Sync, revoke Sync devices and CLI keys, unpublish hosted content, and export or retain your local files independently. Publishers can collect or delete Form responses using the available product controls. To request access to, correction of, or deletion of account data, contact us using the address below. Some transaction, security, or legal records may need to be retained.

12. Changes and contact

We may update this policy as the product or applicable requirements change. We will publish the revised policy here and update the date above. Privacy requests can be sent to support@eidos.space. GitHub and Discord remain available for general product discussion, but please do not post personal or confidential information in public channels.