Data & privacy
Local where practical.
Clear about the rest.
CzerTek projects are designed around local processing whenever practical. Individual projects may connect directly to third-party services necessary for their functionality.
This website
This is a static website. It does not use cookies, analytics, tracking scripts, external fonts, or third-party embedded resources. There are no accounts or forms on this site.
As with any website, serving a page requires the hosting infrastructure to receive request information, such as your IP address and the requested URL. Server and reverse-proxy logging depends on the hosting configuration; the absence of analytics does not imply the absence of infrastructure logs.
Inbox Triage
Inbox Triage does not send your Gmail data, OAuth credentials, or application data to CzerTek servers. It communicates directly with Google services and stores application data locally. This application behavior is separate from the website request handling described above.
- The application works with Gmail metadata, headers, snippets, IDs, labels, and related information required for its functionality. Local data may also include account information, rules, job state, and audit information. Normal operation does not retrieve or store full email bodies or attachment contents.
- OAuth credentials and refresh credentials are protected locally using Electron safeStorage. Access tokens remain in memory.
- Bring Your Own OAuth is required: each user supplies and controls their own Google Cloud project and Desktop OAuth client. CzerTek provides no shared OAuth client, hosted authentication, backend, hosted sync, or managed Gmail access.
- The application has no advertising, analytics, telemetry, automatic updates, or AI service.
Credential protection does not mean all local application data is encrypted. Disconnecting an account does not delete all local application data. The application includes a deliberate local-data/reset function; do not assume uninstalling removes all user data.
The gmail.modify scope is required for Gmail organization
actions; mail.google.com is not requested.
See Inbox Triage setup
for the required scopes and Google project responsibilities.
ZYN Rewards
Imported reward URLs and codes are stored locally in a SQLite database. This database is not application-level encrypted.
There is no CzerTek backend, analytics, or telemetry. When you open an imported reward URL, your browser connects to that destination website and its privacy practices apply.
Mission Where Package
The application queries OpenSky Network for aircraft information. Geographic query information is necessarily sent to OpenSky to obtain that data.
Matching and monitoring logic runs locally. Application data, including settings, logs, and rate-limit information, may be stored locally. There is no CzerTek backend, analytics, or telemetry.
The application monitors aircraft, not individual packages, and does not access carrier shipment tracking systems.
Third-party services
Services such as Google, OpenSky Network, GitHub, and websites opened from imported reward URLs have their own privacy practices. Those services receive information needed for the interactions you make with them. Local processing within a CzerTek project does not prevent the third-party connections described above.
Review the relevant service's privacy information when using it. This page describes the website and project data flows; it does not make guarantees about third-party services.
Independent projects
CzerTek and its projects are independent personal work. They are not affiliated with, endorsed by, or sponsored by referenced third-party brands or services, including Google, ZYN and its manufacturer, UPS, FedEx, DHL, and OpenSky Network.