1. Scope and contact
This policy covers Nessara Office, the private job-administration application used by Nessara Construction. The public construction website may collect project-request details separately when a visitor submits its contact form.
Questions, access requests, deletion requests, or requests to remove a Google connection can be sent to [email protected].
2. Google data the app accesses
Account and authorization data
When the Office owner approves Google access, the app receives OAuth credentials, the approved scope set, and the connected Gmail address. Google handles the password and consent process; Nessara Office does not receive the Google password.
Gmail sending
For an Office email, the app sends Google the sender address, recipient address, subject, plain-text message body, and message identifier. Google returns provider message and thread identifiers used to record delivery and correlate a later reply.
Gmail reply metadata
The app establishes a forward-only Gmail history cursor and processes metadata for newly added messages. That metadata can include the mailbox profile and history identifier; message and thread identifiers; labels; and the From, To, Subject, Message-ID, In-Reply-To, and References headers.
The app does not request or store reply bodies or attachments. It retains an inbound reply record only when the Gmail thread exactly matches an estimate or invoice message sent by Office. That record contains the subject, Google message and thread identifiers, associated Office record, and detected time. Metadata for unmatched messages is not retained in the Office database.
Google Calendar events
The app writes assignment events to the connected user’s owned primary calendar. Event details can include the job and customer name, job location, assignment start and end, status, subcontractor name, arrival information, scope summary, and an optional subcontractor attendee email.
Before changing or deleting an Office-created event, the app reads that exact event’s identifier, status, version tag, private Office marker, organizer data, and attendee data. It does not list or retain unrelated calendar events.
3. How Google data is used
- Send project messages and configured follow-ups chosen by an authorized Office user.
- Confirm delivery receipts, prevent unsafe duplicate sends, and associate a customer reply with the correct Office estimate or invoice.
- Stop an applicable follow-up sequence when a matching reply is detected.
- Create, update, or remove Office assignment events on the owned primary calendar.
- Verify that the OAuth token belongs to the single Google account configured for the application and includes only the approved permissions.
Google user data is not used for advertising, audience profiling, sale of data, or training a general-purpose artificial-intelligence or machine-learning model.
4. Storage and security
OAuth credentials are stored in a server-side token file with operating-system permissions restricted to the application service. They are not stored in the visitor’s browser. Office operational records are stored in the application’s private database and are available only through authenticated Office access and authorized operations.
Stored operational data can include sent email subjects and bodies, recipients, Google message and thread identifiers, matched reply subjects and identifiers, Gmail history cursors, and Calendar event identifiers, version tags, attendee state, and synchronization state. Reply bodies and unmatched Gmail message metadata are not stored by Office.
No internet-connected service can eliminate every security risk. Nessara Construction limits the Google account, OAuth scope set, application access, and stored provider receipts to what the current workflow needs.
6. Retention and deletion
The local OAuth token is retained until the connection is replaced or the token is removed from the Office server. Google may invalidate the credential or the account owner may revoke access sooner; either action prevents the stored credential from authorizing new Google API access. Sent-message records, matched-reply metadata, Calendar receipts, and related Office records are retained while needed for project administration, delivery safety, and Nessara Construction’s business records.
Nessara Office does not currently apply a fixed automatic deletion schedule to those operational records. A request to remove the local Google token or delete associated Google-derived records can be sent to the contact above. Nessara Construction will evaluate the request against operational, security, and recordkeeping needs and confirm what can be removed.
7. Choices and revocation
The authorized account owner can decline the Google connection or revoke it from the Google Account third-party connections page. Revocation stops new API access but does not by itself delete Office records already retained or an event or message already delivered through Google.
To request local token removal, deletion of eligible stored records, or an operator change that disables Calendar synchronization, email [email protected]. A subcontractor is added as an event attendee only when the Office owner selects that option for the individual assignment.
8. Changes to this policy
This page will be updated if Nessara Office changes how it accesses, uses, stores, or shares Google user data. The date above identifies the current version. Material new uses of Google data will not be introduced without an updated disclosure and any consent required by Google or applicable law.