Who We Are
OSINT Fieldbook is being built as an education-first OSINT and cyber learning platform at osintfieldbook.com. The public launch should make the operator, contact routes, commercial relationships, and safety boundaries obvious before anybody is asked to trust the site.
Business Identity
- Legal entity
- To be formed before public launch.
- Trading name / DBA
- OSINT Fieldbook, subject to local registration requirements.
- Primary domain
- osintfieldbook.com, registered through DigitalOcean.
- Registered jurisdiction
- To be confirmed with accounting and legal advice.
- Operator
- Founder-led, with a named human contact published before payments go live.
- Commercial model
- Free learning resources first, with clearly labelled affiliate links and any future paid tiers separated from editorial content.
DBA / Trading Name Note
A DBA, trading name, or fictitious business name is jurisdiction-specific. Before launch, choose the legal structure, register the trading name if required, and publish the company name, registration number, and service address where the law or payment providers require it. This page is a product placeholder, not legal advice.
Human Contact Policy
The site should publish monitored routes for general questions, safety reports, security disclosures, privacy requests, and partnerships. Planned routes are [email protected], [email protected], [email protected], and [email protected]. Each route should have a plain-language response target so learners know there is a real person behind the platform.
Affiliate Disclosure
Endorsed tools and discounts should live on a dedicated page. If an affiliate relationship exists, the link should be labelled near the recommendation so trust is not hidden inside fine print.
Before Launch Checklist
- Choose the legal entity and registered jurisdiction.
- Register OSINT Fieldbook as a DBA or trading name if required.
- Set up branded support, abuse, security, and privacy inboxes on osintfieldbook.com.
- Publish a named operator or company contact route.
- Have terms, privacy, acceptable use, and affiliate wording reviewed.
- Document how security disclosures and abuse reports are triaged.