Skip to main content
The inspected implementation handles account identifiers and profile fields, provider credential files, provider/bucket identifiers, object names and metadata, and object bytes during retrieval or transfer. PostgreSQL stores application records. Redis backs session state. Provider credential files are uploaded in encrypted form to configured Google Cloud Storage. Profile images are uploaded to a configured Google Cloud Storage bucket. During migration or synchronization, the backend retrieves object content from a source adapter and writes it to the destination adapter. The code path holds object bytes in memory. This is not an end-to-end design: the backend processes the content while performing the requested operation. The repository alone does not verify production hosting region, retention periods, backup lifecycle, operator access, complete logging coverage, TLS deployment, or deletion timelines. Maintainers must confirm these details before publishing formal privacy commitments.