S

SignGraf

Privacy Policy

Admin login

Privacy Policy

Effective date: 8 September 2026

1. Who we are

SignGraf is a field data collection and fitting management application used by authorised staff to record shop visits, installation measurements, GPS locations, and before/after photographs. This policy explains what information the app and admin portal collect, why they are collected, and how they are handled. SignGraf is intended for organisational use. Personal data is processed to operate field operations for your organisation.

2. Information we collect

Account information. When an account is created we collect full name, email address, phone number, role (for example field executive, fitter, or admin), and a password. Passwords are stored in hashed form on the server. The mobile app stores a session token in secure on-device storage; the admin portal uses a session cookie. Field entries. Entries may include shop name, batch and excel identifiers, material, dimensions, pole counts, remarks, assignment details, and activity logs (who created, updated, or completed an entry and when). Location. With permission, the mobile app reads GPS coordinates when a user captures a location for an entry, and may reverse-geocode those coordinates into a street address. Location is recorded for the job, not used to track users in the background. Photos. With camera or photo-library permission, the app collects initial (before) and after-installation images attached to an entry. Images may be annotated and uploaded to the organisation’s server. Uploaded images are stored so authorised staff can review them in this admin portal. Device and technical data. The app and admin portal communicate with the organisation’s API over the network. Standard connection data (such as IP address) may be logged by the server. We do not use advertising identifiers or third-party analytics SDKs in the SignGraf mobile app.

3. How we use information

We use this information to: • Authenticate users and enforce role-based access (field staff vs admin). • Create, assign, review, approve, and close field jobs. • Show job locations on maps and help teams navigate to a site. • Store photographic evidence of site conditions and completed work. • Export entry records (for example CSV) for operational reporting. • Maintain an audit trail of changes to entries and user roles. We do not sell personal information. We do not use field data for advertising.

4. Permissions

Location (when in use). Used only when a field user taps to capture GPS for an entry. Camera. Used to take initial and after-installation photos. Photo library. Used to attach existing images to an entry. Internet. Used to sign in and sync entries, users, and photos with the organisation’s server. Users can deny or withdraw permissions in device settings. Features that depend on a permission (GPS capture or photos) will not work without it.

5. Sharing and third parties

Data is shared within your organisation according to role: admins can view entries, photos, and user accounts; field staff see work assigned to them. The mobile app may open Google Maps (or another maps app) when a user chooses to view a job location. That app is operated by its own provider and is subject to their privacy policy. Photos and entry data are uploaded to the API host configured for your environment. That host is operated for your organisation. We do not send field data to unrelated advertising or social platforms.

6. Storage and security

On the mobile app, session tokens are stored in the device’s secure storage. In this admin portal, a session cookie is used after login. Account credentials and field records are stored on the organisation’s server. Passwords are hashed. Access is limited to authenticated users with assigned roles. No method of transmission or storage is completely secure. We take reasonable measures to protect data in transit (HTTPS in production) and at rest on the server.

7. Retention

Account and field-entry data are retained for as long as needed to manage installations, audits, and organisational records, or until an administrator deletes them according to your organisation’s policy. Signing out removes the session from the device or browser. It does not delete server-side entries or the user account.

8. Your choices and rights

Field users can update name and phone number from the Profile tab in the mobile app. Email is part of the account identifier. Administrators can change user roles in this portal. To correct or delete an account or field records, contact your SignGraf administrator. Depending on applicable law, you may also have rights to access, correct, or request deletion of personal data held by your organisation.

9. Children

SignGraf is a workplace tool. It is not directed at children and should not be used by anyone under 16.

10. Changes

We may update this policy when data practices change. The effective date at the top of this page will be revised when that happens. Continued use of SignGraf after an update means you acknowledge the revised policy.

11. Contact

Questions about this policy or a request relating to personal data should be directed to your SignGraf administrator, or to the organisation that provided you access to the app.