Yokefellow - Trust & Legal
Privacy Policy
The data-use policy for wallet-linked activity, usage data, support data, blockchain-derived records, service providers, and user rights.
Effective Date: [4 10, 2026] Last Updated: [4 10, 2026]
1. What This Policy Is
This Privacy Policy explains how Yokefellow collects, uses, stores, shares, discloses, and otherwise processes personal data and related information when people use the platform. It applies to the Yokefellow website, apps, buckets, offerings, wallet-linked surfaces, APIs, SDK-connected services, support flows, and related platform tools. It is meant to explain Yokefellowâs data practices plainly, including wallet-linked activity, analytics, support data, cookies or local storage, third-party processors and service providers, retention, security, and user rights where applicable.
This document should be read as a disclosure document, not as marketing copy. Its purpose is to explain what information Yokefellow handles, how that information is collected, why it is used, when it may be shared, who may process it, how long it may be kept, and what choices or legal rights users may have depending on the laws that apply to them.
Because Yokefellow is a mixed onchain and offchain platform, some information covered by this policy may include wallet-linked records, platform activity, and platform-readable reflections of public blockchain activity. This policy describes Yokefellowâs handling of information through the platform and related services. It does not mean that all blockchain activity is private, nor does it replace the other platform documents that describe rights, risks, technical boundaries, and platform terms.
2. Information We Collect
Yokefellow may collect different categories of information depending on how a person uses the platform, what features they interact with, and whether they are acting as a participant, operator, builder, partner, or support requester. The categories below describe the main types of information Yokefellow may collect and process.
2.1 Wallet-linked information.
This may include wallet addresses, connected-wallet state, signed message context, transaction hashes, bucket-linked activity, offering participation records, NFT-related state, YES-related participation or funding state, and other platform records associated with a wallet address. Because Yokefellow includes wallet-linked and contract-backed activity, wallet context is one of the main ways platform activity may be organized and reflected.
2.2 Platform usage information.
This may include pages viewed, app interactions, request timing, device and browser information, IP-based or approximate location signals, session-level interaction patterns, referrer information, error logs, performance diagnostics, abuse-prevention signals, and other technical or usage data tied to operation, security, analytics, or product improvement.
2.3 Support and communication data.
If a user contacts Yokefellow for support or otherwise communicates with Yokefellow, Yokefellow may collect the contents of those communications, related contact details, relevant wallet addresses, screenshots, uploaded files, and technical context needed to investigate, respond to, or document the issue.
2.4 Content and operator-provided materials.
If a user or operator creates a bucket, publishes an offering, uploads a document, posts an update, submits a receipt, fills in profile or settings fields, or otherwise provides content to the platform, Yokefellow may collect and store that content and the metadata associated with it.
2.5 Builder and integration data.
If someone uses a builder-facing or integration-facing surface, including APIs, SDK-connected services, app keys, or related tooling, Yokefellow may collect request logs, route access metadata, credential or integration identifiers, technical configuration details, and operational records needed to support, secure, monitor, and improve that integration surface.
2.6 Public blockchain and derived platform records.
Because Yokefellow is a mixed onchain and offchain platform, Yokefellow may also collect, ingest, index, organize, or reflect public blockchain data relevant to the platform, such as transaction records, contract events, token activity, NFT transfers, collection-linked records, and other public onchain facts. Yokefellow may associate those records with bucket, wallet, offering, entitlement, activity, or participation surfaces inside the platform.
Yokefellow may also generate internal records, inferences, or linked operational data from the categories above where needed to run the platform, keep records coherent, prevent abuse, investigate issues, support users, or improve the product.
3. Information We Do Not Collect by Default
Yokefellow does not automatically know a userâs real-world identity just because that user has a wallet address. A wallet address is public blockchain-facing information, but it is not the same thing as a verified legal identity.
Yokefellow also does not claim to collect every possible off-platform activity tied to a userâs wallet. This policy covers the information Yokefellow collects, uses, or processes through the platform and related services, not every blockchain action, wallet interaction, or third-party activity that may exist elsewhere.
If a user does not provide optional information, Yokefellow may simply have less context rather than a hidden identity profile.
Yokefellow also does not ask users to provide private keys, seed phrases, or wallet recovery phrases through normal platform use. Users should never submit those credentials through support, bucket content, operator surfaces, or any other Yokefellow interface.
This policy should not be read to imply that Yokefellow collects more information than is actually described here simply because a wallet interacts with public blockchain infrastructure. Public blockchain visibility and Yokefellowâs own data collection are related, but they are not the same thing.
4. How We Collect Information
Yokefellow collects information in three main ways.
4.1 First, information collected directly from users or operators.
This includes information a person provides through platform use, such as wallet connections, signatures, support messages, uploaded files, bucket content, offering content, operator-provided records, builder or integration inputs, account or profile details, and any other information entered into a Yokefellow form, tool, workflow, or interface.
4.2 Second, information collected automatically through platform use.
This includes device, browser, log, analytics, session, and performance-related information, as well as information collected through cookies, local storage, and similar browser-side or technical tools where applicable. It may also include request metadata, technical diagnostics, usage patterns, abuse-prevention signals, and other information generated as users interact with the platform.
4.3 Third, information collected from blockchain activity and platform operations.
Because Yokefellow includes contract-backed activity, the platform may collect, ingest, index, organize, or reflect public blockchain data such as wallet addresses, transaction hashes, contract events, token activity, NFT transfers, collection-related records, and similar public onchain information. Yokefellow may then associate or display that information within platform-visible bucket, wallet, offering, entitlement, funding, activity, or participation surfaces.
In some cases, Yokefellow may also receive information from service providers, infrastructure providers, analytics vendors, wallet-related tools, or other technical partners that support the operation, security, monitoring, or improvement of the platform.
The practical rule is simple: some information comes from what users provide, some comes from how the platform is used, and some comes from the public blockchain and the systems Yokefellow uses to make that activity readable and operable inside the platform.
5. How We Use Information
Yokefellow uses collected information to operate, maintain, improve, secure, and explain the platform. The exact use of information may depend on how a person uses Yokefellow and which platform surfaces, tools, or services are involved.
Yokefellow may use information to:
operate bucket, offering, wallet, NFT, funding, market, and related platform surfaces
reflect wallet-linked, bucket-linked, and participation-linked activity in readable platform views
support request, review, queue, issuance, fulfillment, and other operator-managed or system-managed flows
provide account-linked, wallet-aware, app-linked, builder-facing, and integration-facing functionality
respond to support requests, troubleshoot issues, and communicate with users or operators
monitor platform health, availability, indexing freshness, queue health, performance, and operational status
analyze usage, improve usability, improve product quality, and develop new features or tools
detect, prevent, investigate, and respond to abuse, fraud, misuse, security incidents, and technical failures
maintain records, logs, receipts, and related internal operational documentation
comply with legal obligations, regulatory requirements, lawful requests, and enforcement needs
enforce platform rules, policies, disclosures, and Terms of Service
protect Yokefellow, its users, its operators, its partners, and the broader platform environment
Yokefellow may also use information in aggregated, de-identified, or reasonably pseudonymous form where appropriate for analytics, diagnostics, product improvement, research, operational reporting, or abuse prevention.
Because Yokefellow is a mixed onchain and offchain platform, some uses of information involve turning public blockchain activity and platform-generated records into readable product surfaces, operational workflows, and supportable system history. That does not make all blockchain activity private. It means Yokefellow may process and organize relevant information so the platform can function as intended.
6. Wallet-Linked Activity and Public Blockchain Data
Yokefellow is a mixed onchain and offchain platform. Some information reflected in the platform may therefore be derived from public blockchain activity. If a wallet interacts with Yokefellow-related contracts or platform-linked onchain flows, those actions may be publicly visible on the relevant blockchain and may also be reflected inside Yokefellowâs bucket, activity, entitlement, funding, NFT, market, or other wallet-linked surfaces.
This means wallet-linked participation may be visible in more than one place, including:
on the public blockchain
in third-party explorers, wallets, analytics tools, or similar services
in Yokefellowâs own platform surfaces and readable records
Users should understand that public blockchain activity is not private simply because Yokefellow also reflects it in an app. Public blockchain records may remain visible indefinitely and may be accessible to people, services, and tools beyond Yokefellowâs control.
At the same time, Yokefellowâs platform-layer records may organize, group, label, interpret, or make those actions easier to read in context. For example, Yokefellow may connect public transaction activity to bucket history, participation records, entitlement state, queue state, or related wallet-linked surfaces. That added context can make activity more legible, but it can also create additional privacy considerations around how wallet-linked behavior is understood inside the platform.
This policy applies to Yokefellowâs handling of wallet-linked and blockchain-related information through the platform and related services. It does not mean Yokefellow controls the broader public visibility of blockchain activity once that activity exists onchain.
7. Cookies, Local Storage, and Similar Technologies
Yokefellow may use cookies, local storage, and similar browser-side or device-side technologies to keep the platform working, preserve session state, improve usability, remember settings, support analytics, and help monitor platform health, security, and performance.
These technologies may be used for purposes such as:
session continuity
saved interface preferences
wallet-connection support
draft preservation
authentication or access-state support where applicable
app performance and error monitoring
analytics, traffic measurement, and usage understanding
security, abuse prevention, and system integrity checks
Some of these technologies are necessary for basic platform function. Others may support measurement, diagnostics, optimization, or product improvement. Where required by applicable law, Yokefellow will seek consent before using non-essential cookies or similar technologies.
Users can often control cookie and storage behavior through their browser or device settings. However, limiting or disabling some of these technologies may affect how parts of Yokefellow function, including wallet-linked flows, saved drafts, preferences, session continuity, or other platform features.
Yokefellow does not treat browser-side storage as meaningfully private simply because it is stored locally. Users should understand that local storage and similar technologies are part of how modern web applications preserve state and usability across sessions.
8. Analytics
Yokefellow may use internal analytics systems and third-party analytics tools to understand how the platform is used, how users, operators, and builders move through the product, which surfaces are active, where errors occur, and which parts of the experience need improvement.
Analytics may include information such as page views, feature usage, click or interaction patterns, event timing, session behavior, referrer information, technical performance data, error signals, and related usage indicators. Yokefellow may use this information to monitor product health, diagnose problems, improve usability, measure engagement, and make decisions about platform performance and development.
In some cases, analytics may be associated with wallet-linked context, session context, device context, account-linked context, or pseudonymous identifiers where needed to understand how the product is functioning and where users are encountering friction or failure.
Analytics does not mean Yokefellow is automatically attaching a verified legal identity to every wallet or user. It means Yokefellow may analyze platform usage and technical behavior to operate, secure, support, and improve the platform.
Where required by applicable law, Yokefellow will seek consent before using non-essential analytics technologies. Yokefellow may also use aggregated, de-identified, or reasonably pseudonymous analytics data where appropriate for reporting, diagnostics, and product improvement.
9. Support Data
If a user contacts Yokefellow for help, Yokefellow may keep the support request and related records. That may include wallet addresses, email addresses or other contact details, screenshots, uploaded files, messages, notes about the issue, technical diagnostics, relevant account or session context, and the history of the response or resolution process.
Yokefellow may use support data to investigate problems, respond to users, troubleshoot technical issues, maintain a record of past issues, improve product reliability, detect repeated failure patterns, and, where necessary, protect the platform, its users, and its operators from abuse, misuse, fraud, or security incidents.
Support records may be linked to wallet context, bucket context, operator context, or other platform records where needed to understand what happened and respond effectively. Submitting support information may therefore result in that information being associated with other platform data relevant to the issue.
Users should avoid sending unnecessary sensitive information through support channels and should never send private keys, seed phrases, or wallet recovery phrases to Yokefellow.
10. How We Share Information
Yokefellow may share information in limited circumstances where doing so is reasonably necessary to operate the platform, provide requested services, comply with law, enforce platform rules, or protect users, operators, partners, and the platform itself.
This may include sharing information with:
infrastructure, cloud, and hosting providers
analytics, monitoring, and diagnostics providers
customer-support and communications tools
security, fraud-detection, and abuse-prevention providers
blockchain infrastructure, node, RPC, indexing, or related technical providers
development, operational, or integration support providers
professional advisers such as lawyers, accountants, auditors, insurers, or similar advisers
legal, regulatory, law-enforcement, or governmental authorities where required or appropriate under applicable law
a buyer, investor, financing counterparty, successor, affiliate, or other relevant party in connection with a financing, restructuring, merger, acquisition, sale, transfer, or other business transaction involving all or part of Yokefellow or its platform operations
Yokefellow does not need to share every category of information with every recipient. Sharing should be limited to what is reasonably necessary for the relevant service, transaction, legal obligation, protection need, or operational purpose.
Yokefellow may also share information where a user directs Yokefellow to do so, where sharing is necessary to carry out a user-requested action, or where the information is already public by nature, such as certain public blockchain records or publicly visible platform content.
11. Third-Party Processors and Services
Yokefellow relies on third-party processors and service providers to help operate, secure, support, and improve the platform. These providers may process information on Yokefellowâs behalf where needed to deliver the relevant service.
These providers may include services used for:
hosting and cloud infrastructure
databases and storage
analytics and diagnostics
support and communication tools
blockchain infrastructure, node, RPC, indexing, or related technical services
logging, error monitoring, and uptime monitoring
email, messaging, or notification delivery
security monitoring, fraud detection, and abuse prevention
When third-party providers process information on Yokefellowâs behalf, Yokefellow may rely on contractual terms, service commitments, internal review, or other appropriate safeguards to govern that relationship. Yokefellow may update the providers it uses over time as the platform, infrastructure, and operational needs change.
Some third parties connected to the broader Yokefellow experience may act independently rather than as Yokefellow processors. These may include wallet providers, blockchain explorers, external sites, and certain third-party operator or partner surfaces. Their privacy practices are governed by their own terms, notices, and policies rather than this Privacy Policy.
12. Data Retention
Yokefellow may retain information for as long as reasonably necessary to:
operate, maintain, and secure the platform
maintain bucket, offering, wallet, NFT, activity, builder, integration, and support records
comply with legal, regulatory, tax, accounting, or compliance obligations
enforce platform rules, disclosures, and Terms of Service
resolve disputes, investigate incidents, and respond to claims
detect fraud, abuse, misuse, or repeated technical failure patterns
improve product quality, operational integrity, and system reliability
Different categories of information may be retained for different periods depending on their purpose, sensitivity, legal significance, and operational value. For example, operational logs and technical diagnostics may be retained for shorter periods, while support records, compliance records, dispute-related records, and certain platform business records may be retained longer where reasonably necessary.
Public blockchain data may remain publicly visible indefinitely even if Yokefellow no longer actively stores, displays, or maintains a related platform-side copy. Yokefellow cannot delete or alter public blockchain records that exist independently of the platform.
If a user requests deletion, Yokefellow may delete or de-identify information where appropriate, but some information may still need to be retained for legal, security, contractual, operational, recordkeeping, fraud-prevention, or technical integrity reasons. In some cases, Yokefellow may also retain limited information to document that a request was received and how it was handled.
13. Data Security
Yokefellow uses technical, administrative, and organizational measures intended to protect the information it stores or processes. These measures may include access controls, authentication safeguards, logging, monitoring, infrastructure protections, environment controls, vendor management, incident-response practices, and other reasonable operational safeguards designed to reduce the risk of unauthorized access, disclosure, alteration, loss, or destruction.
Yokefellow also works to limit access to information to the people, systems, and service providers that reasonably need it for platform, security, support, legal, or operational purposes.
No system is perfectly secure, and Yokefellow cannot guarantee that information will never be accessed, disclosed, altered, lost, or destroyed by unauthorized parties. Security incidents, software flaws, infrastructure failures, misconfigurations, third-party failures, and malicious activity can still occur.
Users should also understand that the public blockchain portions of the platform have different visibility, permanence, and security properties from private app infrastructure. Information that is public onchain should not be treated as private simply because related platform records are protected by ordinary application security measures.
14. International Transfers
Depending on where Yokefellow, its service providers, and its infrastructure operate, information may be processed, stored, accessed, or transferred in countries other than the userâs own jurisdiction.
By using the platform, users understand that their information may be transferred to, stored in, or processed in other jurisdictions that may have data-protection laws different from those of their home country. Where required by applicable law, Yokefellow will use appropriate safeguards for such transfers.
International processing may occur, for example, when Yokefellow uses cloud infrastructure, support tools, analytics providers, communications tools, security providers, or other service providers that operate across jurisdictions.
15. Childrenâs Privacy
Yokefellow is not intended for children below the age at which they may lawfully use the platform under applicable law. Yokefellow does not knowingly collect, solicit, or process personal data from children where doing so is prohibited by law.
If Yokefellow learns that it collected personal data from a child in a way that requires deletion, restriction, or other action under applicable law, Yokefellow may take steps to delete that information, limit its use, or otherwise respond as required.
If a parent, guardian, or other person believes that a child may have provided personal data to Yokefellow in violation of applicable law, they should contact Yokefellow using the privacy contact listed in this policy.
16. User Rights and Choices
Depending on where a user lives, they may have rights under applicable privacy and data-protection law. Those rights may include the right to:
request access to certain personal data
request correction of inaccurate personal data
request deletion of certain personal data
request restriction of certain processing
object to certain processing
request portability of certain data
withdraw consent where processing depends on consent
appeal certain privacy decisions where required by law
These rights are not absolute. Yokefellow may decline, limit, or condition a request where permitted by law, including where the relevant information is needed for legal compliance, security, fraud prevention, operational integrity, contract performance, dispute resolution, recordkeeping, or protection of the platform, its users, or its operators.
A user seeking to exercise a privacy right should contact Yokefellow through the privacy contact identified in this policy. Yokefellow may take reasonable steps to verify the identity and authority of the requester before responding. Where permitted or required by law, Yokefellow may also request clarification about the scope of the request, deny requests that cannot be verified, or explain the basis for a partial or full denial.
Users may also make some choices directly through their own behavior and settings, such as disconnecting a wallet, limiting optional information they provide, adjusting browser cookie controls, declining non-essential cookies or analytics where such choices are offered, or avoiding participation in bucket, offering, or other platform surfaces they do not want associated with their wallet or activity.
Because Yokefellow is a mixed onchain and offchain platform, users should understand that some information may not be deletable in the ordinary sense. For example, public blockchain activity cannot be deleted by Yokefellow, and some platform records may need to be retained for legal, security, operational, or recordkeeping reasons even after a request is made.
17. Public and Operator-Provided Content
Bucket pages, offering descriptions, documents, posts, receipts, NFTs, metadata, updates, and related materials may be visible to other users or to the public depending on how the relevant platform surface is configured.
Users, operators, builders, and partners should assume that content submitted to public-facing or shared Yokefellow surfaces may become visible to others and may remain visible for as long as that surface, record, or related blockchain activity remains available. People should therefore avoid uploading or publishing private, confidential, or unnecessary personal information unless that disclosure is intentional, lawful, and appropriate for the relevant surface.
Yokefellow may host, display, index, organize, or make readable content that users or operators choose to publish through the platform. That does not mean every such item is private, limited in audience, or removable on demand once it has been made public or tied to public blockchain activity.
Operators are responsible for the content, records, disclosures, and third-party information they provide through Yokefellow surfaces and for handling that information in a lawful and appropriate way. If an operator uploads, publishes, or otherwise uses third-party information through the platform, the operator is responsible for making sure they have the right to do so and that the content is accurate, appropriate, and consistent with applicable law.
18. Changes to This Policy
Yokefellow may update this Privacy Policy from time to time to reflect changes in the platform, its services, its data practices, applicable law, or operational needs.
If Yokefellow makes a material change to this Privacy Policy, Yokefellow may provide notice through the platform, by email where appropriate, or by another reasonable method. The updated version will become effective when posted or on the later effective date stated in the updated policy, except where applicable law requires a different form of notice, consent, or timing.
Users should review this Privacy Policy periodically so they remain informed about Yokefellowâs current data practices. Continued use of the platform after an updated policy becomes effective means the user accepts the updated policy to the extent permitted by law.
19. Contact
Users who have privacy questions, requests, or complaints may contact Yokefellow through the privacy contact or support channel identified on the platform.
Privacy requests, complaints, and rights-related inquiries may be submitted through that contact path, and Yokefellow may take reasonable steps to verify the identity and authority of the requester before responding.
The final published version of this policy should include a specific privacy contact channel, such as:
Email: privacy@yokefellow.io