Privacy notice

1. Operator and scope

This notice covers the current Synaptik web preview from REDKO. It describes the code and services currently configured, not a promise about a future clinical service. Read the separate Consumer Health Data Privacy Notice for health-related information. The public rights-request contact and operator details are still being verified for this draft.

2. What you provide

Your device can store an optional name, adult confirmation, preferred time and session duration, symptom interests, self-reported diagnosed or suspected conditions, reduced-motion settings, saved activities and reminder preferences. It can also store mood, stress, energy and sleep-quality ratings; symptom selections; PHQ-4 answers and scores; timestamps and timezone; practice choices, progress, responses and reflections. Browser storage is not an encrypted medical vault.

The condition and symptom filters used only while exploring are temporary interface state. They are not sent as product analytics. If you choose to save condition or symptom information in your profile or check-in, it becomes part of your private journal instead.

3. Accounts and cloud records

Signing in uses the dedicated Synaptik Firebase project. Firebase and an identity provider such as Google process account identifiers, email, display name, authentication tokens and security information needed for sign-in. Passwords are handled by the authentication provider. Apple sign-in appears only when that provider is enabled.

With separate cloud-sync permission, the private wellbeing journal is stored in Supabase and linked to your Firebase account identifier. Account-owner access rules restrict ordinary users to their own records. Sync is not public sharing. Legacy game-account and population sync remain disabled unless separately configured and reviewed. Signing in alone does not enable wellbeing-record sync.

4. Optional product analytics

First-party REDKO product analytics are off unless you opt in. They record an allowlist of generic page categories, selected control identifiers, core-task start/completion/failure, voluntary stops and fixed-choice usability feedback. Selected public controls can include a coarse 10 × 10 click position and a broad viewport category. We do not capture screen recordings, DOM text, form values, full URLs, symptom or diagnosis selections, journal ratings, free text, game names, account IDs or advertising identifiers in this collector.

A random identifier is specific to each product and rotates after 30 days. MedLit uses a separate identifier and product partition, even when REDKO uses the same telemetry infrastructure. We do not join these identifiers to account or health records. Server and hosting providers still receive connection information such as IP addresses while processing requests; provider security logs have their own retention. This is pseudonymous telemetry, not a claim of complete anonymity.

GA4 and PostHog are a separate optional setting in Synaptik. When configured and enabled, they receive only approved generic product events under the existing event policy; autoplay/replay, automatic input capture and health-event payloads are disabled. They have their own provider identifiers and controls. Do Not Track and Global Privacy Control keep optional first-party analytics off. Turning off a setting stops future collection; it does not by itself erase earlier records.

5. Service providers and other disclosures

Vercel serves the website and public media. Google/Firebase provides authentication and configured account functions. Supabase hosts optional private journals and the first-party telemetry store. Google Analytics and PostHog process their optional product events when separately enabled. These services may process data in the United States and other locations under their applicable arrangements. REDKO personnel with authorized operational access may handle necessary records to maintain the service or respond to a verified request.

LTX and Blender are used to produce curated visual assets. The current client does not send your journal or condition selections to a generative-media service. A new feature that sends personal information to another processor requires updated disclosure and any required consent.

We do not sell health information, use it for targeted advertising or share it with other REDKO products for health profiling. We may disclose information when legally required, to protect lawful rights or address security incidents, or in a lawful business transfer subject to applicable notice and privacy protections. We do not authorize recipients to repurpose private journal data for their own advertising.

6. Retention and deletion

Local records remain in your browser until you delete them or the browser removes them. Synaptik offers local export and deletion in Your space. Cloud records persist until you use cloud-record deletion or a verified request is completed; turning sync off alone leaves existing cloud records in place. Account deletion and provider-retained security records are separate from journal deletion.

The first-party analytics database is pruned daily at 89 days, targeting a maximum 90-day active-store retention. The delete-analytics control stops collection and uses deletion keys retained by this browser to remove its current and prior rotating identities from that active store. Keys remain available for retry if deletion fails. Clearing your browser first may remove the keys needed to locate pseudonymous records. Unlinked, small-cell-suppressed aggregate reports may remain for product quality review. Provider backups and security logs are outside this active-store deletion mechanism; their exact schedules must be verified before a finalized notice claims complete deletion.

As reviewed on September 12, 2026, the dedicated GA4 property uses two-month event-data retention and fourteen-month user-data retention with renewal on new activity. These settings do not govern most standard aggregate reports. PostHog, hosting/security logs and provider backups require separate verified schedules; these GA4 settings are not a promise that every copy disappears at those times.

7. Your rights and choices

Depending on location and applicable law, you may have rights to access, correct, delete, obtain a copy, withdraw consent, restrict certain processing, appeal a denied request or complain to a regulator. We will not penalize you for exercising applicable privacy rights. Use Your space for local export/deletion, optional cloud controls and first-party analytics deletion. Downloaded files and copies you share are outside these controls.

A verified public request channel is required before this draft is finalized. Requests may require proportionate verification to protect against unauthorized access. Do not send passwords, provider tokens or unnecessary sensitive details in a request. This preview is not offered as a HIPAA-covered clinical service; ordinary consumer health apps are not automatically protected by HIPAA. Other privacy and consumer-protection duties may still apply.

8. Children, security and changes

The service is intended for adults 18 and older. We do not knowingly invite children to submit health records. If we learn that a child supplied data, we will address it consistent with applicable law.

We use transport encryption and account access controls where configured. No system is perfectly secure; avoid shared devices for sensitive entries. We will respond to incidents and provide notifications required by applicable law. A new purpose or category of health processing requires updated notice and consent where required. The dated notice and prior versions should remain accessible.

