FiloSpaceFiloSpace

Trust & legal

Security

FiloSpace is designed with private-by-default storage and controlled access. This page describes the controls implemented in the current product.

Last updated: August 12, 2026

1. Security approach

Security is handled across authentication, application authorization, database policy, and private object storage. No single control is treated as enough on its own.

FiloSpace does not claim SOC 2, ISO, HIPAA, PCI, GDPR, or other certification or formal compliance status on this page.

2. Private file storage

  • File objects are stored in a private Amazon S3 bucket.
  • Raw private object URLs are not used as public download links.
  • Uploads and downloads use time-limited signed S3 URLs.
  • Storage keys are generated by the server inside the owner's namespace.
  • Generated files use new object keys and retain source-file lineage.

3. Authentication and authorization

  • Supabase Auth manages email/password and optional Google authentication.
  • Server functions verify the authenticated bearer token before private operations.
  • File, folder, tag, share, and processing services verify ownership server-side.
  • PostgreSQL row-level security restricts database rows to the authenticated owner.
  • Database constraints reinforce ownership relationships and storage-key format.

4. Uploads and file processing

File names, sizes, MIME types, extensions, operation types, and processing targets are validated against defined limits. Large uploads use S3 multipart upload so file bytes do not pass through a normal application request.

Browser-supported transformations create a separate output file. Heavy operations are modeled for an isolated background worker and are not presented as active until a real worker exists. User input cannot supply arbitrary shell or FFmpeg commands.

5. Credentials and secrets

AWS access credentials and the Supabase service-role key are read only in server code. They are not included in the browser configuration. Client code receives only the Supabase publishable key and time-limited signed URLs needed for a requested operation.

6. Controlled sharing

Files are private until their owner creates a share link. Share tokens are random, revocable, and may expire. Before issuing access, FiloSpace checks that the link exists, has not expired, has not been revoked, and still points to an available file.

A share link is a bearer capability: anyone who receives it may be able to use it until it expires or is revoked. Share it only with intended recipients.

7. Report a security issue

Send a clear description and safe reproduction steps to support@filospace.online. Do not access another person's data, disrupt the service, or include live credentials or private file contents in a report.

We will review good-faith reports. A formal vulnerability-disclosure or bug-bounty program has not been published, so this page does not promise rewards or response times.