Data Deletion Policy

Capture Snaps
Last Updated: August 18, 2026

This Data Deletion Policy explains how operators and guests can request and carry out the deletion of data associated with Capture Snaps. This policy supports your rights under the UK GDPR, EU GDPR, and other applicable data protection laws, including the right to erasure (“right to be forgotten”).

1. Overview

Capture Snaps provides self-service deletion tools within the desktop application and admin dashboard. Most data can be deleted directly by operators without needing to contact us. Where self-service options are not available, we process deletion requests promptly upon receipt.

1.1 Automatic 60-day deletion

Capture Snaps automatically deletes managed event records and associated managed cloud media 60 days after the event end date. Operators may delete individual uploads, all event uploads, or an entire event earlier. This automatic process does not delete local files, exported copies, or copies already synced to third-party services such as SmugMug or Dropbox.

2. Data You Can Delete

2.1 Individual Uploads

Operators can delete individual photo uploads from the gallery view in the desktop application or admin dashboard. Deleting an upload removes:

• The upload database record
• Associated stored media files (from Cloudflare R2 or Supabase Storage)
• Associated metadata (thumbnails, moderation status, device identifiers)

2.2 All Uploads for an Event

Operators can delete all uploads for a specific event in bulk. This removes all upload records and associated stored media for that event.

2.3 Entire Events

Operators can delete an entire event, which removes:

• The event record and all event metadata
• All associated upload records and stored media
• All associated templates and assets managed through Capture Snaps
• Event configuration and settings

2.4 Local Application Data

You can remove all locally stored data by:

• Uninstalling the Capture Snaps application
• Removing the app data directory for your operating system profile

Local data includes cached files, preferences, integration credentials, and runtime state.

2.5 Subscription Data on Device

You can remove the saved subscription/customer ID from a specific device within the app settings, clearing the local activation state.

2.6 Optional Integration Data

You can disconnect optional integrations (SmugMug and Dropbox) at any time through the application settings. Disconnecting removes locally stored credentials used by Capture Snaps for that integration.

Important: Disconnecting an integration does not automatically delete data that has already been synced to that third-party service. You must manage deletion of synced copies directly within each provider.

3. How Deletion Works

3.1 Cloud Data (Managed by Capture Snaps)

When you delete uploads or events through the application:

• The database records are removed from Supabase
• Associated media files are deleted from Cloudflare R2 (primary storage) and Supabase Storage (fallback)
• Associated thumbnails and generated derivatives are removed

In rare cases, if a storage provider operation fails temporarily during deletion, some orphaned files may persist until the next cleanup attempt.

3.2 Local Data

Local data (cached images, preferences, logs) is removed when you uninstall the application and clear the app data directory. Operational logs are overwritten on each app restart.

3.3 Third-Party Data

Data synced to third-party services (SmugMug and Dropbox) is managed by those providers. You must delete synced copies directly through each service unless the integration supports direct cleanup for that specific item.

3.4 Billing and Subscription Data

Stripe billing records, payment history, and subscription data are managed by Stripe. Capture Snaps stores only subscription identifiers and status required for licence validation. To manage or delete your Stripe billing data, use the Stripe customer portal or contact Stripe directly.

4. Requesting Deletion Assistance

4.1 Operator Requests

If you cannot delete data through the self-service tools in the application, you can request deletion assistance by contacting us:

Email: james@capturesnaps.com

Please include sufficient detail for us to identify and locate the data, such as:

• Event name or event code
• Approximate date of the event or upload
• Description of the specific data you want removed
• Your Stripe Customer ID (if related to account data)

4.2 Guest Requests

If you are an event guest and wish to have a photo or upload removed:

1. Contact the event operator first. The operator is the data controller for content collected at their events and can delete uploads directly through the application.
2. If the operator is unavailable or unresponsive, contact us at james@capturesnaps.com. Please provide as much detail as possible, including:
   • The event name, code, or date
   • A description of the image(s) you want removed
   • Any other information that helps us identify the content

We will make reasonable efforts to locate and remove the data or assist the operator in doing so.

4.3 Data Subject Access Requests (DSARs)

Under the UK GDPR and EU GDPR, you have the right to request access to, correction of, or deletion of your personal data. To submit a formal data subject request, contact us at james@capturesnaps.com. We will verify your identity before processing the request.

5. Response Times

6. Data We May Be Unable to Delete

Certain data may be retained even after a deletion request, where required or permitted by law:

• Stripe billing and payment records retained by Stripe for financial, tax, and regulatory compliance
• Data retained by third-party services that have already received synced copies (outside Capture Snaps’ direct control)
• Records required by law for accounting, fraud prevention, legal proceedings, or regulatory obligations
• Anonymised or aggregated data that can no longer identify any individual (not subject to erasure requests under GDPR)

Where we are unable to fully comply with a deletion request, we will inform you of the reason and the legal basis for retention.

7. Verification

To protect your data, we may need to verify your identity before processing a deletion request. For operator requests, this may include confirming your Stripe Customer ID or event details. For guest requests, we may ask for information that helps us confirm you are the data subject.

8. Changes to This Policy

We may update this Data Deletion Policy from time to time. Changes will be reflected by updating the “Last Updated” date at the top of this page.

9. Contact Us

For deletion questions, requests, or any concerns:

Capture Snaps
Email: james@capturesnaps.com

For broader privacy questions, please refer to our Privacy Policy.