1. Scope
This policy describes how Prace Launcher processes data when the Google integration is used with Google Sheets, Gmail, Google Calendar, Google Contacts, Google Drive, and Google Apps Script.
Contact: vlnkasoft.dev@gmail.com
2. Purpose of the integration
Prace Launcher uses Google services to support technician scheduling and field-work operations.
- read planning emails from Gmail
- import schedule data into Google Sheets
- create or update calendar events for technician visits
- create, update, and archive customer or technician contacts
- complete the Google setup flow used by the desktop launcher
3. Google services that may be accessed
- Google Sheets
- Gmail
- Google Calendar
- Google Contacts / People API
- Google Drive
- Google Apps Script
4. Data categories that may be processed
- Google account email address used during authorization
- technician name, phone number, and work email address
- customer names, phone numbers, and addresses
- visit dates and time windows
- planning information contained in work-plan emails
- Google Sheet identifiers, runtime metadata, and calendar identifiers
5. How data is used
Google data is used only for the technician workflow and related setup selected by the user or administrator.
- Gmail message data is used to import work-plan information into a Google Sheet
- calendar data is used to create or update technician visit events
- contact data is used to create or update customer and technician contacts
- sheet and runtime metadata are used to connect the desktop launcher to the correct Google runtime
6. Data sharing
Prace Launcher does not use Google data for advertising or unrelated profiling.
Google data may be shared only with the parties and systems required to operate the workflow:
- the authorized technician Google account
- the operator or administrator account that prepared the sheet
- the local bridge service-account flow, if enabled, for desktop-side sheet access
7. Storage and retention
Google-related data may remain in the technician Google Sheet, Google Calendar, Google Contacts, local PC configuration, and local logs generated by the launcher.
Retention depends on the feature. Some data remains until deleted by the user or operator, and contact archive behavior can be configured through the launcher automation settings.
8. User choices and controls
- choose whether to complete Google authorization
- disable calendar writes where supported
- disable contact writes where supported
- stop use of the integration
- revoke Google access from the relevant Google account
- delete or unshare the relevant Google Sheet
9. Security
Prace Launcher aims to limit access to the minimum needed for the workflow. Operational safeguards can include technician-owned Google authorization for runtime behavior, runtime tokens for desktop-to-web-app calls, limited sheet sharing, and keeping service-account keys out of source control.
10. Contact
For questions, access requests, or deletion requests related to the Google integration, contact: