Cookie Policy

Socialize intends to launch without advertising cookies or cross-site behavioral tracking. Google Analytics 4 is optional and is loaded only after you actively allow analytics. If you decline, the analytics tag is not loaded.

Signed-in areas use browser storage required by account sign-in to maintain a session, complete OAuth flows, prevent abuse, and remember limited product preferences. The production deployment is reviewed after material provider changes to keep this policy accurate.

Cookies

Small values sent with web requests. A hosting, authentication, security, or load-balancing provider may set them when necessary for a protected route or session.

Local storage and IndexedDB

Account sign-in may use browser databases to remember the signed-in user and refresh the session. Socialize also stores your analytics choice under socialize-analytics-consent so it survives a browser restart.

Session storage

Temporary storage may support Google or GitHub redirect state and protect the integrity of an authentication attempt. It normally clears when the browser session ends.

Similar delivery records

Server logs, cache headers, and content-delivery records are not cookies, but may contain device or request information. They are described in the Privacy Policy.

Necessary storage supports a feature you request or protects the service. It may be used to:

• Keep a user signed in through account authentication.
• Complete and validate Google or GitHub OAuth redirects.
• Protect against cross-site request forgery, replay, or session abuse.
• Route requests reliably and detect operational failures.
• Remember a security or consent choice where the law requires it.

Blocking necessary storage may prevent sign-in, the dashboard, or account security features from working. Public profiles should remain readable without an account session.

Preferences

Socialize may remember a theme, motion, editor, or accessibility preference on the device. Where the preference is not necessary, it should be stored only after the user actively chooses it and should have a clear reset path.

Analytics

After consent, Socialize loads Google Analytics 4 to measure aggregate page visits and navigation. Manual page-view events contain the page path and title but omit URL query strings, account fields, and profile fields. Advertising storage, ad personalization, and Google advertising signals remain disabled.

Google Analytics may set identifiers such as _ga and_ga_* after consent. Their exact lifetime is controlled by the production Google Analytics property and may also be affected by your browser settings.

Advertising

Socialize does not intend to use advertising cookies, sell browsing data, or build cross-service visitor profiles. A future business-model change would require an updated policy and any notice or consent required by law.

Choosing Google or GitHub sign-in opens an authentication flow controlled in part by that provider. The provider may use its own cookies or account session under its policy. Socialize receives the authentication result and account fields permitted by the sign-in flow, not the provider password.

Account sign-in can persist its own state in the browser so you do not need to sign in on every page. Signing out clears the active Socialize session, but it does not sign you out of Google, GitHub, or other websites.

Browser controls can delete or block cookies, local storage, IndexedDB, and site permissions. The exact controls depend on your browser. Clearing Socialize site data will generally sign you out and reset local preferences.

Socialize asks before loading Google Analytics. Use the persistent Privacy choices control to withdraw a previous choice or choose again. Withdrawing sends a denied analytics consent update and stops future collection; you can remove previously stored analytics cookies through your browser's site-data controls.

Questions or requests can be sent to llewellynpaintsil34@gmail.com.

The operator of a self-hosted Socialize instance selects its backend project, domain, hosting, integrations, and any additional analytics. That operator is responsible for scanning the deployed site, publishing an accurate cookie notice, and collecting consent where required.

This managed-service policy does not describe storage added by a fork, reverse proxy, hosting provider, custom script, or linked destination.

The operator reviews production browser storage and network requests while signed out, signing in with each provider, editing a profile, and signing out. This policy is updated if that review finds an additional persistent identifier or purpose.

Material changes will be posted with a new update date. Where law requires consent for a new purpose, that purpose will not rely only on continued use of the service.