Privacy

Privacy Policy

This policy explains what EditorSaves receives when you use the Phase 1 upload service, why the information is collected, and how the infrastructure is designed to restrict public access.

Phase 1 stores uploaded files for format research and parser development. Do not upload a save that contains personal, confidential, or otherwise sensitive information you do not want to provide to the project.

1. Information we receive

When you submit a supported save file, the upload service receives the file itself and basic metadata associated with the upload. The current database record can include the original filename, storage path, file size, MIME type, upload timestamp, IP address when the server can determine it, and an internal status value.

Cloudflare Turnstile is used as an anti-abuse control. The upload server sends the verification token to Cloudflare's verification service before accepting a file.

2. How files are stored

Uploaded save files are placed in a private Supabase Storage bucket. The application uses a server-side service role for storage operations; browser users are not given that secret. The database table used for upload metadata has row-level security enabled.

3. Why files are collected

EditorSaves is being developed as a universal save editor. Real files help the project understand format differences, versions, schemas, compression, and edge cases that cannot be reliably inferred from filenames alone.

4. Retention

The project intends to retain uploaded files for up to 30 days during the initial research phase, after which files can be deleted. Retention behavior may evolve as the service changes; the current upload system does not promise indefinite storage.

5. Security

The service applies size and extension validation in the browser and again on the server. Files are stored under UUID-based paths, the bucket is private, and the Supabase service-role credential is server-only. These measures reduce accidental exposure but cannot make internet services risk-free.

6. Your responsibility

Only upload files you are permitted to provide. Make your own backup before experimenting with save editing, and do not submit credentials, private documents, or other unrelated sensitive data inside a save file.

7. Changes to this policy

This page may be updated as EditorSaves evolves. Material changes should be reflected here before they become part of the normal service workflow.