1. Who we are
Chroniq is operated by Syscake S.r.l., Via Quinto Novio 44, 00175 Rome (RM), Italy, VAT and tax identification number 16207441003 (“Syscake”, “we”, “us”).
For privacy requests or questions about Chroniq, contact chroniq-support@syscake.it.
2. What this policy covers
This policy applies to the Chroniq macOS application, the website at chroniq.syscake.it, and support communications relating to Chroniq. Chroniq does not require a Chroniq account, and Syscake does not operate a cloud service that stores your meeting archive.
Services you choose to use with Chroniq—including Google Gemini, OpenAI, Anthropic, an OpenAI-compatible server you configure, Google Drive, Google Docs, Hugging Face and its download hosts, GitHub, and Apple—also process data under their own terms and privacy policies.
3. Meeting data stored locally
Chroniq records microphone and system audio only after an explicit action. It stores source audio tracks, transcripts, generated artifacts, meeting metadata, processing state, timing metrics, token-usage metrics, and local diagnostic records in locations on your Mac that the application is authorized to use.
- Audio transcription runs locally on your Mac. Selecting a local GGUF model also keeps artifact generation on this Mac, on macOS 15 or later.
- Microphone and system audio are never sent to any model provider or to Google Drive.
- Your local meeting archive is not automatically sent to Syscake.
- You control the archive location, corrections, regeneration, export, and deletion.
Ordinary diagnostics contain processing events and timing information without meeting text. A dedicated local provider-response ledger stores the complete response returned by Gemini for inspection; for OpenAI, Anthropic and OpenAI-compatible servers, Chroniq keeps only normalized metadata such as timings, token counts and error categories. Local generation plans and validated section evidence are stored with the meeting archive; reasoning traces are not retained. These records remain on your Mac unless you deliberately send them to Syscake, for example in a support request.
Recording reminders
Recording reminders are off by default. If you turn them on, Chroniq checks once a second, on your Mac, which applications are using a microphone input, using metadata provided by macOS. It never opens an audio device, reads audio, or starts recording without your action. Chroniq stores your reminder preference, the applications you choose to ignore, and short-lived timing information needed to avoid repeated reminders in its local preferences. It keeps no history of observed applications and sends nothing to Syscake.
4. Processing and optional services
Local transcription, GGUF models and downloads
Apple SpeechTranscriber provides on-device live transcription on macOS 26 or later using language assets managed by macOS. NVIDIA Parakeet provides on-device transcription after recording on macOS 15 or later using an explicitly downloaded model. Language detection and transcription run locally; audio is not uploaded for either mode.
llama.cpp artifact generation is available on macOS 15 or later. After a compatible GGUF model is installed, inference runs in a sandboxed service without network access. Chroniq does not send transcripts or generated artifacts to Apple or a model publisher for this local inference and does not automatically switch to a remote provider.
Public Hugging Face search and model downloads use the internet. The host and its delivery providers may receive your IP address, the requested repository and files, search query, and other ordinary network data. These requests do not upload your meeting content. Chroniq stores downloaded models, partial downloads, file checksums, licenses, and source revisions in local Application Support. Local imports are copied there without changing the original files. You can remove managed models in Settings. The llama.cpp runtime is an independent open-source project; model weights are supplied by their respective publishers. Apple language-asset downloads are handled by macOS.
Gemini artifact generation
If you select Gemini, configure its API key, acknowledge its disclosure, and request generated outcomes, Chroniq sends the current editable transcript and generation instructions directly from your Mac to the Google Gemini API. Google may receive the transcript, generated response, request metadata, IP address, and other technical data needed to provide the service. Your API key is stored in the macOS Keychain. Audio is not sent.
OpenAI, Anthropic and OpenAI-compatible servers
If you select OpenAI, Anthropic, or an OpenAI-compatible server, configure it, acknowledge its disclosure, and request generated outcomes, Chroniq sends the current editable transcript and generation instructions directly from your Mac to that provider: the OpenAI Responses API, the Anthropic Messages API, or the server address you enter. The provider may receive the transcript, generated response, request metadata, IP address, and other technical data needed to provide the service. OpenAI requests are sent with response storage disabled. A server you configure is operated by you or a third party you choose, under its own terms. API keys and optional server tokens are stored in the macOS Keychain, scoped to their provider or server. Audio is not sent.
Google Drive document publishing
If you connect Google Drive, select a destination folder, acknowledge the disclosure, and enable publishing, Chroniq sends meeting titles, generated artifacts, transcripts, meeting metadata, processing timings, and token-usage metrics directly to Google Drive and Google Docs. Chroniq requests only the drive.file permission, which limits access to files you select for, open with, or create through Chroniq.
Chroniq stores the Google refresh token in the macOS Keychain and holds short-lived access tokens in memory. Non-secret folder and publishing state is stored locally. Disconnecting removes the local refresh token and attempts to revoke it, disables automation, and does not delete documents already created in your Drive.
Google API Limited Use.
Chroniq’s use of information received from Google Workspace APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising, or use it to train generalized artificial-intelligence models.
5. Website and support data
The Chroniq website does not use analytics, advertising trackers, cookies, accounts, or contact forms. It is hosted through GitHub Pages and includes release download links updated when the site is published. When you visit the site or download a release, GitHub may process ordinary network and device data such as your IP address, user agent, request, and timestamp under GitHub’s privacy policy.
If you contact support, we receive the contact details, message, attachments, and any diagnostic or meeting information you choose to provide. Please avoid sending meeting content unless it is necessary for your request and you are authorized to disclose it.
6. Purposes and legal bases
Where Syscake receives personal data, we process it only as necessary to:
- provide the website and respond to support requests, based on performing a contract or taking steps at your request;
- secure, maintain, and troubleshoot Chroniq, based on our legitimate interests in operating a reliable product;
- meet legal, tax, accounting, security, and compliance obligations; and
- process data based on consent where applicable, which you may withdraw at any time without affecting earlier lawful processing.
Chroniq’s local processing and direct Google API actions are initiated and controlled by you. You are responsible for having an appropriate legal basis to record participants and process meeting content.
8. Retention, controls, and deletion
- Local meetings, audio, artifacts, generation checkpoints, and diagnostics remain until you delete them or remove the relevant local data. Model installations and partial downloads are managed separately in Settings.
- Google documents remain in your Drive until you delete them under your Google account’s controls.
- Google authorization remains until you disconnect Chroniq, revoke access in your Google Account, or Google expires or revokes it.
- Support communications are retained only as long as reasonably necessary to resolve the request, maintain business records, and comply with law.
- GitHub determines retention for website and download service logs under its own policies.
You can delete local meetings in Chroniq or Finder, remove configured API keys in Settings, disconnect Google Drive in Settings, delete published documents in Drive, and revoke Chroniq from your Google Account’s third-party access controls.
9. Your data-protection rights
Subject to applicable law, you may ask Syscake to access, correct, erase, restrict, or provide a portable copy of personal data we control, or object to particular processing. You may withdraw consent where processing depends on it. We may need to verify your identity and may retain information when the law permits or requires it.
You may also complain to the Italian Data Protection Authority (Garante per la protezione dei dati personali) or the supervisory authority where you live or work. Most meeting content is stored locally or in services under your control, so the fastest route is usually to use the deletion and revocation controls described above.
10. Security
Chroniq uses the macOS App Sandbox, Keychain storage for credentials, least-privilege Google scopes, explicit authorization, and local durable storage boundaries. No method of storage or transmission is completely secure. You are responsible for protecting your Mac, archive location, backups, Google account, and API credentials.
11. Children
Chroniq is a professional productivity tool and is not directed to children under 16. Do not use it to collect a child’s personal data unless you have all authorization and consent required by applicable law.
12. Changes and contact
We may update this policy when Chroniq, our providers, or applicable requirements change. We will publish the updated policy here and revise the date above. Material changes may also be communicated in the application or release notes where appropriate.