Encryption and backup scope
Supabase states that its hosted customer data is encrypted at rest with AES-256 and in transit with TLS. DeepSearch also uses private storage, signed access links, and application encryption for selected sensitive records. The provider statement describes its platform, not every third party involved in a search.
Database backups and object storage need separate recovery plans. Supabase’s database backup documentation distinguishes database records from the stored files themselves. Backup frequency, retention, restore testing, and recovery objectives should be confirmed for the relevant service configuration.
Collect and retain what the task needs
A research request should send only the input and context needed by the selected feature. Support and security reports should avoid unnecessary private records. Retention, account deletion, and legal exceptions are described in the Privacy Policy.
Information in transit and at rest
Encrypted transport protects communication with the service. Our storage infrastructure provides encryption controls, while additional application encryption protects selected sensitive information such as removal profiles. The Privacy Policy describes these measures without treating every feature as an identical storage workflow.
Private files and temporary access
Uploads can be stored in private object storage and accessed through signed links. Access to a file is limited to the relevant feature and authorized context. Some requests send content directly to a contracted search or AI provider to perform the requested operation.
Retention follows purpose
Retention depends on the feature, account state, operational needs, and legal obligations. Deleting an account or a saved item does not necessarily erase billing, security, dispute, or legally required records immediately.