THE ARBOR PRIMUS
THE ARBOR PRIMUS / PRIVACY

Privacy Notice

How The Arbor Primus handles account, Build, sharing, verification, employer, purchase, and analytics information.

Version 1.0Reviewed Plain-language product policy

What this notice covers

The Arbor Primus stores information needed to provide the Build, Hobby Tree, resumes, sharing controls, employer workspace, opportunity marketplace, verification workflow, purchases, and safety operations. This notice describes the current product behavior in plain language; it is not a promise of a particular legal result or retention period.

Private by default

Professional Builds and Hobby Trees start private. A user chooses whether a Build or selected Hobby Tree content is private, unlisted, or public. Unlisted links are not placed in the public directory, but anyone who receives an unlisted link may be able to view the selected content.

Private evidence files, URLs, account settings, applications, messages, purchases, analytics, and admin content are not intended for public pages or crawler routes.

Information sources and sharing

Information may be entered or uploaded by a user, calculated by the platform, or reviewed through a specific Arbor Primus workflow. Public visibility describes who can access selected information; it does not make the information independently verified.

Do not upload passwords, government identification numbers, private identity documents, or someone else’s material without permission. Review each public selection before publishing and unpublish it when the information should no longer be public.

Verification, employers, and payments

Verification records are separate from ordinary profile content. Public surfaces show only the safe result and scope needed for context. Raw documents, private reviewer notes, internal fraud signals, and provider secrets are not public profile data.

Payment records and order identifiers are kept to operate checkout, entitlements, purchase history, and support. Stripe or another payment provider may process a payment when a supported checkout is actually configured; the app must not represent an unconfirmed payment as completed.

Analytics and account control

The product may record page, sharing, Build, marketplace, and checkout events to operate the service and measure use. Owner and admin traffic is excluded where the configured analytics controls identify it. Account and private product data are returned only through authorized server-side paths.

For a privacy question or correction request, use the current supported support path. Do not include passwords or raw identity documents in a support request.

These pages describe the current product boundaries. They do not replace a contract, legal advice, or any obligation that applies outside the product.