Effective date: July 22, 2026
Application: AJAZZ AKP05E Pro Companion
Developer: Nikita Likhachev
This Privacy Policy explains how AJAZZ AKP05E Pro Companion (the Application) accesses, uses, stores, and protects information obtained through Google APIs.
The Application is an open-source desktop utility that runs locally on the user’s Windows computer. Its optional Google Calendar integration reads the next event from the user’s primary calendar and displays its title and start time on an AJAZZ AKP05E Pro device.
The Application has no developer-operated server or database. Google Calendar data and OAuth credentials are not transmitted to the developer.
The Application requests only this Google OAuth scope:
https://www.googleapis.com/auth/calendar.events.readonly
This read-only scope permits the Application to retrieve calendar events. The Application requests one next upcoming event from the user’s primary calendar and uses only:
The Application does not create, edit, delete, accept, or decline calendar events. It does not use event descriptions, locations, attendees, attachments, or conference information.
The accessed information is used solely to render a next-event card on the user’s locally connected AJAZZ device. It is not used for advertising, profiling, analytics, credit decisions, or training artificial intelligence models.
The Application’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
OAuth and Calendar requests are made directly between the user’s computer and Google’s OAuth and Calendar API endpoints over HTTPS.
The Application stores the following files under %LOCALAPPDATA%\AjazzCompanion:
google-oauth-client.json — the Google Desktop OAuth client configuration supplied by the user;google-calendar-token.dat — the OAuth access and refresh token encrypted with Windows Data Protection API (DPAPI) and bound to the current Windows user account.claude-usage-cache.json — optional non-Google dashboard state containing only Claude rate-limit percentages, reset timestamps, and retry time; it contains no Google data, credentials, prompts, or conversation content.The next event is cached only in process memory for approximately two minutes to avoid unnecessary API requests. Event contents are not written to disk and are discarded when replaced or when the Application exits.
For its separate, non-Google limits card, the Application may read %APPDATA%\Claude\plan-usage-history.json. That file supplies only timestamped plan-usage percentages to this integration; the Application does not read Claude conversation contents and does not copy the organization identifier into its own cache.
The encrypted OAuth token remains on the computer until the user removes the local application data or revokes access through their Google Account.
The developer does not receive, sell, rent, share, or disclose Google user data. The Application has no advertising SDKs, analytics services, or developer-operated backend.
Information is sent to Google only as required to authorize access, refresh an access token, and retrieve the next calendar event. The resulting card is sent locally to the connected AJAZZ device through Stream Dock. This integration does not transmit Google Calendar information over the network to AJAZZ, Key123, Anthropic, OpenAI, Open-Meteo, or any other service.
The Application does not write OAuth credentials, Google API response bodies, or calendar event contents to its logs. Error states shown on the device contain only generic diagnostic messages.
The OAuth authorization flow uses PKCE, a random state value, and a temporary loopback redirect on the user’s computer. OAuth tokens are protected at rest using Windows DPAPI. Network requests to Google use HTTPS.
No method of storage or transmission is completely secure, but the Application limits access to the minimum read-only scope and avoids persistent storage of calendar event contents.
Google Calendar integration is optional. A user can stop access and delete locally stored Google data at any time by:
%LOCALAPPDATA%\AjazzCompanion directory from their Windows account.Revoking access invalidates the Google authorization grant. Deleting the local directory removes the OAuth client configuration and encrypted token stored by the Application. The user may also remove the plugin from Stream Dock AJAZZ.
For deletion assistance, contact the developer using the details below. Because the Application has no developer-operated backend, the developer does not hold a server-side copy of the user’s Google data to delete.
The Application is a general-purpose desktop productivity utility and is not directed to children under 13. The developer does not knowingly collect personal information from children.
This policy may be updated if the Application’s data practices or Google API integration change. Material changes will be published on this page and the effective date will be updated. The repository history provides a public record of revisions.
Questions or requests concerning this Privacy Policy can be sent to: