blendstra

Blendstra · Fenceline, Inc.

Privacy Policy

Effective 2026-10-29

Blendstra is operated by Fenceline, Inc. (“Fenceline,” “we,” or “us”). This Policy explains how we collect, use, share, and retain personal information when you visit Blendstra or use its workspaces, model pages, embeds, APIs, and agent tools.

Fenceline is responsible for the processing described here. Separate policies govern other Fenceline products and third-party services you choose to use. This Policy explains our practices; it is not a request for blanket consent to every use of information.

1. Information we collect

Account and connection information

We collect information used to create and manage your account, such as your name, email address, account identifiers, authentication status, workspace membership, and permissions. Google/Firebase provides authentication. If you use Google sign-in, we receive the basic account information needed to authenticate you, such as your name, email, and provider identifier.

We maintain session and authorization records for signed-in use and connected agents or apps, including the connection, approved workspace, permissions, and relevant activity. Blendstra's application does not store your password in its own account records; authentication is handled by the identity provider.

Project content and information you provide

We process models, source files, scripts, textures, images, reference files, descriptions, product information, saved versions, and other material you or your authorized tools submit. This can include personal information contained in uploaded files or their metadata.

We also process requests saved for your agent, project notes and review history, sharing settings, public creator credits, saved-model activity such as stars, and communications you send us.

Usage and technical information

We collect operational information such as request times, browser or device information, IP addresses in service logs, errors, model-processing status, resource usage, and security or audit events. We use this to run the Service, investigate problems, prevent abuse, and understand capacity and reliability.

We also use approximate country and, where necessary for regional restrictions, subdivision information supplied by our hosting provider from your browser connection to check service and payment availability. This is not GPS location, nationality, or proof of residence. We keep the latest observation and its time with your account; this feature does not retain the underlying IP address. Existing service logs are governed by the operational practices described above. These access checks are separate from optional analytics. With your analytics choice, the country may also be included in aggregate reports about account creation and modeling activity. If analytics is off, your country is not included in those reports. Contact us if an approximate location appears incorrect.

With your optional analytics choice, we collect limited first-party events about public-model discovery, link visits, sharing actions, and signup actions. These may include a public model identifier, a random event or browser-session journey identifier, a general arrival category, and a broad signed-in or visitor category. These events are separate from private modeling content and do not include your prompts or full browsing history.

2. How we use information

We use information to:

  • Authenticate users, manage workspaces, and enforce access and sharing choices.
  • Store and deliver models, run requested operations, preserve saved versions, and enable connected agents and apps.
  • Provide public model pages, discovery, attribution, stars, and permitted remixing.
  • Respond to support and privacy requests and communicate service or legal notices.
  • Diagnose failures, measure use and reliability, manage resources, prevent abuse, and improve the Service.
  • Meet legal obligations, resolve disputes, and protect users, Fenceline, and others.

Private project content is processed to provide and support the workflows you request. This Policy does not authorize using that content to train general-purpose AI models. Any optional use for that purpose would require a separate, clear choice.

We may use aggregated or de-identified information that no longer reasonably identifies a person to understand and improve the Service, and we do not attempt to re-identify it.

3. Your sharing choices matter

Projects are private by default, subject to access held by authorized workspace members and tools. “Private” does not mean inaccessible to the service providers that process the work or authorized personnel supporting, securing, or legally administering the Service.

When you publish, the model, public description, creator credit, and other information you choose to include become available to people with the public link. Listing in Explore makes the model discoverable there. Public material can also reach search engines, external websites, social services, and agents.

An unlisted public link is not private. A link that follows the current project may expose later saved results. Source downloads or remixes can expose embedded files and metadata, so review them before enabling those permissions.

Removing public access does not retrieve copies already downloaded, cached, shared, indexed, or lawfully remixed by others.

4. Connected agents, apps, and external websites

An agent or app you authorize can receive the data its permissions allow, such as project context, files, tool results, and model previews. If you save a request for a connected agent, that request may be available through the authorized connection.

Blendstra does not automatically receive an entire conversation from your AI provider. We receive the content that you or the connected tool actually send to Blendstra. The provider may receive and retain information returned by Blendstra under its own policies, including its own settings for AI training.

Disconnecting an integration stops new access under that authorization. It does not erase information the provider already received or necessarily stop work already submitted.

If a model is embedded in another website, that website has its own privacy practices. Requests needed to load the Blendstra model also reach our infrastructure. Links to manufacturers, products, and other external services lead to sites we do not control.

5. When we share information

We disclose information as needed in these circumstances:

  • Service providers: providers of hosting, storage, compute, authentication, monitoring, and support process information to help us run Blendstra. We currently use Google Cloud and Firebase for core infrastructure and authentication.
  • People and tools you authorize: workspace members, approved recipients, connected agents, and apps receive information according to their access.
  • Public sharing: information you publish is disclosed as described above.
  • Legal and safety needs: we may disclose information when reasonably necessary to comply with law or valid legal process, prevent fraud or abuse, protect rights or safety, or establish or defend legal claims.
  • Business changes: information may be transferred as part of a merger, acquisition, financing, reorganization, or sale of the relevant business, subject to appropriate protections and continued notice of material changes.
  • Your direction: we may disclose information with your consent or at your request.

We do not sell personal information or share it for cross-context behavioral advertising. We do not use private project files for advertising.

6. Cookies, browser storage and your choices

We use essential session and authorization cookies to sign you in and connect the agents you choose. We also use browser storage for requested features, including temporary drafts, pending remix recovery and saved viewer preferences. These features continue to work when you reject optional analytics. Authentication providers may use cookies or storage needed for their sign-in flows.

