SiteForce terms and privacy

Draft for legal review, not yet in force. The description of what the system does is accurate. The legal wording and everything marked [like this] is to be completed by SiteForce's lawyer. An Arabic version follows the approved English text.

Terms of service

Who we are

SiteForce is provided by [legal name, registration number, address] ("we"). It is used by construction companies ("the customer") and the people they invite (their staff, consultants, clients, subcontractors and suppliers).

The service

SiteForce is a project management system for construction: documents and approvals, site reports, quality, procurement and stores, commercial records and handover, on the web and in the field app. Each customer has its own account; the modules in it are those in the customer's plan.

Your data stays yours

Everything the customer and its users put into SiteForce belongs to the customer. We use it only to run the service for that customer. [Export and return of the data at the end of the contract, and how long after that it is deleted.]

Accounts and users

The customer's administrator invites users and decides what each may see and do. Users keep their sign-in details to themselves; each person has their own login. [Seat limits per plan; responsibility for what users do.]

Acceptable use

[No unlawful content, no attempts to break into other accounts or overload the service, no reselling without agreement.]

Availability and support

[Target availability, planned maintenance windows, support hours and response times (launch checklist A15).]

Fees and payment

[Plans and prices (A12), invoicing and payment terms (A13), trial terms, what happens when an invoice is unpaid.]

Term and ending

[Contract length, renewal, notice, suspension.]

Liability, warranties, law and disputes

[For the lawyer: limits of liability, warranties, governing law and courts or arbitration.]

Privacy policy

Roles

For the project data in an account, the customer decides what is recorded and why (the controller); we process it on the customer's instructions (the processor). For our own dealings with customers (contacts, invoices), we are the controller. [Applicable law(s): e.g. Egypt Personal Data Protection Law 151/2020, UAE / KSA PDPL, GDPR for EU persons: lawyer to confirm.]

What is stored

WhatWhoseWhy
Name, email address, job title; a mobile number if the person adds one for SMS or WhatsApp noticesUsersSigning in, notifications, showing who did what
Password, stored only as a salted scrypt hash; sign-in sessionsUsersSigning in securely
Project records the users type or upload: letters, RFIs, drawings, reports, snags, orders, payment certificates and their attachmentsCustomerThe service itself
Site photos (they may show people); a GPS position on a daily report when the engineer taps "Tag GPS location"Customer, site staffEvidence of site progress
Drawn signatures given with approvals and site reportsUsersShowing who approved, on screen and in printed documents
Workers: name, employer, craft, hourly rate, certifications and their expiry, SAP employee number, hours worked per day and activityThe customer's and subcontractors' workersLabour planning, productivity and hours sent to the customer's SAP
Supplier names, contacts and weekly pricesSuppliersProcurement
The history of every record and an audit log: who did what and whenUsersAccountability, required for approvals
Server logs: time, address requested, IP address, response. No passwords, cookies or link tokens.Anyone using the siteSecurity and fault finding

Cookies and browser storage

Who else handles the data (sub-processors)

ServiceWhat it receivesProvider and location
Hosting (the server and database)Everything above[provider, country / region]
Encrypted backupsEverything above, encrypted before it leaves the server; the key is not on the server[storage provider, region]
Email sendingRecipient's address, the notice, and the document PDF when the customer turns that on[email provider]
SMS, only if the customer turns it onMobile number and the short noticeTwilio [region]
WhatsApp, only if the customer turns it onMobile number and the short noticeMeta (WhatsApp Business) [region]

How it is protected

How long it is kept

Your rights

People whose data is in a customer's account should first ask that customer, who controls it; we help the customer answer. [Rights under the applicable law, how to complain, privacy contact.]

Data processing agreement

Customers that need a data processing agreement can ask for one at [privacy email]. It covers the processing described above, the sub-processors, security measures, breach notification within [N hours], help with people's requests, audits, and the return and deletion of data at the end of the contract. [Lawyer to provide the agreement.]

Contact

[Support email / WhatsApp (A15) and privacy contact, postal address.]

Last updated: [date the approved text takes effect]