Last updated September 4, 2026
Privacy Policy
This policy covers private, personal-use software integrations operated by the owner of chipstar.net. These integrations are not offered as public services. They access connected accounts only after the account owner explicitly authorizes them.
Google data accessed
Some private integrations use these read-only Google permissions:
- Gmail: sender, subject, received time, importance label, and a short snippet for a bounded set of recent messages.
- Google Calendar: calendar name, event title, start and end times, and all-day status for near-term events.
These integrations do not request permission to send, modify, or delete email or calendar data. They do not retrieve attachments or retain full email bodies.
How connected data is used
Connected-service data is used only to provide personal summaries and automations requested by the account owner. Processing occurs on owner-controlled hardware using local software and, where appropriate, a local AI model. Google user data is not used for advertising, eligibility decisions, sale, or training a general-purpose AI or machine-learning model.
Storage and retention
- Authorization credentials are stored in protected files on owner-controlled hardware.
- A collection may produce a bounded context snapshot on the owner's private network. The snapshot becomes unavailable after a short validity period and remains unavailable until replaced or removed.
- A generated summary, rather than the raw Google source data, may remain in private communication services and local operational history until the owner deletes it.
Sharing and transfer
Google data is transferred only among the owner's private systems to provide the requested personal feature. A finished summary may be sent to a private communication service selected by the owner, including Discord. Google user data is not sold or disclosed to data brokers, advertisers, or unrelated third parties.
Security
Safeguards include separate least-privilege credentials, protected local files, authenticated data transfer, network allowlists, bounded data collection, freshness limits, and fail-closed source validation. Retrieved text is treated as untrusted data rather than executable instructions.
Your control and deletion
The account owner can revoke a connected service at any time from that service's account settings. Revocation prevents future API access. The owner can also delete local authorization credentials, context snapshots, local run history, and delivered messages.
Use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.