Customer organisation
For inspection and contact information entered by workspace members, the customer organisation generally decides the purposes and means of processing.
- Define lawful purpose
- Provide required notices
- Manage member access
GDPR
Data-protection responsibilities in MeetInspect
This overview explains how GDPR roles commonly apply when organisations use MeetInspect. It complements the Privacy Policy and does not replace a customer’s own legal assessment.
What it covers
Who is responsible for what
The role depends on the information and processing activity, not simply on which product screen contains the data.
MeetInspect
MeetInspect processes customer-controlled workspace information to provide and secure the service, and acts as controller for limited account, billing and website operations where it determines those purposes.
- Operate the service
- Protect accounts
- Respond to valid requests
Service providers
Operational providers support authentication, infrastructure, storage, billing, email, AI template generation, mobile distribution and website delivery as described in the Privacy Policy.
- Limited operational purpose
- Provider obligations
- Documented disclosure
In practice
Handling a data request
Identify the controller
Workspace members should normally start with their organisation’s administrator for inspection records controlled by that organisation.
Verify and scope the request
Requests may involve access, correction, export, objection or deletion depending on location and circumstances.
Contact MeetInspect
Send privacy questions to support@meetinspect.com. Include enough information to locate the account without sending unnecessary sensitive inspection content.
Next step
Continue with the right inspection workflow
Explore the related guidance, or speak with MeetInspect about the inspection your team needs to run.
