Landing Privacy Notice
Last updated: June 28, 2026
This Landing Privacy Notice (this "Notice") explains how Inkberg LLC handles information from visitors to the public Inkberg landing website. This Notice is narrower than the main Inkberg Privacy Notice for authenticated account, issuer, investor, verification, wallet, tax, document, and offering workflows.
1. Scope
1.1 This Notice applies to public browsing of the Inkberg landing website, including pages hosted at inkberg.com or another Inkberg-controlled public marketing domain.
1.2 If a visitor enters the Inkberg app, creates an account, submits information, connects or selects a wallet, begins issuer onboarding, begins investor onboarding, pays a fee, completes verification, reviews offering materials, or participates in an offering workflow, the broader Inkberg Privacy Notice and applicable workflow documents govern that additional processing.
1.3 This Notice does not change securities eligibility requirements, offering restrictions, investor verification requirements, tax-certification requirements, or any rights and obligations under an offering document or platform agreement.
2. Information Collected From The Landing Website
2.1 The landing website is currently intended to operate as a public marketing site with a simple waitlist form. If a visitor submits the waitlist form, Inkberg collects the email address and related form metadata the visitor provides.
2.2 Inkberg and its infrastructure providers may collect ordinary technical and operational information when the landing website is visited or a waitlist form is submitted, such as:
- IP address or approximate network location;
- browser, device, operating-system, and language information;
- request URLs, referrers, timestamps, and error logs;
- security, rate-limit, bot-detection, and abuse-prevention signals;
- static asset requests, including font and image requests; and
- similar information needed to host, secure, debug, and deliver the website.
2.3 The landing website may load fonts from Google Fonts, may be hosted or protected through Cloudflare or similar infrastructure, and may route waitlist form submissions through FormSubmit.co or a successor form-processing provider. Those providers may receive technical request information and submitted form fields under their own terms and privacy notices.
2.4 Inkberg uses PostHog Cloud US for aggregate landing website analytics through Inkberg's reverse proxy at r.inkberg.com. PostHog is configured in cookieless mode for the landing website. Inkberg does not identify landing-page visitors in PostHog and does not send waitlist email addresses or form field values to PostHog. If Inkberg later adds cookie-based analytics, advertising pixels, behavioral advertising cookies, chat tools, or similar features, Inkberg should update this Notice or provide an appropriate supplemental notice before relying on those features as live public-site defaults.
3. App Handoff And Broader Platform Processing
3.1 Links from the landing website may direct visitors to app.inkberg.com or a successor app domain.
3.2 App workflows may collect or process account data, contact details, authentication data, wallet metadata, identity and entity verification data, sanctions-screening data, investor eligibility data, tax-certification data, issuer authority records, offering documents, payment references, support records, and transaction or recordkeeping references.
3.3 Those app and offering workflows may involve Inkberg LLC, affiliated or issuer-side entities, issuers, Sponsors, Founder / Target CEOs, identity, investor-eligibility, tax, wallet, payment, hosting, storage, archival, compliance, and support providers, professional advisers, regulators, courts, and other approved recipients where required by the workflow.
3.4 Some blockchain or archival records may be visible or persistent by design. Private compliance, tax, identity, issuer, filing, and evidence records are intended to remain role-restricted or privately retained unless a workflow expressly makes a limited public reference available.
4. Uses Of Landing Website Information
4.1 Landing website information may be used to:
- deliver and operate the website;
- maintain security, availability, and abuse-prevention controls;
- debug technical issues;
- measure basic operational performance where supported by hosting logs;
- manage waitlist requests and launch follow-up;
- route visitors to the app or public legal notices;
- preserve legal, audit, security, and compliance records where reasonably necessary; and
- comply with law, court order, regulatory request, or valid legal process.
4.2 Inkberg does not use public landing website browsing alone to determine investor eligibility, issuer approval, accredited-investor status, allocation, offering access, tax status, or investment suitability.
5. Retention
5.1 Technical logs and security records may be retained for as long as reasonably necessary for hosting, security, troubleshooting, fraud prevention, legal compliance, dispute handling, and operational continuity.
5.2 If a visitor enters an app workflow, app and offering records may be retained for longer periods where required for securities, tax, audit, evidence, dispute, archival, blockchain, or platform-record purposes.
5.3 Waitlist contact records may be retained until they are no longer needed for launch follow-up, operational records, or lawful business purposes, unless a shorter period is required by law or requested rights apply.
5.4 Deletion of an account or contact record may not delete public blockchain records, public-safe archival references, immutable transaction records, legal records, tax records, filing records, or records that Inkberg or another authorized party must retain.
6. Security
6.1 Inkberg intends to use commercially reasonable administrative, technical, and organizational safeguards appropriate to the landing website and related infrastructure.
6.2 No website, provider, network, device, wallet, or storage system can be guaranteed to be perfectly secure or continuously available.
7. Privacy Requests
7.1 To the extent applicable law provides rights of access, correction, deletion, restriction, objection, portability, appeal, or similar rights, a visitor may submit a request to Inkberg Privacy Team at privacy@inkberg.com.
7.2 Inkberg may require identity verification, authority verification, or additional information before acting on a request.
7.3 Requests may be limited, delayed, or denied where records must be retained for legal, regulatory, tax, audit, security, fraud-prevention, dispute, blockchain, archival, or other lawful reasons.
8. Contact
Privacy questions and requests may be directed to:
Inkberg Privacy Team privacy@inkberg.com Mailing address available upon request where required by applicable law.