Privacy

PolicyReadable version

01 / Scope

Where this applies

This policy covers this portfolio website and the features around it: browsing, contact forms, newsletter prompts, authentication, profiles, comments, project pages, blog pages, and collaboration conversations.

A signed project agreement, NDA, proposal, or statement of work controls if it sets stricter privacy or confidentiality terms.
Website content is for evaluation and general information; production project access is handled separately.

02 / Data

Information you share

You may share your name, email, phone number, message details, account profile, comment text, subscription preference, or project context when you use the site or reach out.

If you sign in with a provider like GitHub or Google, I receive only the account details needed for login and profile display.
Contact and comment content may include information you choose to write, so avoid sending secrets or sensitive material in public fields.

03 / Project material

Client materials and access

If a conversation becomes project work, any repositories, datasets, prompts, documentation, credentials, cloud accounts, logs, or internal notes you provide remain your responsibility and are used only for the agreed purpose.

Access should follow least-privilege principles and should be revoked when it is no longer required.
Do not provide regulated, sensitive, or third-party restricted data unless the written scope explicitly permits it.

04 / Use

How information is used

I use information to respond to messages, manage sessions, show profile and comment activity, prevent misuse, improve the experience, and support requested engineering or AI/data work.

Operational logs, datasets, and internal documentation should be shared only to the extent needed for the work.
AI, automation, and RAG workflows may depend on the quality and permissions of the material provided.

05 / Security

Credentials and security

I design for careful handling of credentials, infrastructure access, and technical material, but secure collaboration requires disciplined access control on both sides.

Credentials should be shared through secure channels and stored in approved secret-management systems, not in public comments or plain contact messages.
Security reviews, compliance audits, or formal certifications require a separate written scope.

06 / Providers

Third-party services

This site and related workflows may rely on providers for hosting, analytics, identity, booking, comments, media delivery, email, model APIs, databases, or cloud infrastructure.

Those providers operate under their own terms, privacy policies, availability limits, and security models.
Provider changes, outages, rate limits, model updates, or policy changes may affect how a feature behaves.

07 / Control

Retention and deletion

I keep information only as long as it is useful for the purpose it was provided, required for site operation, or needed for security, debugging, legal, or continuity reasons.

You can ask to access, correct, or delete information connected to your account, comments, contact messages, or newsletter preferences.
Upon project completion or termination, confidential materials should be returned or deleted where practical and legally permitted.

08 / Promise

No selling

I do not sell your personal information. I only share data when needed to run the site, provide a requested feature, comply with law, or protect the integrity of the experience.

I do not use private client material, credentials, datasets, or internal documentation for unrelated public portfolio content without permission.
Case studies or public attribution should avoid confidential details unless you explicitly approve them.

Questions aboutyour data?

Email me directly if you want to review, update, or remove information connected with your account, comments, contact messages, or newsletter preferences.

CONTACT