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
| What | Whose | Why |
|---|---|---|
| Name, email address, job title; a mobile number if the person adds one for SMS or WhatsApp notices | Users | Signing in, notifications, showing who did what |
| Password, stored only as a salted scrypt hash; sign-in sessions | Users | Signing in securely |
| Project records the users type or upload: letters, RFIs, drawings, reports, snags, orders, payment certificates and their attachments | Customer | The service itself |
| Site photos (they may show people); a GPS position on a daily report when the engineer taps "Tag GPS location" | Customer, site staff | Evidence of site progress |
| Drawn signatures given with approvals and site reports | Users | Showing 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 activity | The customer's and subcontractors' workers | Labour planning, productivity and hours sent to the customer's SAP |
| Supplier names, contacts and weekly prices | Suppliers | Procurement |
| The history of every record and an audit log: who did what and when | Users | Accountability, required for approvals |
| Server logs: time, address requested, IP address, response. No passwords, cookies or link tokens. | Anyone using the site | Security and fault finding |
Cookies and browser storage
- One cookie,
sf_session, keeps you signed in: not readable by scripts, sent only to SiteForce, ends after 14 days and after 3 days without use. - The browser also keeps your language, light or dark theme, favourites, screen layout, your saved drawn signature and, in the field app, a copy of your work so it keeps working without signal. This stays on your device.
- No advertising, no analytics and no tracking cookies. Nothing is sold or shared for marketing.
Who else handles the data (sub-processors)
| Service | What it receives | Provider and location |
|---|---|---|
| Hosting (the server and database) | Everything above | [provider, country / region] |
| Encrypted backups | Everything above, encrypted before it leaves the server; the key is not on the server | [storage provider, region] |
| Email sending | Recipient's address, the notice, and the document PDF when the customer turns that on | [email provider] |
| SMS, only if the customer turns it on | Mobile number and the short notice | Twilio [region] |
| WhatsApp, only if the customer turns it on | Mobile number and the short notice | Meta (WhatsApp Business) [region] |
How it is protected
- Encrypted connections only (HTTPS); each company's data is kept apart inside the database, and a company can never read another's.
- Each user sees only the projects and actions their administrator gave them; documents keep a full history.
- Nightly encrypted backups. [Access by our staff: who, when, and how it is logged.]
How long it is kept
- While the customer's account is active, records are kept until the customer deletes them.
- Backups: one a day for 14 days, one a week for 8 weeks, one a month for 12 months. A deleted record therefore remains in backups for up to about a year.
- Server logs are overwritten as they grow (about 50 MB per part of the system).
- [After the contract ends: data returned within N days, then deleted; backups expire on the schedule above.]
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]