Skip to main content

Website information

Policies & reporting

Open the section you need.

Updated 8 September 2026

PrivacyYour information and your choices.

This notice covers codejavu.tech. Customer agreements may include additional privacy terms.

Who to contact

Codejavu LLC, a Wyoming, United States company, is responsible for this website’s personal-data processing. For questions or requests, email [email protected].

What we collect

Your enquiries and emails, including name, work email, company, service, message, and referring page. We also process connection and browser signals for abuse prevention, usage and performance events, and authorised staff identity, login, role, and security records.

Don’t send passwords, keys, exploit payloads, confidential evidence, health information, government IDs, or other unnecessary sensitive data through the public form.

Why we use it

To answer enquiries, operate and improve the site, protect accounts, prevent abuse, and meet business and legal obligations. Depending on the context and applicable law, we rely on contract-related steps, legitimate interests, consent, or legal obligations.

We do not sell personal information or use it for third-party behavioural advertising.

Who helps us run the site

Vercel provides hosting, Web Analytics, and Speed Insights. MongoDB stores application and enquiry records. Cloudflare Turnstile checks for automated abuse. Cloudinary handles media, not enquiry records.

Resend sends enquiry notifications to our business mailbox. Failed notification delivery does not delete the enquiry stored for authorised staff.

Providers receive information needed for their roles and may process it abroad under applicable transfer mechanisms. We may also share information when legally required, to protect rights or safety, or during a corporate transaction with appropriate safeguards.

How long we keep it

Inactive enquiries are scheduled for deletion after 12 months, unless a continuing discussion, contract, dispute, or legal duty requires longer. Abuse-prevention identifiers follow configured security windows. Operational and provider logs follow their documented retention rules. Business and legal records follow applicable requirements.

Security and your choices

We use access controls, authentication, encryption in transit, and provider protections. No internet service can promise absolute security.

Depending on applicable law, you may request access, correction, deletion, restriction, a copy of your data, or object to processing. We may verify your identity and retain information where legally permitted or required. Contact us using the address above.

Children and updates

The site and services are not directed to children. Don’t submit a child’s personal information. We update this notice as practices or requirements change, with material changes shown here before or when they take effect.

Website termsUsing the site and its content.

Using the site

By using codejavu.tech, you agree to these terms. If you disagree, do not use it. You may browse, link to, and factually reference the site.

Do not disrupt services, bypass controls, probe private admin routes, or test systems without written authorisation. No malware, credential submissions, unlawful content, deceptive enquiries, spam, impersonation, false affiliations, or copying that violates law, third-party rights, or reasonable technical restrictions.

Working with us

Website descriptions are general information, not a quote, guarantee, offer, certification, opinion about your systems, or permission to test. A security engagement requires an agreement and statement of work signed by authorised representatives. Those documents take precedence over website content.

Research and artwork

Unless stated otherwise, Codejavu LLC or its licensors own the site’s design, text, software, research presentation, and brand assets. Third-party marks belong to their owners.

The press kit permits accurate editorial identification under its usage rules. Do not modify the artwork or imply endorsement, affiliation, certification, sponsorship, or a customer relationship. No other licence is implied.

Research is for education and responsible defensive use. Historical findings may no longer apply. Verify current facts and obtain authorisation before testing. Use our disclosure policy to report issues; it does not grant testing permission. We do not control linked sites or their security, availability, content, or privacy practices.

Availability and responsibility

The site is provided as available. We do not promise uninterrupted access, complete accuracy, or suitability for a particular purpose.

To the extent permitted by applicable law, Codejavu LLC is not responsible for indirect, incidental, special, consequential, or punitive loss resulting from use of the public site. Nothing here excludes responsibility that cannot lawfully be excluded.

Changes and questions

We may update or withdraw content and these terms. The date above identifies the version. Continued use after an update means the revised terms apply from their stated effective date.

Questions? Email [email protected].

Report a vulnerabilityFound a security issue in our systems?

Contact us

Email [email protected] to arrange a secure reporting channel. Don’t include vulnerability details or use the public contact form.

Our systems only

This policy covers systems owned and operated by Codejavu LLC. It does not grant permission to test. Get written authorisation before active testing. A link, logo, or public hostname is not proof of ownership or permission.

Customer systems, third-party platforms, social profiles, programs, and linked tools are excluded unless explicitly authorised in writing. Follow their own reporting rules. If ownership is unclear, stop and ask.

Keep people and data safe

Do not access, change, keep, or disclose other people’s data. No destructive testing, denial of service, heavy scanning, password guessing, spam, social engineering, physical testing, malware, persistence, or staff-account access.

Stop once you can describe the issue. Use synthetic data and redact credentials and personal information. Coordinate disclosure with us in writing before publishing.

What to send

Once a secure channel is agreed, send the affected asset, a short summary, minimal non-destructive reproduction steps, impact, preconditions, and your contact details. Include redacted evidence only when needed.

Don’t send archives, executables, private keys, database records, unredacted credentials, or another organisation’s confidential evidence.

What happens next

We check ownership, reproducibility, and impact. Timing depends on the issue. We do not promise a response deadline, payment, bounty, or public credit. Any recognition is discretionary and depends on a valid report, lawful conduct, and agreed disclosure.