Optional analytics are off until you choose “Accept analytics.” They help us understand visits to public models, sharing actions, signup actions and how people reach Blendstra. With your permission, we store a random discovery journey identifier and a limited arrival category in session storage, for up to 24 hours within that browsing session. If you create an account, that arrival information may be associated with the new account. These identifiers are pseudonymous, not a guarantee of anonymity, and are not advertising identifiers. We do not send them in agent briefs.

“Reject optional” is available alongside “Accept analytics.” You can change or withdraw your choice through “Privacy settings” in the footer or on the Account page. We remember your choice on that browser for up to 180 days, including the notice version and time, solely to apply your preference. If browser storage is unavailable, your choice applies to the current page. Consent choices are separate from accepting the Terms or seeing this Privacy Policy.

Withdrawing consent stops future optional browser measurement and clears the discovery and arrival information from that tab's session storage. Other open tabs honor the change and clear that information when they receive the update or become active. We do not replay actions that occurred before consent. Withdrawal does not undo prior lawful processing or automatically erase records already received; contact us to exercise applicable deletion or other rights. A pending remix may retain an earlier identifier locally only to recover the same requested operation without making duplicate copies; it is not sent as new attribution while analytics are off.

We honor Global Privacy Control and Do Not Track signals by keeping optional browser analytics off. Embedded model viewers do not start optional analytics or display this consent notice. A website embedding a model has its own privacy practices.

Essential operational records, such as accounts, saved models, jobs, service errors, security events and resource usage, are handled separately from optional browser analytics to provide, secure and support the Service. Rejecting optional analytics does not stop this necessary processing. Our administrative reports may also summarize existing service records; applicable rights to object to personal-data processing remain available through the contact below.

We do not use advertising trackers, sell personal information or share it for cross-context behavioral advertising. You may also manage cookies and browser storage through your browser settings. Blocking essential storage can disrupt sign-in or requested features.

7. Retention and deletion

We retain account and project information while needed to provide the Service and maintain the work you choose to keep. Retention depends on the type of information, your account and deletion choices, active work, security needs, legal obligations, and applicable limitation periods.

Deleting a project withdraws access and starts the work needed to stop active processing and remove associated files. Cleanup may take time. It does not necessarily erase security, audit, usage, attribution, or legally required records, or another person's independently saved copy or permitted remix.

Account or workspace deletion is a separate request and may require support to complete the erasure of remaining personal information. Ask us if you want deletion beyond an individual project.

Revoking an original public link prevents new access and remixes through that link and hides its automatic source credit on public remix pages. It does not automatically erase source-credit metadata already saved with a remix, personal information embedded in copied files, or copies downloaded outside Blendstra. If information about you remains in someone else’s remix, contact us using the details below. We assess applicable correction, restriction and erasure rights for personal information in copies we hold, and notify recipients or take steps concerning downstream copies where required by law. Permission to remix does not remove applicable data-protection rights.

We keep support, security, and any legally required transaction records only for as long as reasonably necessary for their purposes. Backup copies, where maintained, may persist until their normal replacement or deletion cycle; they remain protected and are not used for unrelated purposes. We may retain information needed for a legal hold or dispute. Information no longer needed is deleted or de-identified.

8. Your choices and rights

You can review sharing settings, revoke available connections, delete projects, and download available model files through the Service. For account information, a broader data copy, correction, or deletion, contact support@fenceline.ai with “Blendstra privacy” in the subject.

Depending on your location and applicable law, you may have rights to access, correct, delete, or obtain a portable copy of personal information; restrict or object to processing; withdraw consent where processing relies on it; and appeal a denied request. You may also have rights relating to sales, targeted advertising, or certain automated decisions. Our current practices do not involve sales or cross-context behavioral advertising.

We may need to verify your identity and, where relevant, an authorized representative's authority. We will respond within the period required by applicable law, explain any lawful exceptions, and not unlawfully discriminate against you for exercising your rights. To appeal a response, reply to it or contact us with “Privacy appeal” in the subject. You may also complain to the relevant privacy regulator.

If you use a workspace controlled by another organization, that organization may also determine how information within the workspace is used. Contact it about its own practices or requests it must handle.

9. International users and legal bases

Fenceline is based in the United States, and Blendstra uses US-based infrastructure. Our providers may process information in other locations where they operate. Those countries may have different privacy laws. Where applicable law requires safeguards for an international transfer, we use an appropriate lawful mechanism, such as contractual protections, and you may contact us for information about the safeguards relevant to your data.

Where the EEA or UK rules apply, we rely on performance of our agreement to provide requested account and modeling services; legitimate interests to secure, support, and improve the Service where those interests are not overridden by your rights; legal obligations for required records and disclosures; and consent where required. You may withdraw consent without affecting earlier lawful processing.

Creating or processing a 3D model is not a decision about your eligibility for employment, credit, insurance, or a similarly significant personal outcome. We do not use Blendstra's modeling tools to make those decisions about you.

10. Security and children

We use safeguards designed to protect information, including access controls, authenticated connections, and restricted private-file delivery. No internet service can guarantee absolute security. Protect your account and avoid uploading secrets or sensitive personal information that is unnecessary for your project.

Blendstra accounts and creation tools are intended for adults aged 18 or older and are not directed to children. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us so we can investigate and take appropriate steps.

11. Changes to this Policy

We may update this Policy as Blendstra develops. We will publish the revised Policy with its effective date. For material changes, we will provide an appropriate notice through the Service or another reasonable method. If a change requires consent under applicable law, we will obtain it before applying that change. We will not treat a policy update alone as consent to a new use that requires your permission.

12. Contact

For privacy questions or requests, contact:

Fenceline, Inc.
1111b South Governors Avenue, STE 23921
Dover, DE 19904
United States

Email: support@fenceline.ai. Please identify the request as relating to Blendstra.

Version privacy-2026-10-29-v2