Overview
Tape B Cloud is an independently operated, pre-launch conversational market-data service available through a private web beta and private AI-platform connections. This policy describes what the Tape B service itself handles. AI, market-data, and infrastructure providers handle information under their own policies.
Beta recruitment waitlist
Recruitment submissions are temporarily paused. The website does not currently accept new waitlist registrations. With your affirmative consent at registration, Tape B Cloud collected your email address, primary interest, optional preferred AI platform, consent-notice version, and registration time. Earlier registrations may retain a self-reported brokerage-account ownership answer under the notice accepted at registration. The operator may also record recruitment status, relevant recruitment notes, and the time of an administrative update. We use existing details only to administer recruitment, assess beta suitability, and email recruitment updates or invitations under the original consent. Registration is not an invitation, a brokerage connection, or permission to access brokerage-sourced data.
Existing registrations are stored in a separate SQLite recruitment database on the existing Railway persistent volume. The database is restricted to the service’s operating-system user and authorized infrastructure administrators; there is no public list or export endpoint. The operator uses an authenticated private register to search and manage recruitment records and download private CSV exports. We do not send recruitment details to AI models or market-data providers, and do not store them in website browser storage or source control. OpenAI Sites and Railway process submissions as hosting providers; their infrastructure may process request metadata under their own policies.
We retain recruitment details while the January 2027 recruitment process is active and delete them within 90 days after that recruitment closes, unless you separately agree to continued contact. You can withdraw consent, stop recruitment emails, request correction, or request deletion at any time by emailing support@tapeb.cloud from the registered address. We may verify your request before making changes. Backups and infrastructure logs are subject to the hosting providers’ retention practices.
Existing registrations retain their original details, registration time, and consent notice. The pause does not withdraw existing consent or extend the retention period. No payment is required. Do not submit brokerage credentials, account numbers, financial balances, or API tokens.
Information you submit
When you use the private web beta, Tape B receives your invitation code, your affirmative Terms-acceptance request, and your market question. OpenAI or Anthropic receives the conversation context and relevant tool results for the selected analytical rigor. Tape B calls its permitted tools on the user’s behalf; the invitation code is not sent to the inference provider. When an AI platform calls a Tape B tool directly, Tape B receives the structured information needed for that tool. Depending on the request, this may include ticker symbols, timeframes, indicator settings, and scan settings.
Tape B does not ask for or need your brokerage password, brokerage account number, trading credentials, balances, positions, or order history. Do not put that information into a Tape B request or support email.
How information is used
Tape B uses tool inputs to retrieve the requested public-market data, perform the requested calculation or analysis*, and return a result to the conversational interface. The public beta sends allowlisted read-only requests to Twelve Data. Raw provider responses are normalized before Tape B returns a result.
Storage and retention
The web beta sends conversation context and tool results to its inference providers to generate responses. OpenAI requests use the API storage setting disabled. Provider safety, abuse-monitoring, and infrastructure retention are governed by the applicable provider policies; Tape B does not control those practices. Conversation state is encrypted into an opaque token returned to the open browser tab; the service does not create a server-side conversation record, and closing or refreshing the tab clears the conversation from the interface.
Invitation codes are compared on the server and used for short-term abuse limits. The application does not intentionally log invitation codes, prompts, market queries, or returned market results.
To document contractual assent, Tape B stores an opaque one-way identifier derived on the server from the authorized invitation, a server-generated acceptance time, the accepted Terms version, immutable document identifier and content hash, acceptance-event schema version, acceptance status, and whether the currently configured Terms require reacceptance. A separate acknowledgment records the privacy disclosure revision and acknowledgment time against the same opaque identifier. This acceptance record does not contain the raw invitation code, an IP address, a user-agent string, conversation text, or market requests. It remains for the period reasonably needed to document the accepted Terms and administer beta access.
Cloudflare and Railway are in the service request path and may process or record infrastructure information such as request timing, errors, and IP-related metadata under their own practices. Tape B does not control their platform retention rules.
Service providers
- OpenAI and Anthropic process web-beta conversation context and relevant tool results for inference. Their respective policies govern their processing and retention. Do not submit private financial information.
- Cloudflare hosts the public website and proxies web-beta requests. OpenAI operates ChatGPT when a user connects Tape B there.
- Railway hosts the Tape B market-data tools.
- Twelve Data supplies the limited, real-time, non-consolidated U.S. equity data used by the web beta.
- GitHub hosts private source repositories and may participate in source-based deployment. Tape B does not intentionally send tool inputs or market results to GitHub.
Recruitment submissions are paused. The website uses optional Google Analytics as described in this policy. Analytics runs only after you allow it. We do not use advertising pixels.
Optional website analytics
If you choose “Allow analytics,” our existing Google Analytics property measures visits to the overview, recruitment, and launch pages only. While recruitment is paused, the website generates no registration events. It stays off the private beta and legal/support pages. Declining does not affect beta access. No analytics script loads before permission. You can withdraw permission using “Analytics preferences” at the bottom of any page; this disables further measurement and removes the website’s Google Analytics cookies.
For the launch campaign, we may record a source label limited to X, Bluesky, Threads, Instagram, TikTok, Discord, or direct visits on the homepage and launch page, and clicks on configured official follow links. Approved source labels may also populate Google Analytics campaign-source fields, with fixed campaign and organic-social labels. Arbitrary query values are discarded. The launch page does not collect email addresses or feedback.
Google Analytics may process page paths and titles, device and browser information, request metadata including your IP address, and first-party cookie identifiers under Google’s policies. We do not send email addresses, recruitment answers, AI-platform preferences, invitation codes, or consent-form contents to Google Analytics. Page-location fields omit query strings and fragments, and referrers are suppressed. Advertising storage, advertising personalization, and Google signals are disabled by this integration. Do not include personal details in website URLs.
Your allow/decline choice is saved in this browser’s local storage; recruitment answers are not. After permission, Google Analytics sets cookies according to the property configuration. Google’s account-level data-retention settings apply to analytics; the repository does not establish the currently configured retention period. See Google’s Privacy Policy.
No sale of personal information
Tape B does not sell personal information. Tape B does not use tool inputs for advertising or to build marketing profiles.
Security
Tape B uses technical controls intended to limit the service to market-data operations, including strict tool schemas, an allowlist of provider endpoints, normalized outputs, encrypted storage for the operator’s provider token, and no trade-execution functions. No online service can guarantee absolute security. A compromise of the running service or its hosting account could expose information available to that environment.
Your choices and requests
You can remove a Tape B price alert through the available alert-removal tool. For a deletion or privacy request, email support@tapeb.cloud with enough detail to identify the request. Tape B may need to verify that a request is legitimate and may not be able to delete information controlled only by a third party.
Third-party privacy practices
Review the policies of the services you use with Tape B:
- OpenAI Privacy Policy
- Anthropic Privacy Policy
- Cloudflare Privacy Policy
- Google Privacy Policy
- Railway Privacy Policy
- Twelve Data Privacy Policy
- GitHub General Privacy Statement
Tape B does not control those services or their privacy practices.
Changes to this policy
This policy may change as Tape B develops or its providers change. The updated policy will be posted here with a revised effective date. Material changes will apply prospectively unless a different approach is required by law.
Contact
Questions about this policy may be sent to support@tapeb.cloud.