← Back to home

Legal

Privacy & Data Protection

How AiGiS handles personal data, who is responsible for it, and the principles the product is built around.

Draft — pending legal review

This is a working draft

The wording on this page is a template prepared by the engineering team to describe what the product actually does today. It has not been reviewed by legal counsel and must not be treated as your organization's final, binding privacy notice until it has been reviewed, completed with your company's details, and approved.

Roles & responsibilities

Data protection on AiGiS is shared between your organization and us, with clearly separated roles:

  • Controller — your organization is the data controller for the personal data your employees enter into AiGiS (incident reports, safety observations, inspection records, team and role data). Your organization decides what is collected and why.
  • Processor — AiGiS acts as the data processor, operating the platform on your organization's behalf under a Data Processing Agreement (DPA).
  • Administrators — within your organization, users with the Owner or Admin role (or any custom role granted the relevant permissions) manage accounts, roles, and access on your organization's behalf.
  • AiGiS staff do not access your organization's data except where strictly necessary to operate, secure, or support the service.

Privacy by design & by default

We try to build the product so the safe, private option is the default one, not something you have to opt into:

  • New roles are created with zero permissions by default — access is granted explicitly, never assumed.
  • Every action in the app is scoped to your organization; no user can see or affect another organization's data.
  • Temporary credentials, such as profile photo links, are never written to persistent local storage.
  • Uploaded images automatically have EXIF and GPS metadata stripped before they leave your device.
  • Debug and diagnostic logs redact tokens, passwords, and other secret-shaped fields automatically.

Data minimisation — what we actually collect

We only ask for the data needed to run an HSE (Health, Safety & Environment) workflow:

We do not ask for date of birth, home address, national ID numbers, or any other data that isn't needed for that purpose.

  • Account: first name, last name, email address, and a securely hashed password. Nothing else is required to create an account.
  • Organization membership: your role, assigned plant/department, and the permissions granted to you.
  • Work records: the incidents, safety observations, and inspections you or your organization choose to record, plus optional photo attachments.

How we protect your data

Data in transit is encrypted (HTTPS/TLS). Access to organization data is scoped by role and permission, and administrative actions are restricted to privileged roles within your organization.

[Placeholder — to be confirmed with hosting/infrastructure team]: data at rest is encrypted, backups are encrypted and stored securely, and hosting is located at: __________.

Cookies

We only use strictly necessary cookies: one to keep you signed in, and one to remember your active organization/workspace. We do not use analytics, advertising, or tracking cookies.

You can review your choice at any time from the cookie banner shown when you first visit the site.

Data retention

[Placeholder — retention periods to be defined per data category and confirmed with your organization's compliance requirements, e.g. incident records, employee accounts after departure, audit logs.]

Your rights

Depending on your role and your organization's configuration, you can request access to, correction of, or deletion of your personal data by contacting your organization administrator or AiGiS support.

Changes to this policy

We may update this page as the product changes. Material changes will be communicated to organization administrators.

Questions about your data?

Reach out to your organization administrator, or contact AiGiS directly.

privacy@aigis.example