Legal
Data Processing Addendum
Version 5. Effective date: 11 November 2026. Last updated: 11 November 2026. For a Customer that accepted an earlier version, the changes in this version take effect 30 days after we tell its office users (section 13.3).
Changes from version 4
1. Where data is kept: one of our founders also keeps an encrypted copy of our backups, including the photos and files stored in Sightgrid, on the computer that founder works from in British Columbia, Canada. Added to section 5.1, 11.1, 11.3 and Schedule 1.
2. References updated to the Terms of Service and Privacy Policy effective 11 November 2026.
3. Schedule 1: Sightgrid sends no texts or emails to the Customer's customers for Office. We may email the Customer's office about Office, for example to confirm an Office trial. Section 5.1 now refers to 5.4 for notice of a new provider.
4. Schedule 1: the backup key is said to be kept apart from the backups only for the copy in the United States.
This addendum
Version 5, 11 November 2026. Effective 11 November 2026. Replaces version 4 (effective 29 October 2026, corrected 9 November 2026).
This Data Processing Addendum (the "DPA") is part of the agreement between Sightgrid Technologies, Inc., an Oklahoma corporation, of 9909 N 118th E Ave, Owasso, Oklahoma 74055, United States ("Sightgrid", "we", "us"), and the Customer under the Sightgrid Terms of Service effective 11 November 2026 (the "Terms"). It applies to personal information in Customer Data whether or not it is signed (Terms 1.2). Words with capitals that are not defined here have the meaning in the Terms.
In plain words. Your company decides what personal information goes into Sightgrid. We handle it only to run Sightgrid for you, on your instructions. We don't sell it, don't use it for anything else, and our AI and speech-to-text providers don't train on it. We tell you at least 30 days before a new provider handles it. We tell you within 72 hours if we confirm a breach that affects it. When you leave, you can export it for 30 days, and then we delete it. Recaps serve only your job record, and their recordings are deleted after the days you set. Crew hours in Office are your records about your own workers.
1. Definitions
- "Customer Personal Data" means personal information in Customer Data that we process for the Customer under the Agreement.
- "Data Protection Laws" means the privacy and data protection laws that apply to the processing of Customer Personal Data. These may include Canada's Personal Information Protection and Electronic Documents Act (PIPEDA), British Columbia's Personal Information Protection Act (PIPA), US state privacy laws such as the California Consumer Privacy Act as amended (CCPA), Taiwan's Personal Data Protection Act, and, where they apply, the EU and UK General Data Protection Regulations.
- "Subprocessor" means a third party we engage that processes Customer Personal Data.
- "Security Incident" means a confirmed breach of security leading to accidental or unlawful destruction, loss, alteration, or unauthorized disclosure of or access to, Customer Personal Data.
- "Personal information" includes "personal data" and "personal information" as Data Protection Laws define them. "Processor" includes "service provider" and "contractor" as US state laws use them.
2. Roles
2.1 The Customer decides; we act for it. For Customer Personal Data, the Customer (or, on a shared Job, each company for what it contributes) decides what is collected and why. We act as its processor and service provider (Terms 13.3; Privacy 3.1). We process Customer Personal Data only on its documented instructions. The Agreement, the Customer's settings and its use of the Service are its instructions. Under Canadian law the Customer remains accountable for it (Privacy 3.1).
2.2 What we decide ourselves. This DPA does not cover information we handle for our own purposes: account and sign-in details, billing, security and rate-limit records, help requests, feedback and surveys, AI usage records, website visits, field test requests, sales contacts and signed agreements with us. The Privacy Policy covers those (Privacy 3.2).
2.3 The Customer's duties. The Customer is responsible for having a lawful basis, and for giving the notices and getting the consents the law requires, for the personal information it and its Authorized Users put into the Service (Privacy 12.8). This includes photos of people on site, voice notes, and the personal information of a restoration company's callers, property owners, tenants and adjusters (Privacy 4.11). For Recap & Confirm, the Customer makes sure its people record only their own voice and send recaps only to people they deal with on the Job (Terms 17.1B). For Office, the Customer is responsible for telling its workers that their time on a loss is recorded, and for any notice the law where they work requires (Terms 17A.8). The customer names, phone numbers and addresses in its customer updates are its Customer Personal Data (Privacy 6C.2).
2.4 Instructions we cannot follow. We will tell the Customer if we believe an instruction breaks Data Protection Laws, and we may decline to follow it.
2.5 Learning, only with a yes. De-identifying Customer Data under the Help improve Sightgrid setting happens only while the Customer's office has it on, as Terms 13.8 and Privacy 6A say. The result identifies no one and is not Customer Personal Data (Privacy 3.4).
3. What we process
Purpose: To provide, secure, support and maintain the Service for the Customer, as the Agreement describes (Terms 13.2)
Kinds of data: all products: Names, work email addresses and phone numbers, roles, trades and companies; photos; voice notes; chat messages and files; issue, clash and sign-off records with who did what and when; supplier representatives' names and contact details; email addresses that view-only links are sent to; personal information that happens to be in models, drawings or documents (Privacy 4.2)
Kinds of data: Sightgrid Restoration: For each loss: the caller's name and phone number, the property address, the type and date of the loss, the insurer and claim number, and the adjuster's name and contact details. Moisture and air readings, drying logs, equipment records and room-by-room scans, each with the name of the person who recorded it and when. Day records signed with a full name and drawn signature. Work authorizations and certificates of satisfaction signed by the company's customer: the name they give, their drawn signature, the time, the signed form, the browser details used to sign, and their IP address when they sign through a link. Meter photos with the number read, the AI model and how sure it was. Voice recordings, the text made from them and the AI's draft. Read-only record links, who they were sent to, and when they were first and last opened. Uploaded documents in the job record (for example subcontractor and communication files) (Privacy 4.4, 4.11, 6.1A, 6.1B)
Kinds of data: Recap & Confirm (all products): A person's recording of their own voice, or their typed words; the text made from it; each version of the summary with who changed it, when and why; who made it, the job and item, and when the talk took place; who it is for (a person or company on the Job, or someone outside the Job by name and email address or phone number, shown masked; links and email stop requests keep only a one-way hash of the address); each answer with the version answered, and either the name and company of the person who answered in the app (for a confirmation from an account with no name of its own, the name typed and signature drawn), or, for an answer through a link, the name typed and signature drawn for a confirmation (the signature where the page asks for one), the masked address, a keyed hash of the network address and the browser type; SHA-256 fingerprints; and the recap's history (Privacy 4.12, 4.13, 6B)
Kinds of data: Office (Sightgrid Restoration add-on): Visits on the schedule with the person, loss, time, kind and note; crew time on each loss (on site and leaving times, office entries and corrections with reasons, and an after-hours flag; no location and no pay rates), which is personal information about the Customer's workers; the equipment fleet with rental details; loss stages with who moved them; billing files (counts of unit days, crew hours by person and day, signed days and the Work Authorization signer, with no prices); customer updates the office says it sent, including the customer's name and the property address; and the customer's read-only loss link, kept only as a hash (Privacy 4.14, 6C)
Whose data: The Customer's people; people invited from other companies; supplier representatives; a restoration company's callers, property owners, tenants and adjusters; the Customer's workers whose time on a loss is recorded; people a recap is sent to, who may not be Sightgrid users; people who appear in photos, voice notes, recaps or documents
Sensitive data: None is intended. Terms 18.2 asks the Customer not to put sensitive personal information into the Service unless the Job needs it and it is lawful, and never into an AI feature. We never create a voiceprint or use a voice to identify anyone, including in recaps (Privacy 4.10)
How long: For the term of the Agreement, then until deleted under section 10. Retention of particular items is in the table in section 10.4
3A. Providers that handle only our own records
These are not Subprocessors, because they do not process Customer Personal Data. We list them so the Customer can see every provider (Privacy 8.1 to 8.3):
Stripe, Inc. What it does: Payments, subscriptions, invoices and sales tax. What it handles: Billing contact, address, tax ID, payment details (Privacy 4.6)
Kaplex Industries Inc. (Kaplex Sign), a British Columbia company owned by one of our founders. What it does: Electronic signing of agreements between the Customer and us. What it handles: Signing records (Privacy 4.8). Company in Canada; hosting in the United States.
Telegram. What it does: Tells our founders that something is waiting in our internal system. What it handles: A fixed notice and a link. No personal information.
Google LLC (Google Fonts). What it does: Fonts on the website. What it handles: IP address and browser details of website visitors.
A restoration company's own customers sign work authorizations and certificates of satisfaction inside the Sightgrid app, not through Kaplex Sign. Those signatures are Customer Personal Data (section 3).
4. Our people
Only our founders and staff who need access to run the Service have it. Each is bound by a duty of confidentiality. Our founders do not open a Customer's models, photos, voice notes, recaps or chat unless the Customer asks or agrees, or it is needed to stop a security threat, fix a serious fault, or comply with law (Privacy 7.6).
5. Subprocessors
5.1 Our current Subprocessors. The Customer authorizes us to use these Subprocessors:
Vercel, Inc. What it does: Hosts the app and its server functions. Stores files in a private Vercel Blob store (models, drawings, photos, meter photos, voice recordings, recap recordings, chat files, signed forms, exports, quotes and price files). Holds our nightly encrypted database backups in a separate private Blob store. Customer Personal Data it processes: All app traffic and stored files; request logs including IP addresses; encrypted backups. Where: United States. Server functions: San Francisco (Vercel region sfo1). Customer files: Portland, Oregon (pdx1). Nightly backups: Washington, D.C. (iad1). Requests pass through Vercel's global edge network.
Supabase, Inc. What it does: Hosts the app's Postgres database. Customer Personal Data it processes: All Customer Data records other than stored files. Where: United States: Northern California (AWS us-west-1)
Anthropic, PBC. What it does: The AI behind "Ask it in words" and spreadsheet column matching; reading meter photos; sorting the text of voice notes into fields; drafting recap summaries. Customer Personal Data it processes: Only what Privacy 4.4, 6.1A, 6.1B and 6B.6 describe: the words a person types or says into Ask it in words, pasted lines, or column headings with up to three sample rows (price cells removed); a meter photo with location and hidden data removed, with no names, addresses or job details; a voice note's text with the job's rooms and where they are, its reading points with materials and units, and its equipment by type, asset number or name, and room; a recap's text with the company's language, the date, the job's name, the item's label, and the names and companies of the people on the Job. Apart from what a person says in a recap and a job's name (which can be an address), never customer names or addresses, models, drawings, chat or other Job records (Privacy 6.2). Where: United States.
OpenAI, L.L.C. What it does: Turns Sightgrid Restoration voice-note recordings, and recap recordings, into text. Customer Personal Data it processes: The recording; as spelling hints, for voice notes the names of the job's rooms, and for recaps the job's name and the names of the people on the Job. A customer's name or address is never added to a voice note's hints. Where: United States.
Resend, Inc. What it does: Sends the Service's emails (sign-in links, invitations, alerts, view-only links, change notes, recaps sent to people outside a Job and their one reminder). Customer Personal Data it processes: Recipient's name and email address and the email's content. Where: United States.
Functional Software, Inc. (Sentry). What it does: Error monitoring. Customer Personal Data it processes: Error messages and technical details. Set not to collect personal information by default, with no screen recording, and with invite links, issue links and signed file addresses removed. An error message can occasionally contain a fragment of data that was on screen. Where: United States.
The person's browser push service (for example Google for Chrome and Android, Apple for Safari and iPhone, Mozilla for Firefox). What it does: Delivers phone notifications the person turned on. Customer Personal Data it processes: The device's push address and the alert, sent encrypted. Where: The push service's own locations.
No text message provider is connected. We will add one to this list, with notice under 5.4, before any text message is sent (Privacy 8.1).
Our own copy in Canada is not kept by a Subprocessor (section 11.1).
5.2 No training. Under their commercial terms, neither Anthropic nor OpenAI trains its models on what we send. Each may keep what we send for a limited time under its own terms, for example to detect abuse (Privacy 6.3). We never let a third-party AI provider train on Customer Data (Terms 13.7). Recaps are used only for the Customer's own Job record: never for analytics, never to train any AI, ours or a provider's, and never for learning across companies (Privacy 6B.9).
5.3 Duties we pass on. Each Subprocessor is bound by a written contract or its published terms to protect Customer Personal Data at least as well as this DPA requires, as far as relevant to its service. We remain responsible to the Customer for our Subprocessors' performance.
5.4 Notice of changes. We keep the current list in the Privacy Policy at getsightgrid.com/privacy (section 8). We will email the Customer's office users at least 30 days before a new Subprocessor starts processing Customer Personal Data, or before an existing one moves it to a new country (Privacy 8.4). In an emergency needed to keep the Service running securely, we tell the Customer as soon as we can.
5.5 Objection. The Customer may object on reasonable data protection grounds within those 30 days. We will discuss it in good faith. If we cannot resolve it, the Customer may end the affected Subscription before the change takes effect, and we refund the prepaid fees for the unused part.
6. Security
6.1 Our measures. We maintain the administrative, technical and physical safeguards in Schedule 1, which suit the nature of Customer Personal Data and the risks of processing it (Terms 22; Privacy 11). We may change them over time, but not in a way that materially lowers the protection of Customer Personal Data.
6.2 The Customer's part. The Customer is responsible for its settings, for who it invites, for removing people who leave and signing out lost devices, and for the security of its people's devices (Terms 4.3 and 22). Data on a device stays there until it is deleted (Terms 4.5).
7. Security Incidents
7.1 Notice. We will notify the Customer's office users by email without undue delay, and in any case within 72 hours after we confirm a Security Incident affecting the Customer's Customer Personal Data.
7.2 What we tell you. What happened, the data and people likely affected, what we have done and will do, and a contact person. If we don't know everything at first, we send what we know and update as we learn more.
7.3 Help. We take reasonable steps to contain the incident and limit its harm. We give the Customer the information it reasonably needs to assess it and to meet its own duties to notify regulators and individuals. In Canada, that includes what the Customer needs to decide whether the breach creates a real risk of significant harm and to keep its record of breaches under PIPEDA (Privacy 12.4).
7.4 Our own records. We keep a record of every breach of security safeguards involving personal information (Privacy 12.4).
7.5 Not an admission. A notice under this section is not an admission of fault.
8. Helping the Customer
8.1 People's requests. If someone asks us to access, correct or delete Customer Personal Data, we pass the request to the Customer and do not answer it ourselves unless the law requires or the Customer asks us to (Privacy 12.2). The Service lets the Customer view, export, correct and delete Customer Data itself. Some Restoration records cannot be edited while the Job exists, because they are the Customer's record of who measured, said and signed what (Privacy 12.3). We give other reasonable help with requests the Customer cannot handle in the Service.
8.2 Assessments and regulators. We give reasonable help with the Customer's privacy impact assessments and its dealings with regulators about the Service, to the extent the Customer cannot do it from what we publish.
8.3 Legal demands. If a court or authority demands Customer Personal Data from us, we refer it to the Customer where we can, tell the Customer promptly unless the law forbids it, and disclose only what we are legally required to disclose (Privacy 7.8).
9. Information and audits
9.1 Information. We answer the Customer's reasonable written security and privacy questionnaire once a year, and give the information reasonably needed to show that we meet this DPA.
9.2 Audits. If 9.1 is not enough because a regulator requires an audit, or after a Security Incident, the Customer (or an independent auditor bound by confidentiality, who is not our competitor) may audit our compliance with this DPA. No more than once a year, with at least 30 days' written notice, during business hours, without access to other customers' data, and at the Customer's cost. Audits of our Subprocessors are by means of the reports and certifications they make available.
10. Deletion, export and retention
10.1 Export. While the Customer has access, its office users can export any Job it hosts (Terms 13.9). For 30 days after a paid plan, a Restoration trial or the Agreement ends (the Export Window), they can still open and download every Job it hosts (Terms 12.2A and 31.1).
10.2 Deletion. After the Export Window, we delete the Customer's Jobs, their files and its people from our live systems (Terms 31.2). The Customer may ask in writing for earlier deletion.
10.3 Backups. Deleted data can remain in a backup until that backup is deleted on its normal cycle: at most about 8 weeks for our own backups (Terms 31.3; Privacy 10). Our database provider's own backups roll over on its schedule. We restore from a backup only to recover from a failure.
10.4 Retention of particular items (Privacy 6.4 and 10):
A Job the Customer deletes. How long: Restorable for 30 days, then deleted for good.
Voice-note recordings (Restoration). How long: 30 days after recording, or the number of days the Customer's office sets (1 to 365); at once if the note is discarded. The text and confirmed lines stay with the Job.
Meter photos and readings. How long: With the Job, as evidence of the reading.
Signed forms and their signing records. How long: With the Job. Signing links work once and for 7 days; the signer's download page works for 7 days after signing.
Read-only record links. How long: 30 or 90 days, as the Customer chooses, or until it cancels them.
Recap recordings. How long: Deleted after the number of days the Customer's office sets (7 unless it changes it; 1 to 365). If the other side disputes the recap, kept until the recap is deleted. Deleted at once when the recap is deleted.
Recap text, summaries, answers and history. How long: With the Job. A deleted recap is hidden and its history stays with the Job; the address typed for someone outside the Job is cleared.
Recap links. How long: 14 days.
Requests to stop recap emails. How long: Until the Customer's company is deleted.
Office records. How long: With the Job, including after Office ends.
A customer's read-only loss link (Office). How long: 30 days, or until the office stops it or makes a new one.
Data on devices. How long: Until the person deletes it or clears the app's data.
10.5 What we may keep. What the law requires, under the confidentiality and security duties of this DPA, for as long as the law requires; billing records under tax law; and figures that identify no one (Terms 31.3).
11. Where data is processed
11.1 Locations. Customer Personal Data is stored in the United States, as section 5.1 shows, apart from the backup copy in Canada below. This includes our own nightly encrypted backups, which are kept in a private Vercel Blob store in Washington, D.C. (Vercel region iad1). One of our founders also keeps an encrypted copy of our backups, including the photos and files stored in Sightgrid, on the computer that founder works from in British Columbia, Canada. Our founders work from the United States and Canada and may access Customer Personal Data from either country when section 4 allows.
11.2 Transfers. The Customer authorizes these transfers. We protect Customer Personal Data in every country by this DPA and by our contracts with Subprocessors. Information stored in another country is subject to that country's laws and may be accessed by its courts, law enforcement and national security authorities under those laws (Privacy 9.2).
11.3 Canada. For Customer Personal Data about people in Canada, we provide a level of protection comparable to that required in Canada while it is processed outside Canada, by contract and by the measures in Schedule 1. We handle it as PIPEDA and, where it applies, BC PIPA require. Our Privacy Officer answers questions about it at hello@getsightgrid.com with "Privacy" in the subject (Privacy 1.2). A Customer in Canada should tell its people and its customers that their information is stored in the United States, with an encrypted backup copy in British Columbia, Canada.
11.4 Taiwan. For Customer Personal Data about people in Taiwan, we comply with any restriction on international transfer issued by Taiwan's competent authority that applies to it (Privacy 9.4).
11.5 Europe and the United Kingdom. We do not currently offer the Service to customers in the European Economic Area, Switzerland or the United Kingdom (Privacy 9.5). If a Customer needs to transfer personal data from there to us, we will first sign the European Commission's Standard Contractual Clauses (with the UK Addendum where needed) with that Customer.
12. US state law terms
Where US state privacy laws apply, we act as a service provider or processor, and we will not:
1. sell or share Customer Personal Data, as the CCPA defines those terms;
2. keep, use or disclose Customer Personal Data for any purpose other than the business purposes in the Agreement, including any commercial purpose other than providing the Service, or outside our direct business relationship with the Customer;
3. combine Customer Personal Data with personal information we receive from others or collect ourselves, except as the law allows a service provider to do.
We comply with the obligations that apply to us under those laws and provide the same level of privacy protection they require. We tell the Customer if we can no longer meet them. The Customer may take reasonable and appropriate steps to stop and remedy any unauthorized use of Customer Personal Data, and to ensure that we use it consistently with the Customer's obligations under those laws. We certify that we understand and will comply with the restrictions in this section.
13. General
13.1 Liability. Each party's liability under this DPA is subject to the limits in section 27 of the Terms.
13.2 Order of precedence. For the processing of personal information, this DPA wins over the Terms and over an Order Form, unless the Order Form says expressly that it changes this DPA (Terms 1.3).
13.3 Changes. We may change this DPA as Terms 25.2 says, with at least 30 days' notice of a material change.
13.4 Duration. This DPA lasts as long as we process Customer Personal Data.
Schedule 1. Security measures
These describe how the Service works today.
Encryption
- All traffic to the app and website uses HTTPS (TLS).
- The connection from our servers to the database is encrypted, and our servers check the database's certificate before sending credentials.
- Our hosting and database providers encrypt stored data at rest under their standard controls.
- Our own backups are encrypted with AES-256-GCM before they are written. For the copy in the United States the key is kept apart from the backups. No backup is written unencrypted: with no key, no backup runs. A backup that was changed or cut short is refused on restore.
Access control
- People sign in with a single-use link sent to their email or by accepting an invitation. Each device then holds a signed session that an office user can revoke. A session ends after 30 days without use and 180 days after sign-in (Privacy 10).
- The server checks the person's live membership of the Job and their role on every read and every write. Restoration actions (taking readings, confirming someone else's voice note, signing a day), recap actions (making, seeing every recap, sending outside the Job, deleting) and Office actions are checked against the company's permission settings. Office is refused for a company that does not have it switched on.
- The database enforces row level security.
- Invite links, view-only issue links, Restoration signing links, recap links and Office loss links are stored only as hashes, and expire. Each signed Restoration form keeps a SHA-256 fingerprint of the exact document version signed.
- Secret keys, including the AI and speech-to-text keys, are kept only on the server. None reaches a browser.
- Only our founders have administrative access to production systems.
Files
- Files are stored in a private store. A device uploads a file directly with a permission limited to one file name, one size, the expected file type and a short time. Downloads use signed addresses that expire within minutes.
- The server checks each stored file's size and first bytes before anything points at it, and deletes what fails.
- Location (GPS), camera data and other hidden data are removed from every photo and image uploaded, including meter photos before they go to the AI provider.
Integrity and monitoring
- The activity log and event history are append-only. Restoration readings are never written over: a correction sits beside the original, with who and why.
- Recap summaries are kept as versions and answers as rows that the database refuses to change; each answer names the version and the SHA-256 of the exact words answered. Each recap's history is hash-chained. A deleted recap is marked, not removed, while its Job exists.
- Office's visits, crew time, stage moves, billing files and customer updates are append-only: a change or correction is a new entry that names the one it replaces. Each billing file is kept exactly as made, with its SHA-256.
- Rate limits per device, per person and per network address. Network addresses used for rate limits are stored only as one-way hashes, and the counters are deleted after a short window.
- Error monitoring is set not to collect personal information by default and records no screens.
Backups and recovery
- Besides our database provider's own backups (Supabase, United States), a nightly job writes an encrypted backup of every database table to a private Vercel Blob store in the United States (region iad1) that is used only for backups and has its own access token. We keep the newest of each of the last 14 days and the newest of each of the last 8 weeks, and delete the rest. A missed or failed night is reported to the founders. One of our founders also keeps an encrypted copy of our backups, including the photos and files stored in Sightgrid, on the computer that founder works from in British Columbia, Canada.
- Customer files (photos, models, recordings) live in their own private store and are not in the nightly backup in the United States. The copy in British Columbia also holds an encrypted copy of those files.
- A restore checks row counts and checksums of the event history and activity log before it completes, and rolls back if anything differs.
Least data
- AI and speech-to-text providers receive only what section 5.1 describes. Nothing an AI reads or hears becomes a reading or note until a person confirms it (Terms 17.1A), and a recap summary goes to the other side only when the person sends it (Terms 17.1B).
- A recap link to someone outside the Job shows only the summary, never the recording or the full text. Recap recordings are played only by the recap's own side, through addresses that expire within minutes, and each play is logged; our founders' support view cannot play them.
- Office sends nothing to AI providers, and Sightgrid sends no texts or emails to the Customer's customers for it. A billing file has no prices; a rental cost the Customer enters stays internal.
- Help screenshots are deleted after 90 days (Privacy 10).
People and process
- Founders do not open a Customer's models, photos, voice notes or chat except as section 4 allows.
- Security reports: hello@getsightgrid.com (Terms 18.2).

