1. Information handled by the application
Authorized users provide company, customer and staff information, contact details, transaction references, business schedules, payment and balance information, expenses, remarks and supporting records. The application also maintains account permissions, operational logs and audit information needed to operate and support these features.
When an organizer connects Google, we access the verified Google account email and account identifier to associate the authorization with the intended organizer. We receive authorization credentials that allow background access to the approved calendar features.
2. Google Calendar access and use
The application requests Google account identity permissions and permission to manage calendar events. It uses them to verify the organizer, read and compare relevant calendar events, create business events, update dates, amounts, descriptions and recipients, and remove managed events when requested or required by saved settings.
Event data may include the record reference, customer and assigned staff names, scheduled period and date, amount information, remarks, recipient email addresses and attendee response information. Calendar event identifiers, synchronization state and related metadata are stored to match records to their events and recover interrupted work.
Google data is used to provide, maintain and support these user-facing calendar features. We do not sell Google user data, use it for advertising, or use it to train generalized artificial intelligence or machine learning models.
GWC888's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
3. Sharing and access
Calendar event content is sent to Google and shared with the recipients selected for that record. Authorized company users may view the information allowed by their application permissions. Administrators may include a designated test recipient when investigating invitation delivery; that recipient receives the same event details.
Service operation may involve the hosting and infrastructure providers used to run the application. Support or administrative access is limited to operating, securing and supporting the service. Any access to Google user data must follow Google's Limited Use requirements, including applicable restrictions on human access. Information may also be disclosed when required by applicable law or needed to address security incidents.
4. Storage and protection
Accounting records, calendar mappings and operational information are held in the application's databases and related server storage. Google refresh credentials and protected calendar configuration secrets are encrypted before database storage. Access to accounting and calendar administration features is controlled by application permissions.
The service uses session and authentication mechanisms to support sign-in, preferences and access controls. Operational logging supports troubleshooting and audit. No security measure guarantees absolute protection; report suspected unauthorized access promptly using the contact below.
5. Retention and deletion requests
Information is retained as needed for the configured service, company accounting records, operational support and audit purposes. Some removal actions use soft deletion, so historical records and event mappings may remain for recovery or audit rather than being immediately erased.
To request access, correction or deletion of your information or stored Google authorization, contact your company administrator or [email protected]. We may need to verify your identity and authority over the records. Requests are assessed against the records involved, applicable obligations and the need to preserve authorized business records; deleting Google authorization and deleting accounting records are separate actions.
6. Pausing synchronization and revoking Google access
You can ask an authorized administrator to pause synchronization, change recipients or remove managed events using the application's calendar controls. Pausing retains existing events and the authorization needed for cleanup; it does not revoke Google access.
The organizer can revoke the application's access through Google Account connections. Revocation prevents further authorized synchronization. It does not automatically erase accounting records or events already shared with Google and recipients. If events should be removed, request their removal before revoking access or manage them in Google Calendar.
7. Contact and policy changes
Contact GWC888 application support at [email protected] for privacy, deletion or Google data questions. This page will be updated when data practices change. Where a change requires additional Google authorization or user notice, that authorization or notice will be obtained before the new use.