9. Purpose-by-purpose choices

Requested features use the information needed to perform that feature: profile preferences personalize the interface; check-ins and screenings create your private record; task responses produce task feedback; optional sync copies the selected record to your account; and optional product telemetry helps evaluate usability. The app does not make employment, insurance, credit or medical eligibility decisions from your scores.

You can explore before creating an account, omit optional ratings and conditions, decline analytics and leave a practice early. Local saving, cloud syncing and analytics are separate. Research enrollment is closed. We do not treat a general terms checkbox as consent to research or new health-data sharing.

10. Device storage, authentication and exports

On the web, your browser stores the journal and related preferences for the current device/account context. Signed-in and guest histories are separate. On supported native builds, operating-system secure storage protects authentication persistence; it does not turn every journal or game-history file into an encrypted medical record. Someone with access to an unlocked device or browser profile may be able to read local information.

An exported JSON file or personal summary may contain sensitive information in readable form. Store it somewhere private and review it before sending. Deleting the app or its active records does not delete a downloaded file, a device backup, a screenshot or a recipient's copy. We cannot recover an unexported guest history after the browser permanently removes it.

11. Provider details and international processing

Provider roles differ: Firebase authenticates accounts, Supabase hosts opted-in private records and the separate first-party event store, and Vercel delivers web pages and public assets. Optional GA4 and PostHog process approved generic events only when enabled. Operators and providers can receive network and security metadata necessary to deliver and protect their services. We do not promise that every such record is immediately deleted by a client-side control.

The countries, processor contracts, subprocessor changes, backup schedules and relevant international-transfer safeguards must be verified for the final operating deployment. This draft does not represent an approved EU/UK transfer assessment or a clinical business-associate arrangement. A material new provider or purpose requires updated notice and any required permission before personal information is sent.

12. Regional rights and request handling

Applicable rights depend on where you live and which law covers the service. These may include confirmation/access, correction, deletion, portability, withdrawing consent, restricting or objecting to certain processing, appealing a refusal and complaining to a regulator. California's applicable rights can also include opting out of sale/sharing and limiting certain uses of sensitive information. We do not sell your health records or use them for targeted advertising.

For requests governed by Washington's My Health My Data Act, the usual response period is 45 days, with a conditional extension and notice; an appeal also has a 45-day response period. Statutory duties to address processors and backups are not waived by a limitation in the current interface. Other laws may set different periods. The final notice must publish a verified, monitored request and appeal channel. Until that is confirmed, this document remains a review draft rather than a claim that the full request operation is live.

When verifying a request, use the least information reasonably needed to protect the record. Do not send passwords, authentication codes, private keys, complete journal exports or unnecessary health details to a support address. A request should identify the product, the action sought and the relevant account or device context. A person without an account must not be forced to create one merely to exercise rights that do not require it.

13. Withdrawal, deletion failures and security incidents

Turning off optional analytics stops future collection; previously accepted events may remain until applicable deletion or retention processes run. First-party telemetry deletion uses this browser's retained deletion credentials and has a separate retry path. GA4/PostHog identifiers and provider-held data have separate procedures; the first-party delete control does not claim to erase their records.

Turning off cloud sync does not remove a cloud copy already saved. A failure message means the requested operation has not been confirmed; use the retry control and do not assume the data disappeared. Account deletion must address associated records and provider authorization where applicable. The public web journal-delete control currently identifies its narrower scope.

We minimize and protect information, but cannot guarantee absolute security. If an incident occurs, the operator must investigate actual access/disclosure and provide any notices required by applicable law. A required health-data breach notice is not limited to malicious hacking; an unauthorized disclosure may also require action.

14. Questions, updates and review status

The current data controls are linked below. This notice is intended to be readable before you enter sensitive information, during use and after a setting changes. Its version date changes when the described practices change materially. We will not silently use an older consent choice for an incompatible new purpose.

The legal operator, public privacy/support contact and complete provider retention schedule remain unverified. Their absence is a release issue to resolve, not a waiver of your rights. The draft should not be labeled effective, independently audited, HIPAA compliant or clinically validated until there is evidence for the specific statement.

15. Health inferences, research and future purposes

Health information can include an inference about a person, not only a diagnosis they type. We do not create advertising audiences or profiles for employment, insurance, credit or medical eligibility from your activity. Removing names or rotating browser identifiers alone does not make health-related information anonymous.

We do not use private journals to train our own general-purpose AI models. The present research enrollment is closed. Product analytics cannot be repurposed into a clinical outcomes study through a terms edit. A new study or materially different use requires its own assessment, clear notice and any required consent or authorization before it starts.

When preparing aggregate product reports, we minimize detail and suppress small groups. We will not try to reidentify information represented as deidentified and will require that commitment from any recipient of such information. Aggregation is not a guarantee of anonymity; outputs must be assessed before external disclosure.

16. Necessary retention and lawful disclosures

Information is retained for the described purposes and applicable legal obligations, not merely because it could be useful indefinitely. A legal hold must be limited to relevant records and reviewed when it ends. The operator must finish a category-specific retention schedule for cloud records, authentication records, security logs, backups, consent evidence and rights requests before claiming those schedules are verified.

Legal process and business-transfer provisions do not authorize voluntary blanket disclosure. The operator must assess legal validity, scope, confidentiality duties, notice restrictions and available protections before disclosing information. A privacy notice or company liability limit cannot excuse an unauthorized disclosure or a failure to give legally required incident notices.

The proposed service audience is adults aged 18 or older. An age statement or preview control is not proof of verified age. A service for minors, biometric monitoring, health-related advertising, an employer or insurer program, or a clinical integration requires separate review before introduction.