PUBLIC WEBSITE · FREE TECHNICAL BETA
Privacy Policy
Effective October 7, 2026 · Last updated October 29, 2026
Who handles the data
OBSIDIAS Labs is the project name used by its operators (the Obsidias Desk). No incorporated legal entity has been formed. For privacy questions and requests, email desk@obsidiaslabs.com.
What this policy covers
This policy covers the public website and the portal features described below, together with communications and invited beta testing where provided. The current beta is free and PAPER-only. It does not describe a launched live-trading or paid subscription service.
Public website and contact
Visiting the website sends ordinary request information to the hosting service, such as an IP address, requested URL, browser information, and request time. Hosting and security providers may process this information to deliver and protect the website.
The current public website has no application analytics tracker, advertising pixel, or application cookie/local-storage feature in its page code. This does not mean hosting providers receive no request data. The animated market boards and sample News Desk messages on the homepage are page demonstrations; they are not connected to your brokerage account.
If you email us, we receive the information you choose to send, including your email address and message. The homepage can open a questionnaire followed by an embedded Calendly scheduler. Scheduling contact details and a random booking reference are passed to Calendly when that scheduler loads, before a booking is confirmed, as described in the Book a Call section below. Direct booking links also open Calendly under its own privacy policy.
Book a Call questionnaire
Before you pick a time, the homepage asks a short questionnaire. We collect your contact details (name, email and, if you choose to give it, phone number) and your answers about your trading experience, setup, goals and what you would like help with. The two money questions are optional and include “Prefer not to say”.
When you submit the questionnaire, we use Cloudflare Turnstile to prevent automated submissions. Cloudflare processes security signals from your connection and browser, such as your IP address, browser information and the site where the check runs. We send the resulting verification token to Cloudflare and keep your contact details and questionnaire answers out of that verification request. Cloudflare Turnstile Privacy Addendum
After verification, OBSIDIAS saves the contact details and questionnaire answers you submit so we can prepare for your call. Please leave out account numbers, passwords, API keys and other unnecessary sensitive information.
We send your name, email, optional phone number and a random booking reference to Calendly when its scheduler loads. Calendly processes that information under its privacy policy. The reference connects your questionnaire to the booking and contains no answers.
When you confirm a booking, we prepare a private notice for the OBSIDIAS team from an OBSIDIAS Gmail account. If we verify the match and can prepare a readable PDF, the notice includes your complete questionnaire.
If we verify a match and the questionnaire cannot be rendered, we pause that private notice. We alert an operator using a reference to the held notice and keep the questionnaire private under the retention periods below. The private notice may be delayed or may remain unsent. Your Calendly booking can still proceed.
You can also book directly through Calendly without completing the questionnaire. A direct Calendly booking, expired or reused reference, or changed booking email may leave the questionnaire unavailable. In that case the private notice contains only booking details and says the questionnaire is unavailable. Calendly also sends its normal booking notices. If you reschedule after the private notice has been sent, Calendly's reschedule notice provides the new time.
Retention
Unbooked questionnaires are eligible for deletion after 48 hours. The booking reference can be used for a booking made during its first 24 hours. A further 24-hour period accommodates delayed booking events.
Matched questionnaires, stored booking details and prepared notice copies are eligible for deletion from the application after 30 days. A limited record can remain for 90 days to prevent duplicate notices. Accepted sends, linked reschedules and unresolved attempts may retain identifiers and proof of the attempt for longer while an operator resolves or retires them.
Email copies in the onboarding operators' mailboxes, Calendly records and provider backups have separate retention. We do not sell questionnaire information.
Email desk@obsidiaslabs.com to request access, correction or deletion. We may need enough information to locate and verify the request. Please do not send credentials.
Portal account and access records
The portal uses Supabase for authentication, account data, and supported file storage. Sign-in processes an email address and password through the authentication service. Registration, where enabled, also accepts a name. Authentication and session records, including session cookies, support login and access control.
Portal profile and access records include account identifiers, name where supplied, access/license status, and confidentiality-acceptance date and document version where applicable. The deployed code can read a billing-customer identifier and license-period fields; their presence in the data model does not mean free-beta participants are being charged. Downloads and announcements are made available according to the portal's access controls.
Cloudflare Turnstile is used for portal anti-abuse checks. Cloudflare processes the request, browser, and challenge information needed for those checks, and the resulting challenge token is passed to the authentication service. Hosting services also process ordinary technical request and error information.
Invited PAPER testing and planned connections
Where invited PAPER testing is enabled, testing can involve a paper-account identifier, test configuration, worker/status information, simulated orders, fills, positions, balances, reconciliation, and operational/audit records. The information processed depends on the specific test and features enabled. These records concern simulation and do not establish live-trading availability.
Alpaca OAuth is planned and is not currently available through this website. This policy does not represent that an OAuth token-collection flow has been implemented or approved. Before such a feature is enabled, its requested permissions and actual data handling must be explained through the implemented connection flow and an updated policy where needed.
Do not include brokerage passwords, raw API keys, or access tokens in support messages. A portal password is different from a brokerage password.
Why information is processed and who receives it
Information is used to deliver the website, authenticate portal users, administer invited access, provide enabled features, run and review authorized PAPER tests, investigate errors or abuse, and respond to communications and requests.
Service providers receive the information needed for their roles: Vercel for hosting; Supabase for portal authentication, database, and supported file storage; Cloudflare for anti-abuse checks; email service providers for correspondence; and Calendly when you choose its booking service. Alpaca receives information through any separately enabled and authorized PAPER testing involving its service. A website logo alone does not mean data is sent to that platform.
These providers may process information in locations outside your jurisdiction under their own service arrangements. Provider-specific processing and retention details are available in their privacy notices. We may also disclose relevant information when required by applicable law or to address misuse and protect access. This policy does not promise that information never reaches another provider or is processed only in a particular country.
Retention and security
We have not established a single published retention period for every account, support message, test record, log, and provider backup. Records can remain for account administration, support, test review, incident investigation, and applicable legal requirements; provider copies and backups can have separate retention. Contact us about a specific record or a deletion request. This policy does not promise immediate deletion or deletion from every backup.
The implemented portal uses authenticated sessions and access checks. No security certification, perfect protection, or breach-free service is promised. Do not send unnecessary sensitive information in email.
Requests and choices
Email desk@obsidiaslabs.com to ask about your information or request access, correction, a copy, deletion, or account closure. You do not need to create a new account to send a privacy request. We may need to verify your identity before acting on account information; do not send passwords or credentials to verify it.
Requests are reviewed by the operators and handled subject to applicable rights, verification, and lawful retention requirements. If you disagree with our response, reply to the same email to request reconsideration and ask about the complaint options available in your jurisdiction. This policy does not limit rights provided by applicable law or promise an automated request process.
Closing a portal account, ending a PAPER test, and revoking a third-party authorization are separate actions. Ask for the instructions applicable to your enabled test or connection; do not assume an email request immediately stops activity.
Changes and future services
Updates will be published here with an updated effective date. Future OAuth, paid services, or material changes to data use will need updated disclosures and any consent required before those changes are enabled. This policy does not authorize those future features.
OBSIDIAS LABS