Privacy policy

Private by default
Open by choice

Open source should make our work inspectable, not make your information public. This policy explains that boundary and the limited data our website needs to work.

Effective July 3, 2026

The short version

We collect information you choose to give us, basic technical data needed to deliver and protect the site, and public contribution data when you work with us in open-source spaces. We do not sell personal information, run behavioral advertising, or use private form and fit-check responses to train general-purpose AI models.

1. Scope

This policy applies to the DataJourneyHQ website and the forms on it, including the Academy Fit Check. “DataJourneyHQ,” “we,” and “us” refer to DataJourney Innovations LLC.

Our website links to services such as the DataJourneyHQ Academy, Lean Launch Mate, GitHub, Cal.com, Discord, LinkedIn, and other third-party sites. Their own privacy notices govern information you provide directly to them. A link from us does not merge their data practices with ours.

2. Information we handle

Information you provide

  • Contact requests: your name, email, organization if provided, chosen topic, and message.
  • Academy Fit Check: your name, email, organization, quiz responses, consent, and the recommended path calculated from those responses.
  • Business and community conversations: information you share while discussing consulting, Academy participation, partnerships, talks, workshops, support, or open-source work.

Information created when the site is used

Our hosting and security providers may process standard request and device information such as IP address, browser and device type, requested page, timestamps, referring page, and security signals. We use Cloudflare Turnstile on forms to distinguish legitimate submissions from automated abuse.

Public open-source activity

If you interact with our public repositories or community spaces, we may see the public profile, username, contribution, issue, pull request, comment, commit metadata, and attribution that the platform makes available.

3. How we use information

We use personal information only where it helps us:

  • respond to requests and continue conversations you start;
  • calculate, deliver, and follow up on an Academy fit result when you consent;
  • provide consulting, education, products, support, and community activities;
  • maintain projects, review contributions, preserve attribution, and enforce community standards;
  • protect forms, services, contributors, and visitors from spam, fraud, and security threats;
  • operate, troubleshoot, and improve the reliability and accessibility of the site; and
  • meet legal obligations and establish, exercise, or defend legal claims.

Depending on where you live, our legal basis may be your consent, steps you ask us to take before entering a contract, performance of a contract, compliance with law, or our legitimate interests in operating and securing DataJourneyHQ. You may withdraw consent for future use at any time.

We do not sell personal information. We do not use it for cross-context behavioral advertising, and this website does not currently run advertising pixels or behavioral analytics. The site may store strictly necessary security data or load resources, such as fonts, from a service provider.

4. Open source and public spaces

Public by choice

Code, issues, pull requests, discussions, profiles, and attribution you intentionally publish in a public project.

Private by default

Contact messages, fit-check responses, customer work, non-public project material, and private correspondence.

Public contributions may be indexed, quoted, forked, archived, or copied by others. Removing content from the original location may not remove those copies or the project history. Use a pseudonym or platform privacy settings if you do not want your legal name or email exposed, and never post credentials, security keys, private customer data, or sensitive personal information in a public issue or repository.

Repository-specific licenses, contributor guidance, codes of conduct, and platform terms govern public contributions. This privacy policy does not change an open-source license or create a license where none exists. Please report a suspected vulnerability privately through an available security-reporting channel rather than opening a public issue.

5. AI and automated access

We publish an llms.txt site guide so automated readers can find authoritative public pages. The guide is navigational metadata, not permission to ignore repository licenses, intellectual-property rights, privacy choices, access controls, or website instructions.

We do not currently send contact-form messages or Academy Fit Check responses to an AI model provider or use them to train a general-purpose model. If that practice materially changes, we will update this policy and use consent or another valid legal basis where required.

Public site and repository content may be crawled or indexed by third parties beyond our control. Do not submit confidential information to a public channel because you expect an automated reader to overlook it.

6. When information is shared

We share information only as needed with:

  • Cloudflare, which hosts and protects the site and provides Turnstile bot detection;
  • Resend, which sends contact confirmations, internal notifications, and Academy plans by email;
  • Google Fonts, which may receive standard request data when your browser loads site fonts;
  • professional advisers, contractors, or collaborators who need access for a defined business purpose and are expected to protect it;
  • authorities or other parties when required by law, necessary to protect rights and safety, or relevant to a corporate transaction.

When you choose an external link or service—including GitHub, Cal.com, Discord, LinkedIn, the Academy site, or Lean Launch Mate—you interact with that provider directly. Review its privacy notice before providing information.

7. Retention

We keep personal information only as long as reasonably needed for the purpose described above, an ongoing relationship, security, dispute resolution, or legal and accounting requirements. As a working practice, we review and remove stale inquiry and fit-check records when they are no longer useful, generally within 24 months after the last substantive interaction. Contract, payment, and compliance records may be kept longer where law requires.

Public open-source contributions and attribution can remain in project history indefinitely because removing them may damage the integrity, licensing record, or security of the project. Service providers may keep limited logs and backups under their own documented retention schedules.

8. Your choices and rights

Depending on your location, you may have rights to access, correct, delete, restrict, or receive a copy of your personal information; object to certain processing; withdraw consent; or complain to your local privacy regulator. We will not discriminate against you for exercising a privacy right.

To make a request, use our contact form and write “Privacy request” as the topic or in the message. We may need to verify your identity and clarify the scope before acting. Requests involving public repository history may be limited by other contributors’ rights, platform controls, security, and license records.

9. Security, international transfers, and children

We use reasonable technical and organizational safeguards, including limited collection, bot protection, and access controls. No internet transmission or storage system is completely secure, so please do not send secrets, credentials, or highly sensitive personal data through a general contact form.

DataJourneyHQ and its service providers may process information in countries other than yours. Where required, we rely on appropriate contractual or legal safeguards for those transfers.

The site is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has provided information, contact us so we can review and remove it where appropriate.

10. Contact and policy changes

DataJourney Innovations LLC is responsible for the practices described here. Send privacy questions or requests through the DataJourneyHQ contact form.

We may update this policy when our services or legal obligations change. We will post the revised version here and change the effective date. If a change materially affects how we use information already collected, we will provide additional notice or seek consent when required.