How your recordings are handled.
The website runs on Modal and has account access checks and upload limits. Backups and operational processes still need verification.
Updated October 23, 2026. Alpha. Questions or vulnerability reports: support@solipsium.com.
Storage and deletion
| Editor recordings, repairs, timelines and exports | Stored on Solipsium's server on Modal until you delete them or close the account. |
|---|---|
| Tries from the homepage | The first 20 seconds and their repair, with no account or file name. The upload is deleted once those seconds are read; the rest is refused after half an hour and swept every fifteen minutes on the hosted site, so it is gone within the hour. |
| Quick restore and delivery checks | Eligible for cleanup seven days after upload. Files are removed only when the cleanup task runs, and a self-hosted copy has to schedule that task. |
| Server video enhancement | Only when the operator enables it. The upload is deleted when the job ends. The enhanced video can be downloaded only by its account, for 24 hours after the job ends; a cleanup that runs once a day then deletes the job's files. |
| Account and saved requirements | Account deletion removes media, sessions and saved requirements. A disabled account record, credit ledger and payment references remain, as described in the privacy notice. |
| Usage events and logs | Usage events contain pseudonymous identifiers and are deleted 90 days after the day they were recorded by the hosted site's cleanup task, which runs every fifteen minutes. Container log rotation depends on the deployment configuration. |
| Backups | On each day the hosted site is in use, the account database is copied to separate storage at the same host, Modal, and the newest 14 copies are kept; the privacy notice says what the copies hold. Recordings, repairs and exports are not backed up, and no copy is yet kept outside Modal. The restore procedure was rehearsed on a local test installation with generated recordings; a restore on the hosted site and the time it would take have not been verified. Keep your own originals. |
Where processing happens
The homepage quick check runs in your browser before upload. The video enhancer enlarges and sharpens a video's picture in your browser on its graphics chip and does not upload the video; only Repair the first 20 seconds sends some of its sound. A try of the first 20 seconds is repaired on the same server as the editors' repairs, without a GPU. That server runs on Modal (modal.com), which also stores recordings and the account database and runs AudioSR on a GPU for Quick restore and, in the editors, for Studio and Detail passages and the Hollywood edit's optional detail rebuild. When server video enhancement is enabled, Modal also runs its picture model, Real-ESRGAN's realesr-general-x4v3, on a GPU. Modal's privacy policy names no country, and this deployment does not choose a region. On September 27, 2026 its servers for this site answered from addresses in the United States; that is an observation, not a promise about where data stays. Cloudflare is the registrar for solipsium.com, redirects visits there to the Modal address and forwards support mail; uploads do not pass through it. The hosting provider has access to its own infrastructure, and the application's access controls do not remove that access. A copy you run yourself processes files on your own server.
Solipsium does not train models on uploaded recordings or videos. External API access and batch integrations are off unless the operator switches them on.
Application protections
- Recordings, checks and reports are checked against the requesting account. Another member's private file returns not found.
- Passwords are salted and hashed with scrypt. Sign-in attempts are limited. HTTPS sessions use secure, site-scoped cookies; changing your password ends other browser sessions.
- Browser changes require a permitted origin and a session-bound token. The external API, its keys and batch download remain unavailable unless explicitly enabled by the operator.
- Editor imports are limited to 1 GB or thirty minutes. Media probes and decoders restrict accepted formats and protocols. These controls reduce exposure; they are not an operating-system sandbox.
- Server video enhancement is switched off unless the operator enables it. While it is off, its addresses answer not found to a signed-in member, and ask anyone else to sign in first. When enabled, it accepts videos of up to 1 GB and ten minutes, at most 1920 pixels on the long side, 720 pixels on the short side and 60 frames per second, and at most 18,000 frames in all (ten minutes at 30 frames a second, or five at 60), in 8-bit standard dynamic range only. Each video is measured before any credit is spent, through the same restricted media probes and decoders.
- The Docker setup supplied for running your own copy uses an HTTPS proxy, a non-root application container and restricted container privileges. Those settings still need a deployment rehearsal. The hosted site runs in Modal's containers instead.
- If payments are enabled, card entry happens on Stripe's checkout page. The application receives payment references rather than card numbers.
- The operator can pause new processing for maintenance, such as taking a backup. While it is paused, new uploads, tries, checks, repairs and exports, including the operator's own, are refused with a 503 status and a Retry-After header. Work already accepted keeps running, and editing, downloads and accounts keep working. The switch is stored in the account database, so a restart does not change it, and a new installation starts with processing open. If the stored setting is missing or damaged, new processing is refused until it is repaired.
- Requests refused at the site's entry checks (sign-in, origin, size and the maintenance pause), attempts over the sign-in and sign-up limits, failed sign-ins and account changes are written to a security log. A record holds the requester's address, the method and the path, and the event's own details: the status and reason of a refusal, and the account's username or ID for a failed sign-in or an account change. No password, token or recording is written there. The request fields are written as escaped text, so a URL holding terminal control codes or Unicode line separators is logged as one record and cannot add fake lines. The hosting messages printed when a storage volume fails to save or reload escape the path the same way. The project's own code review found the unescaped fields on October 3, 2026, and they were fixed that day. No independent reviewer has checked the fix.
What a report's fingerprint means
A delivery report identifies its measured file by SHA-256. Matching that value confirms which file the measurements concern. It does not prove authorship, recording authenticity, restoration quality or compliance with every delivery requirement.
What remains unverified
- Files are not encrypted at rest by the application. Server and backup encryption must be assessed for the chosen deployment.
- No SOC 2 report, ISO 27001 certificate or independent penetration test has been completed. Automated tests and code review are not certification.
- A restore exercise on the hosted site, a data-retention schedule and an incident-notification process still need confirmation.
- One person operates the project. There is no staffed on-call service or contractual uptime commitment.
- Solipsium is not incorporated. Any agreement is with its operator.
Read the privacy notice for retained data, deletion limits and incident handling, and the terms for the alpha's limitations.
September 28, 2026: named Modal as the host and GPU processor and Cloudflare for the domain and support mail, and said that no region is fixed. September 22, 2026: added tries from the homepage.
September 30, 2026: the service moved from pre-alpha to alpha; no security practice changed.
October 3, 2026: added the pause for new processing and what the security log holds, with its escaped request fields. Added the backup and restore scripts, rehearsed locally on test data, and named the Hollywood edit's optional AudioSR rebuild among the GPU work.
October 17, 2026: added the video enhancer. In the browser it does not upload the video. Server video enhancement, when enabled, runs Real-ESRGAN's realesr-general-x4v3 on Modal's GPUs within its own limits, and keeps the enhanced video for 24 hours.
October 23, 2026: server video enhancement, when enabled, also refuses a video of more than 18,000 frames in all, before any credit is spent.