Published · Effective October 18, 2026 · Version 1.1
1. About this notice
This notice identifies current external services relevant to Chronacy’s information practices. Provider roles depend on the activity; not every provider acts exclusively as Chronacy’s processor. This notice supplements the Privacy Policy and Cookie Policy. Provider changes do not waive Chronacy’s contractual duties, privacy obligations, or requirements for fresh analytics consent. We update this notice and provide additional notice or consent where required before material changes take effect.
2. AI processing
Current AI API provider: OpenAI. Relevant transcript text, prompts, context, responses and image references may be transmitted for requested AI features. Transcription is performed locally; raw audio is not sent to this provider for transcription.
2.1 API training terms. Chronacy uses OpenAI’s commercial API. Under OpenAI’s business terms, API customer content is not used to develop or improve its services unless the customer expressly agrees. Chronacy does not authorize training of Customer Content without the separate permission described in Section 3.3 of the Privacy Policy.
2.2 Abuse monitoring. OpenAI’s standard API abuse-monitoring logs may contain prompts, responses, and related metadata. The ordinary retention period is up to thirty days for abuse prevention and safety monitoring. Retention may be longer where required by law or reasonably necessary to protect OpenAI’s services or third parties from harm. This monitoring period is not a promise that all information submitted through every API feature is erased on day thirty.
2.3 Separate application storage. Provider abuse monitoring is distinct from storage used by an API feature. Depending on the feature and configuration, application state, responses, or uploaded files may remain until deletion or a configured expiry, and safety exceptions may apply. Disabling stored responses does not eliminate every form of retention. Chronacy does not represent that its API use has zero data retention. OpenAI’s current feature-specific controls are described at https://developers.openai.com/api/docs/guides/your-data.
3. Payments
Current payment processor: Stripe. Stripe processes payment credentials, transaction and subscription information and may act independently for fraud prevention, payment-network and regulatory obligations. Chronacy does not store complete payment-card numbers or card security codes. Stripe Privacy Policy.
4. Cloud backup
4.1 Current cloud-backup settings. CrashPlan is configured to back up changes every fifteen minutes and retain deleted files for ninety days. Local deletion does not immediately purge cloud copies. Cloud removal depends on detection of the deletion, file verification, and archive maintenance. If a local quarantine file or snapshot is removed later, the separate cloud retention process applies after that later removal. Cloud copies may therefore persist beyond ninety days from the original request; ninety days is not a guaranteed date for erasure of every copy.
Current cloud-backup provider: CrashPlan. These settings describe the configured service; they are not a guarantee of immediate erasure. Recovery copies remain restricted and deletion suppression applies as explained in the Privacy Policy.
5. Optional analytics and search reporting
Google Analytics 4 provides optional Analytics and Performance reporting. Microsoft Clarity provides optional Behavior Analytics, heatmaps and webpage session replay. These categories require separate consent. GA4 also measures consented public workspace/campaign usage using opaque site labels; Clarity remains restricted to approved public marketing pages. Google Search Console supplies search-visibility reports without a visitor-tracking integration.
5.1 Independent provider use. Microsoft may process Clarity data for its own purposes under its terms and Privacy Statement, including product improvement, security, and advertising-related purposes where applicable. Chronacy’s configuration does not warrant that Microsoft has no independent permitted use. See https://www.microsoft.com/privacy/privacystatement and, for Google, https://policies.google.com/privacy.
5.2 Collected-data retention. Google Analytics retention depends on the property settings and report type and is not determined by the 180-day cookie period. Microsoft currently specifies thirty days for ordinary playback information and nine months for heatmap and click information and labeled or favorited sessions. Provider practices may change; Chronacy will update material disclosures as needed. Contact support for applicable configuration details and rights requests.
6. Current browser storage and provider notices
| Technology and provider | Purpose and category | Storage duration |
|---|---|---|
| Chronacy authentication and security storage | Requested sign-in, authorization, continuity, and request protection. Strictly necessary. | Session or the configured period for the relevant security or session function. |
| chronacy_consent_v1_production chronacy_consent_v1_test | Chronacy choice record for each environment, including permissions, version, and timestamps. Strictly necessary. | Up to 180 days after a choice is saved. |
| Matching consent key ending in _changed | Chronacy local-storage timestamp synchronizing preference changes between tabs. Strictly necessary. | Until removed or replaced; the reviewed implementation specifies no automatic expiry. |
| chronacy_ga_context_production chronacy_ga_context_test | Consent-bound copy of the traffic-analytics browser/session identifiers for minimal server-side conversion events. Optional Analytics and Performance; no account or payment identifiers. | No longer than the current consent expiry, up to 180 days. Removed on withdrawal where browser access permits. |
| _ga and _ga_<identifier> | Google Analytics browser and session identifiers. Optional Analytics and Performance. | Configured up to 180 days without automatic visit-based renewal; browser limits may shorten this. |
| _clck and _clsk | Microsoft Clarity site identity/preferences and association of page views with a session. Optional Behavior Analytics. | Microsoft-controlled cookie-specific periods, subject to browser restrictions. See the provider notices below. |
| CLID ANONCHK MR MUID SM | Potential Microsoft-domain identifiers and related cookies documented by Microsoft. Presence depends on consent, provider behavior, and browser restrictions. | Provider-controlled periods. See Microsoft’s cookie notice for current details. |
Google Privacy Policy: https://policies.google.com/privacy
Google Analytics cookies: https://support.google.com/analytics/answer/11397207
Google Analytics retention: https://support.google.com/analytics/answer/7667196
Microsoft Privacy Statement: https://www.microsoft.com/privacy/privacystatement
Microsoft Clarity cookies: https://learn.microsoft.com/en-us/clarity/setup-and-installation/clarity-cookies
Microsoft Clarity retention: https://learn.microsoft.com/en-us/clarity/setup-and-installation/data-retention
For privacy, provider, or deletion questions, contact support@chronacy.com. This notice lists currently disclosed AI, payment, backup and analytics services; contact us for other relevant infrastructure or communication recipients and applicable processing or transfer arrangements.