Privacy Architecture | StratoFusion

StratoFusion coordinates work behind the scenes so it can search connected cloud accounts, transfer files between them, and run scheduled backup or sync jobs. To provide those features, its systems need limited access to connection details, file metadata, and sometimes file content while an operation is running. This page explains that access in plain language.

What the server can access

When you use StratoFusion, the application and background systems may access:

Connection details and related account metadata needed to keep provider connections active, refresh access, and run the jobs you authorize.
File and folder metadata such as names, paths, sizes, timestamps, MIME types, container identifiers, and provider and account context so the interface can browse and search correctly.
File content during uploads, downloads, transfers, backups, and sync jobs when a feature requires secure streaming or background processing.
Operational records such as job settings, activity logs, quota usage, error details, and transfer-state snapshots needed for reliability, support, and account protection.

How StratoFusion limits that access

StratoFusion is designed to limit access to what is needed to provide the feature you requested.

Provider connection details are encrypted when stored.
Connected accounts, job history, and transfer controls are tied to the signed-in StratoFusion account that created them.
Each connected resource remains scoped by provider, account, and resource identity so one connection is not treated as interchangeable with another.
Background-job services are protected from open public access.
Internal diagnostics and troubleshooting tools are restricted to authorized use in the appropriate environment.

What StratoFusion does not keep as a long-term store

StratoFusion is not designed to be a long-term file-hosting service for your content.

Your files remain in your connected cloud accounts unless you instruct StratoFusion to move, copy, upload, download, back up, or sync them.
StratoFusion does not intentionally create a permanent hosted copy of file content as a product feature.
Temporary processing and transfer state may exist for short operational windows to support delivery, reliability, recovery, and diagnostics. It is not a customer file archive.
Provider passwords are not collected directly by StratoFusion. Provider authentication uses the provider's authorization flow.
Payment-card details are handled by Stripe rather than stored by StratoFusion.

Why this behind-the-scenes access exists

Cross-provider transfers need a system that can connect to the authorized source and destination and move data for the job you started.
Scheduled backups and sync jobs need stored connection details so they can run when you are not actively using the browser.
Unified browsing, search, and file-management views need provider metadata so they can combine results across services and accounts.
Some upload and download flows use temporary processing or delivery systems to handle provider limitations, large-file delivery, or browser compatibility.

Provider permissions

StratoFusion aims to keep provider permissions aligned with the features it currently offers instead of requesting broader access by default.

Google Drive connections currently request the Drive drive scope. The app uses Drive API metadata to label the connected account instead of requesting separate Google profile scopes in this flow.
OneDrive connections request file access, profile basics, and offline access. Work or school connections may additionally request Sites.Read.All so the app can discover SharePoint sites and document libraries without requesting broader site write permissions.
Dropbox connections request the account-information and file metadata/content scopes used by browsing, search, upload, download, copy, move, backup, and sync flows.

Encryption and transport security

StratoFusion uses practical transport and storage protections, but it is not a storage vault that is technically unable to access the jobs it runs for you.

Web and provider API traffic use HTTPS/TLS in transit.
Stored provider connection details are encrypted before persistence.
The server must be able to use those protected connection details to refresh access and execute the operations you authorize.

Third parties and subprocessors

Depending on the feature you use, data may also be processed by:

Google, Microsoft, Dropbox, and other storage providers you connect.
Hosting and file-processing infrastructure used to run transfers and deliver some downloads.
Clerk for identity and account management.
Stripe for billing and payment workflows.

These services are used for the specific product functions described above. Ordinary browsing and search do not create a separate hosted copy of your files in StratoFusion.

Self-deployment and maximum control

If you need StratoFusion's behind-the-scenes systems to run inside infrastructure you control, contact support about self-deployment. Internal deployment and transfer-service guides require admin or developer access.

Self-deployment can improve infrastructure control, but it does not change the underlying product reality that coordinating work between providers requires access to connection data, metadata, and file content during the operations you run.