FOLKBENCH / LEGAL

Privacy Policy

This Policy explains how Havenbyte LLC handles personal information when you visit, sign in to, submit information to, or participate in Folkbench.

Last reviewedEffective

1. Scope and responsible entity

Havenbyte LLC operates Folkbench and determines how personal information is processed for the service, except where a third party independently determines its own processing. This Policy applies to Folkbench public pages, accounts, vendor workspaces, evaluation participation, support, and related operations.

2. Information we collect

  • Account and identity information, such as an identity-provider subject, display name, verified email, profile image, organization membership, role, and session records where sign-in is enabled.
  • Vendor and service submissions, agreement acceptance, public sources, test-target information, and authorized representatives’ contact details.
  • Evaluation control records, compact results, evidence manifest metadata, review decisions, corrections, and audit history. Raw process artifacts are intended for private object storage rather than public pages or large database fields.
  • Security and operational metadata, such as request or run identifiers, timestamps, route, status, latency, error category, release, and limited network information needed to protect and operate the service.
  • Optional analytics fields after consent, including bounded page, interaction, attribution, and performance data. Folkbench does not include search text, email, full URLs, session replay, or automatic click capture in this browser analytics schema.
  • Communications you choose to send, including support, correction, vendor, privacy, or security requests.

3. Sources of information

We receive information from you, your organization, configured identity providers, participating vendors, public provider sources, controlled evaluation systems, and service providers that support Folkbench. We distinguish provider statements from observed, measured, calculated, editorial, and unknown facts.

4. How we use information

  • Provide accounts, workspaces, directory pages, evidence review, corrections, and support.
  • Authenticate users, enforce roles, protect credentials, prevent abuse, and investigate security incidents.
  • Operate controlled evaluations, sanitize evidence, calculate versioned results, and publish approved snapshots.
  • Maintain audits, troubleshoot failures, measure service reliability, and improve Folkbench.
  • Comply with law, enforce agreements, and establish, exercise, or defend legal claims.
  • Process optional analytics only after the consent required by the Folkbench analytics design.

5. Legal bases

Where applicable law requires a legal basis, processing may be necessary to perform a contract, take requested pre-contract steps, pursue legitimate interests in operating and securing Folkbench, comply with legal obligations, protect vital interests, or act on consent. You may withdraw consent for optional analytics through Analytics choices without affecting earlier lawful processing.

6. How information is shared

We may share limited information with infrastructure, managed database, private object-storage, identity, analytics, communications, professional-adviser, and security providers as needed for their functions. Google or GitHub may participate when their sign-in option is configured. PostHog US Cloud may receive the bounded analytics projection only if analytics delivery is enabled and you consent.

If payments are enabled in the future, Stripe and relevant payment-method providers will process payment information under their own roles and notices. Folkbench does not currently accept live wallet top-ups through this Beta.

We may disclose information when required by valid legal process, to protect rights and safety, or as part of a corporate transaction subject to appropriate safeguards. We do not sell personal information or use raw evaluation evidence as public directory content.

7. Retention

We retain information only for as long as reasonably necessary for the purposes described here, including account operation, evidence integrity, security, disputes, audit, and legal duties. Retention depends on the record type, sensitivity, publication state, and applicable requirements.

Production collection of raw evaluation artifacts will not begin until artifact-specific retention, lifecycle, deletion, legal-hold, and joint database/object-storage recovery rules are approved. Published facts and audit records may remain longer than raw process evidence so changes can be explained.

8. International processing

Folkbench and its service providers may process information in the United States and other locations. Where required, Havenbyte LLC will use an applicable transfer mechanism and related safeguards. Provider locations and legal roles may differ by product and user location.

9. Security

We use measures designed to protect information, including transport encryption, server-only secrets, protected sessions, role checks, least-privilege service access, bounded logs, private raw evidence, and audited publication controls. No system is completely secure, and repository foundations or a successful health check are not proof of production security or recoverability.

10. Your choices and rights

Depending on applicable law, you may request information about processing, access, correction, deletion, restriction, portability, or objection, and may appeal certain decisions or complain to a data-protection authority. Some requests may be limited by identity verification, evidence integrity, legal duties, or the rights of others.

You can allow, decline, or later change optional analytics through the Analytics choices control in the footer.

11. Children

Folkbench is a business and technical service and is not directed to children. Do not provide personal information through Folkbench if you are not old enough to consent to the relevant processing under applicable law.

12. Updates and contact

We may update this Policy to reflect changes in the service or law. The effective date appears above. Privacy requests may be submitted through the contact page; do not send identity documents, passwords, API keys, or raw private evidence in an initial email.