The Four Categories of Materials and Their Boundaries
"Project Memory" is the requirements, project descriptions, product decisions, iteration summaries, selected conversations, selected files and other context that you choose to upload for a designated project, or that forms from project activity within valid authorization. It is not an authorization to collect by default all files on your computer, all chat records, other project materials or third-party account content.
"Private structured materials" are the internal summaries, indexes, vectors, unreleased intent data and other non-public derivatives formed to serve your project. Organizing, vectorizing or tagging raw text does not by itself change its private status.
"Public Project Genome" is a limited structured description — project purpose, functions, interactions, technical categories and the like — extracted from authorized project materials and filtered through public field rules, possibly shown as product genes, intent genes, tags or visual nodes. "Genome" is a metaphor for product characteristics; it does not refer to human biological genetic information and is not used to infer personal health, identity or personality.
"Operational and business data" includes database records, access logs, payment records, real customer materials, uploaded files and Secrets. The Project Memory feature gains no unrestricted permission to read such data, and Public does not make it public by default.
Choices and Confirmation before Collection
The Memory feature may be presented as a recommended feature on the deployment page, but before the first actual upload, storage or sending of Project Memory to a model, PocketBay obtains your valid affirmative confirmation for this feature and describes the data sources, scope, purpose and necessary recipients. Preset selections, silence or unauthorized Agent calls are not valid consent.
You can review the sources and scope of materials to be uploaded and exclude files, conversations or fields that should not be uploaded. Neither the platform nor its tools uses "improving experience" or "safeguarding use" as a blanket reason to collect all accessible materials.
Memory is an optional enhancement. Refusing or stopping Memory processing may make Memory-dependent continuous understanding, retrieval, organization and related enhancements unavailable, but does not block basic deployment and operation that does not rely on such materials. Minimal operational, log or security data genuinely needed by basic services is handled under its own disclosed basis.
Uses of Private Memory
Within the features and scope you choose, PocketBay may store, organize, summarize, retrieve and use Project Memory to provide continuous project understanding, Bayo project assistance, project management, issue diagnosis, private structured-material generation, version continuity and export.
Only when you separately enable public Genome does the platform process the necessary Memory content to generate authorized public fields. Generating internal structured materials without public Genome enabled does not imply consent to publication.
Private Memory is not used by default to provide reconstruction materials to other users, fill other users' conversation context, sell data, conduct behavioral advertising, or train or fine-tune general models for unspecified users. Any proposed new non-essential use is separately announced and requires your corresponding valid choice; refusing does not affect basic deployment or the private Memory services already available.
The platform may process necessary service-operating statistics such as task success rates, resource consumption and error types; it does not use "statistics" as a cover to include private Memory text or derivatives traceable to it in a cross-project content library. Using public Genome for project comparison and discovery follows the public authorization and this policy, not the general service authorization of private Memory.
What "Private" and "Only for You" Actually Mean
Private Project Memory is not opened to the public, Discover visitors, other creators or copy users because the project is Public, and is not distributed with Licensed Copies. By default, only the account that owns the Memory can view, manage and use it through product features; member permissions expressly set by the account owner apply separately.
To provide the features you request, PocketBay systems, necessary authorized personnel bound by confidentiality, and entrusted service providers may still process Memory within the minimum necessary scope — for example, providing inference, storage, troubleshooting, security disposal or performing legal obligations according to permissions. Human support access requires a clear reason, appropriate authorization and access records, except where security or legal obligations lawfully allow no advance notice.
"Private" here means an access and use boundary. It should not be understood as the platform being technically unable to access it, never using entrusted service providers, or already providing end-to-end encryption that has not been expressly promised.
Model Providers and Entrusted Processing
When providing Memory organization, Bayo or Genome extraction, the platform may send the content necessary for the task to the AI models or other processors actually used. The identity of recipients, service purposes, data categories, processing regions, retention arrangements, and whether providers have their own training or other independent uses, are as stated in the Data Processing Addendum and Subprocessor Notice and the platform's actual disclosures.
Entrusted parties are bound by appropriate confidentiality, security and purpose limitations. Authorization for the Memory feature alone is not permission for model providers to use private content for their own general-model training. For providers or interfaces that cannot meet this policy, the platform does not send private Memory merely on the strength of this authorization; it adjusts routing, disables the corresponding processing, or — where lawful — offers a separate express choice.
Nothing in this section represents that the platform has achieved any unverified "zero retention", "no third party ever retains anything" or security certification. Public disclosures stay consistent with actual provider contracts, account settings and data flows.
Default Genome Publication for Public Projects
For new Public projects, the deployment page may recommend enabling public Genome by default and, after you confirm the publication settings, display Genome within the limited field scope. The page prominently notes that full Memory stays private and that only the project characteristics extracted from it and passing the public rules will be shown to the public.
The range of publishable fields is listed on the deployment page or in directly accessible field notes — for example, app purpose, target use scenarios, published features, interaction types and technical categories you permit to be public. Fields that could identify customers, disclose strategies or reveal unpublished roadmaps are not automatically published merely for being "product descriptions".
Raw conversations, full Memory, private indexes/vectors, passwords and keys, real user data, unpublished business metrics, unauthorized third-party information, trade secrets and internal implementation details are not part of the default public Genome. The platform does not hand unfiltered structured Memory to the frontend as a whole and control visibility only by hiding interface elements.
Automatic Extraction, Preview, Correction and Publication Limits
Genome is generated by AI or rule-based systems and may be inaccurate, omit context or misidentify sensitive content. The platform applies reasonable measures such as limited fields, sensitive-content checks and access-permission isolation; you can preview, correct, hide or disable public Genome.
Automatic generation does not by itself prove content is free of personal information or secrets. Where fitness for publication cannot be confirmed, high-risk fields are detected, or a legally required separate consent has not been obtained, the platform withholds the relevant fields from publication, offers a private preview or leaves them empty, rather than publishing first and waiting for complaints.
Where content intended for publication involves a natural person's personal information, applicable legal requirements are assessed. Where individual separate consent is required, the valid separate consent of the individual concerned must be obtained; you cannot consent on behalf of all conversation participants, customers or team members merely through your own deployment tick. The platform may directly exclude the relevant fields to avoid unnecessary publication.
Your review does not replace the reasonable security, privacy and error-correction obligations the platform itself must perform.
Public Search, Comparison and Non-public Business Metrics
Authorized public Genome may be used for Discover search, recommendations, similar-project matching, on-platform comparison, project-relation display and non-sensitive aggregate analysis formed from these public fields. That an ordinary user can see public Genome does not mean a licence to the source project, the full intent package, source code or trademarks has been granted.
That a project is Public does not mean its revenue, orders, paying users, conversion, retention, cost or backend traffic data is public. Using such non-public metrics for public rankings, Product Space or benchmarks traceable to a single project requires a separate express explanation and corresponding authorization.
Model training, private projects joining cross-project content analysis, full reconstruction-package downloads and bulk data sales are not included in the default public uses above; if introduced in the future they will be handled separately.
Stopping, Withdrawal and Deletion
You may stop further Memory uploads, disable public Genome, and request access to, correction of, deletion of or delivery of your own materials through the available account entry points or support@pocketbay.com. The platform performs necessary identity and permission verification.
Disabling the Memory feature stops new processing by default; deleting existing Memory requires performing the deletion or submitting a deletion request. Deletion covers the related original Memory, private summaries, retrieval indexes and vector copies, not merely the user-interface entry points. Disabling public Genome also removes the public display, caches and retrieval entry points within the platform's control.
A limited set of materials that must be retained by law or is genuinely needed to process accrued billing, disputes or security incidents is subject to express purpose, permission and time limits; during retention it will not be used for incompatible generation, publication or commercial purposes. Deletion in backups follows the disclosed rotation cycles, with safeguards against restored data becoming available or public again. For specific categories, retention periods, deletion and backup rotation arrangements, the platform's published data-retention statement prevails.
Export and Migration
You may obtain your own Project Memory and corresponding materials through the features provided or by lawful request. Formats, batch capability, extra migration support or non-essential premium processing may be charged under disclosed plans, but statutory rights to access, copy and other personal-information rights are not refused merely because you have not purchased a membership. Any necessary fees permitted by applicable law are communicated separately.
Export does not transfer intellectual property in third-party material, models or components, and does not guarantee restoring a fully identical app, dependencies, database state or model behavior on another platform. Handing an export package to another platform or Agent creates a new data flow; users should confirm its permissions and third-party processing arrangements.
Security Incidents and Rights Requests
PocketBay implements technical and organizational measures proportionate to the risk and, upon discovering unauthorized publication, Memory leakage or cross-account access, takes reasonable blocking, investigation and remedial measures and performs the required notification and reporting obligations by law. If you discover a suspected leak, you can report it via support@pocketbay.com with the project identifier and affected scope, avoiding attaching unnecessary sensitive text again.
No security disclaimer excludes the responsibility PocketBay bears for its own breach of contract or statutory obligations.
Policy Changes
Where new data sources are added, uses expanded, public field categories increased, previously private content opened to third parties, or other changes requiring renewed consent by law occur, the corresponding notice and confirmation process is completed before the change takes effect. Merely updating a web page, notifying users, or continued use does not automatically replace legally required renewed consent.