Custom Storage for Copy Reports

When you process a Copy (data access) request, MineOS generates a Copy report containing the data subject's data. By default this report is stored temporarily in MineOS (in a private Google Cloud bucket). Setting custom storage lets you use your own cloud storage instead, giving you full control over where that data lives and how long it's retained.

This setting applies to Copy requests only — other request types (such as Delete or Do Not Sell) aren't affected.

Default storage vs. your own

What's stored

When a Copy request is processed, MineOS saves to the configured storage:

• Uploaded files attached to the request.
• Copies of files found by unstructured integrations (e.g. Google Drive, OneDrive).
• A JSON data file from structured integrations — the data retrieved from each integration, plus the integration metadata used to build the report (integration ID, display name, data types, and description).

On MineOS default storage, uploaded and integration files are kept 90 days from collection, and the JSON data report 45 days from when the report was compiled.

Use your own Google Cloud Storage

Step 1: Create and set up the bucket

Whether you use an existing bucket or create a new one, follow these best practices:

• Use multi-region or dual-region for high availability, and the Standard storage class.
• Use uniform bucket-level access.
• Disable versioning (important for compliance).
• Set a retention policy of 45 days or more.
• Configure CORS to allow access from your Privacy Center.

Then grant MineOS access to the bucket: in the Google Cloud Console, open your bucket's Permissions → Grant Access, paste your MineOS principal account ID (shown on the DSR Storage setup page in MineOS once you select Custom and Google Cloud), and assign the Storage Admin role. MineOS needs Storage Admin to set the bucket's CORS policy; it only manages objects in the bucket and won't change lifecycle, permissions, or other settings.

Step 2: Configure it in MineOS

1. Go to Settings → Developers → DSR Storage.
2. Select Custom, then choose Google Cloud as the provider.
3. Enter the project ID and bucket name.
4. Click Test & Save — MineOS verifies it can connect to the bucket and has the required permissions.

Caution: Don't edit file or data attachments on existing requests after changing storage — existing attachments follow the new storage configuration.