Builo Privacy Policy

Who operates Builo

Builo is operated by Devon Schell as an individual / sole proprietor in New York, United States, not an LLC or corporation. “Builo,” “we” and “us” refer to the operator providing this social network for entrepreneurs. This notice covers the website, beta requests, browser application, iPhone application and Builo service. Contact: [email protected].

Mailing address: Devon Schell, 125 E 30th St, Apt 1B, New York, NY 10016, United States.

Builo is currently offered as a free, public beta. We do not currently charge users for access.

Information we collect

When you request beta access, we collect your email, optional description of what you are building, consent version and submission time. We use a short-lived hashed network identifier for abuse prevention; we do not store a raw IP address in the waitlist database. Hosting and challenge providers may process technical request information. When you visit or use Builo, the services that deliver it may also process device or browser information, authentication events, request metadata and diagnostic or security logs as needed to operate and protect the service. We do not claim that all such information is stored in Builo’s application database.

In the app, we process account details, founder and company profiles, posts, comments, follows, club and sprint participation, notifications and sharing preferences. Content visibility depends on your choices and the service’s access rules.

Stripe verification

If an authorized company owner or administrator connects Stripe, Builo processes read-only financial evidence needed for verified revenue calculations, such as provider account and transaction identifiers, successful charges, refunds, disputes, amounts, currency, timestamps, coverage and synchronization status. Provider records may include related customer or transaction details supplied by Stripe; those private records are not public verified cards. Credentials are handled server-side. Connecting Stripe does not by itself authorize public disclosure.

Every post independently requires an explicit choice to attach a verified Revenue or Growth card for a specific company, period, currency and supported display mode. Ordinary posts require no Stripe connection or revenue. Attaching, replacing or removing one post’s card does not configure another post. Company-profile disclosures and leaderboard participation each require their own separate consent; neither enables financial posting. Exact amounts are hidden in supported non-exact modes. Growth requires valid comparison data. Public verified figures describe a particular eligible scope, not the company’s full financial condition. They use Builo’s server-side revenue methodology, including applicable refund and dispute adjustments, rather than promising gross sales or accounting profit. Available verified history is not the company’s complete lifetime revenue. Growth requires complete comparable verified periods and a valid baseline; a zero or otherwise invalid baseline does not produce an invented percentage. Verification reflects the displayed period, source, currency and freshness, and may become unavailable after corrections or eligibility changes.

Why we use information

We use information to review beta requests, send requested beta communications, provide accounts and community features, calculate verified metrics, enforce privacy and permissions, prevent abuse, diagnose issues and respond to requests. An early-access request does not create an account or automatically issue an invitation. Approved invitations and sign-in are handled separately through Supabase Auth.

Who receives information

Other users or visitors can see content you explicitly make public, subject to access rules. Service providers process information to operate Builo, including Supabase for app infrastructure, Stripe for connected financial evidence, Cloudflare for website hosting, waitlist storage and anti-abuse checks, Resend for authentication email delivery, Cloudflare Email Routing for inbound support forwarding, and Google Gmail for the operator’s support inbox. Providers may process data in countries other than yours.

We may disclose information where required by law or reasonably necessary to protect users, enforce terms or investigate security issues. We do not sell personal information or private Stripe evidence, and do not use it for cross-context behavioral advertising.

Website storage and analytics

The marketing site does not set advertising cookies or load behavioral analytics by default. The browser application stores its authenticated session on your device to keep you signed in; logging out clears that session. Native sessions use platform-appropriate secure storage. Necessary anti-abuse verification may contact Cloudflare Turnstile when you use the beta form. Authentication fallback pages have no analytics and do not store link credentials in cookies, local storage or session storage. If optional analytics are introduced, the notice and any required consent controls must be updated first.

Retention and security

We retain beta requests while needed to manage early access, subject to removal requests. We do not promise an automatic deletion schedule that has not been implemented. Account, financial and security records may have different operational or legal retention needs. Withdrawal of a public sharing scope suppresses access through the service; it cannot erase copies already made by other people.

We use access controls, secure transport and restricted server-side handling. Deleted or withdrawn information may persist in access-restricted backups until those backups are replaced or expire; it is not restored to normal public use solely because a backup exists. We restrict retained verification and audit records rather than promising to rewrite immutable evidence. No service can promise absolute security. Do not include credentials or sensitive financial exports in support requests.

Your choices and requests

You can choose what to post, manage authorized financial scopes, withdraw public participation and decline future beta communications. Email [email protected] with the subject “Privacy request” or “Delete my account” to request access, correction, deletion or waitlist removal. Requesting deletion does not itself erase records immediately; support verifies and handles the request. Some immutable verification, security and audit records may need to be retained with restricted access for integrity, dispute or legal obligations. Ask support about retained categories and their reason. We may verify your identity and consider legal retention obligations before completing a request. Rights depend on your location; where applicable, you may object to certain processing, withdraw consent for optional processing, request a copy of your information, or contact your local data-protection authority. We assess requests under the laws that apply and explain material retention limits. Public posts may remain in third-party screenshots, quotations or copies outside our control.

Age and changes

The public beta is for people aged 18 or older. If we learn that information was collected contrary to applicable age requirements, we will review and address it. We may update this notice as Builo evolves and will communicate material changes as appropriate.

Contact

For privacy requests: [email protected].