HC Tender Control privacy and data

Controller and roles

The controller is HAZARDS CONTROL sp. z o.o., ul. Miła 8/13, 00-174 Warszawa, KRS 0001221457, NIP 5253077691. Contact: sforowicz@hazardscontrol.pl.

Before launch, the parties establish controller/processor roles and enter a data processing agreement where required.

Exactly what Google data is accessed

`https://www.googleapis.com/auth/userinfo.email`: the signed-in Google Account email address. The app does not read the mailbox or contacts.

`https://www.googleapis.com/auth/spreadsheets`: cell values, sheet names and structure of the Google Sheet configured as the database for the relevant deployment. The scope technically permits access to the user's spreadsheets, but the application code addresses only the database ID assigned to that customer.

`https://www.googleapis.com/auth/drive.file`: the name, identifier, type and content of attachments and backups created by the application or explicitly shared with it. The application does not scan the rest of the user's Drive.

`https://www.googleapis.com/auth/script.send_mail`: permission to send a message prepared by the application from the user's account. This covers recipient address, subject and invitation or reminder body; it does not allow the application to read the mailbox.

How the application uses Google data

The email address identifies the user, checks the authorised-user list and assigns the ADMIN or USER role.

Sheets data is used to display, add and update tender procedures, deadlines, tasks, stages and the authorised-user list. Changes made in the app are saved to the customer's configured database.

Drive data is used to add, open and remove attachments linked to procedures and to create rotating backups.

Mail permission is used only after an in-app operation: inviting a new user or sending an operational reminder. The application does not send marketing messages.

Why the Sheets scope is used

HC Tender Control operates on a fixed customer database configured in advance and must read and write its cells without asking the user to select that file on every session. The backend runs in Google Apps Script and uses SpreadsheetApp, which requires the `spreadsheets` scope to open the configured spreadsheet by ID.

The `drive.file` scope is already used for attachments and backups, but it does not replace the permission required by SpreadsheetApp for cell operations. Actual use of the broader scope is limited by the application to the single database spreadsheet assigned to the deployment.

Who may receive or access the data

Work data is visible to approved users within the same customer organisation according to their roles. The customer's administrator decides who receives access.

Google processes data as the provider of Google Account, OAuth, Apps Script, Sheets and Drive. Authorised Hazards Control personnel may receive only the access necessary for implementation, diagnostics or support agreed with the customer and are bound by confidentiality.

We do not sell Google data, disclose it to advertisers or data brokers, or use it for advertising profiles. Data may be disclosed to public authorities only where legally required.

Protection of sensitive data

Sign-in uses OAuth 2.0 Authorization Code with PKCE in the system browser. The user's Google password is never provided to the application.

The OAuth token is locally encrypted through Electron safeStorage. Logout revokes the Google token and deletes the local token file. Communication with Google services uses encrypted HTTPS/TLS connections.

Access is limited by the approved-email list, ADMIN/USER roles and Google resource permissions. Customer data remains in the configured customer Sheets and Drive; backups are stored in a designated folder.

Personnel access is limited to people who need it for implementation or support. Security incidents are investigated, access can be revoked, and the data owner is notified as required by law and contract.

Local storage and retention

Local storage may contain read-only offline cache, current email, UI preferences, search history and notification state.

Records use configured Sheets; files and rotating A/B backups use Drive; technical version state may use Apps Script Properties/Cache.

Data is retained for the service period and then according to the contract, controller instructions and legal duties. The customer controls data stored in its Google Account.

Limited Use and AI/ML

Use of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

Data obtained from Google Workspace APIs is not used to develop, improve or train generalised artificial-intelligence or machine-learning models.

Revoke access

Google Account → Security → Connections to third-party apps and services → HC Tender Control → Remove connections; then log out in the app.

Revocation does not automatically delete company data in Sheets/Drive or cache on other devices.

Delete data

Send a request from your business address to sforowicz@hazardscontrol.pl, identifying the organisation, account and scope. Hazards Control will verify identity and coordinate deletion from the configuration, Sheet, Drive files/backups and device cache.

Requests are handled without undue delay, normally within 30 days, subject to legal obligations, agreed retention and the technical backup cycle.

Limitations

Desktop offline cache is read-only; editing requires internet. Android requires a connection.

Users protect their account/device and remain responsible for professional control of deadlines and documents. The system does not submit bids.

Contact

App support and privacy: sforowicz@hazardscontrol.pl.