How Wedding Desk handles project data.

1. Roles

When a photographer or videographer uses Wedding Desk to manage wedding project information, that user decides what information is entered, why it is used and how long it is needed for their work.

For that project data, the user is generally the controller.

Wedding Desk processes that project data only to provide, maintain, secure and support the Wedding Desk service. For that project data, Wedding Desk generally acts as a processor.

2. Subject matter

The subject matter of the processing is the use of Wedding Desk as a workflow workspace for wedding photographers and videographers.

This may include collecting, organizing and storing wedding project information, client intake details, timelines, shot lists, vendor details, gear lists, notes, planning details, action points and delivery preparation information.

3. Duration

Wedding Desk processes project data for as long as the user has access to the workspace, beta account or product environment, or for as long as needed to provide the service, maintain security, handle support, comply with legal obligations or resolve disputes.

When access ends, project data may be deleted, returned or exported where this is technically available and legally appropriate.

4. Nature and purpose of processing

Wedding Desk processes project data to provide the features of the product.

This may include storing data, displaying it inside the workspace, organizing project information, saving changes, generating project views, supporting workflows, maintaining system reliability, protecting accounts, troubleshooting technical issues and providing support.

Wedding Desk does not process project data for advertising resale. Wedding Desk does not sell project data. Wedding Desk does not use project data to train AI models.

5. Types of personal data

Depending on how a user uses Wedding Desk, project data may include:

Client names and contact details.

Wedding dates, locations and planning details.

Questionnaire answers and intake information.

Vendor, venue and supplier information.

Timeline details, shot lists, gear lists, notes and action points.

Uploaded files or images if upload features are used.

Account and technical information needed to operate the workspace.

Users should only enter personal data that is relevant and necessary for their wedding project workflow.

6. Categories of data subjects

Project data may relate to:

Wedding clients.

Wedding guests or family members where the user enters that information.

Vendors, venues and suppliers.

Photographers, videographers and team members.

Other people connected to a wedding project.

7. User instructions

Wedding Desk processes project data only as needed to provide the service and according to the user's use of the product.

The user is responsible for making sure they have a lawful basis and appropriate permission to enter client, vendor or wedding-related information into Wedding Desk.

Wedding Desk will not use project data for unrelated purposes.

8. Confidentiality

Wedding Desk aims to keep project data confidential.

Access to project data should be limited to what is necessary for providing, maintaining, securing or supporting the service.

People or service providers with access to project data must handle it only for the purposes described in this page and the Privacy & Cookies page.

9. Security

Wedding Desk uses reasonable technical and organisational measures to protect project data.

These measures may include access controls, authentication, encrypted connections, secure infrastructure, limited access to production systems, monitoring, backups, security-focused development practices and internal restrictions on unnecessary data access.

No online service can guarantee complete security, but Wedding Desk is designed around minimal data collection and careful handling of project information.

10. Subprocessors

Wedding Desk may use trusted service providers to operate the product.

These providers may support hosting, database infrastructure, email delivery, file storage, analytics, security, error monitoring, support or similar operational functions.

Subprocessors may process limited information only where needed to help Wedding Desk provide the service. They are not allowed to sell project data or use it for unrelated advertising purposes.

If Wedding Desk adds or changes subprocessors in a way that materially affects project data, this page or the Privacy & Cookies page may be updated.

11. Assistance with data requests

Because users usually control the project data they enter into Wedding Desk, users are responsible for handling requests from their own clients or contacts.

Where reasonably possible and technically available, Wedding Desk may assist users with access, correction, deletion, export or restriction requests related to project data stored in Wedding Desk.

12. Deletion and return of project data

Users should be able to manage or delete project information through the product where those features are available.

If a beta account or product account is closed, Wedding Desk may delete or anonymise project data after a reasonable period, unless retention is needed for legal, security, backup or dispute-resolution reasons.

Export, deletion and retention options may be expanded as Wedding Desk develops.

13. International processing

Some technical providers used by Wedding Desk may process data outside the user's country.

Where required, Wedding Desk aims to use appropriate safeguards and work with providers that offer suitable data protection commitments.

14. Breach notification

If Wedding Desk becomes aware of a security incident that affects project data, Wedding Desk will take reasonable steps to investigate, limit the impact and notify affected users where legally required.

Users remain responsible for deciding whether they need to notify their own clients, contacts or authorities based on their role and legal obligations.

15. Audits and information

Wedding Desk may provide reasonable information about its data processing practices, security approach and subprocessors where needed for a user's own compliance.

Requests should be proportionate to the size, stage and nature of the service.

16. Changes to this page

Wedding Desk may update this Data Processing page as the product, beta programme, infrastructure or legal requirements develop.

The latest version will be published on this page. The Last updated date shows when this page was last changed.