A short, practical explanation of what this site records.

Site operator and CodeOnRoids

This website is operated by Răzvan Todică, Founder of CodeOnRoids. CodeOnRoids is the engineering brand behind this portfolio and OmniRoids Studio.

Contact enquiries

Information sent through the contact form is used to review and answer your enquiry. The required fields are your name, email, reason, timeline, budget, and message. Company details are optional. A phone number is collected only when you explicitly choose telephone contact, and is used solely for this enquiry. Submissions may be stored in the private project database and sent to the configured contact mailbox so a reply can be made.

The form does not subscribe you to marketing email. A future marketing opt-in would require a separate, explicit choice.

Live chat and push notifications

The optional chat creates a random browser session token. The site stores only a one-way hash of that token, the messages you send, and timestamps in the private project database so the conversation can be continued from the same browser. Chat messages are not sent to analytics.

The site owner can enable browser push notifications from the protected admin workspace. Push subscriptions contain the browser endpoint and cryptographic subscription keys required by Web Push. Permission is requested by the browser, and the private VAPID key never reaches the browser.

Analytics choices

Analytics is optional. Until you allow it, Google Tag Manager and any GA4 or LinkedIn Insight Tag configured inside that container are not loaded. If you allow analytics, the site may record page views, CTA and LinkedIn link clicks, contact form start/success events, article views, article scroll depth, and campaign labels.

Form names, email addresses, company names, messages, budgets, timelines, and reasons are never sent as analytics event properties. You can reopen the privacy choices from the small settings control at the bottom-left of the page.

Campaign labels

Links may use the non-sensitive UTM fields utm_source, utm_medium, utm_campaign to understand which campaign brought a visit or enquiry. Use the naming convention described in the project analytics documentation.

LinkedIn connection

The private admin workspace can optionally connect the owner's LinkedIn account through LinkedIn OAuth. The access token is encrypted server-side and is used only for an owner-approved distribution workflow. It is not loaded by the public portfolio or sent as an analytics property.

The connection can be removed from the admin integrations screen. You can also revoke the app from LinkedIn account settings at any time.

Facebook and X connections

The private admin workspace can connect the owner's Facebook Page and X account to publish owner-approved content. Access and refresh tokens are kept server-side, are never exposed to public visitors, and are used only for the configured publishing workflow.

A connection can be removed from the admin integrations screen or revoked from the relevant Meta, Facebook, or X account settings. Revoking access prevents future publishing but does not automatically delete content already published on a social platform.

Revocation and data deletion

To request deletion of stored contact details or social-connection credentials, use the contact form and clearly identify the account or enquiry concerned. Requests are verified before deletion to avoid removing another person's data.

Disconnecting an integration deletes or disables the stored authorization used by this site. Content already published on LinkedIn, Facebook, or X must be removed directly on that platform.

Questions

For a privacy question or a request about an enquiry you submitted, use the contact form on the portfolio page.