Privacy Policy
How MyTCLab handles local lab records, account sync, payments and feedback.
Effective October 17, 2026. MyTCLab is operated by MyBasic LLC in Marietta, Georgia, United States. This policy covers mytclab.com, its Academy and the MyTCLab workspace.
What stays on your device
The workspace saves plants and cultivars, batches, culture records, equipment profiles, shelf locations, observations and attached photos in browser storage. Academy progress, quiz results, theme and interface preferences can also be saved locally. A service worker caches public application files for offline use. Public application caching does not cache account or payment API responses.
Local-only records are not automatically published or sent to MyBusinessTree. Clearing browser storage, using private browsing, losing a device or uninstalling an app can remove unsynced work. Export your records and protect access to your device. Signing out separates account caches; it does not securely erase every local backup or downloaded file.
Accounts and synchronization
Clerk provides authentication. Account information can include your identity-provider identifier, name and email address. Authentication resources may load when the workspace initializes, even before you sign in. If you choose Google sign-in, Google also handles that sign-in under its own policies.
When you choose account synchronization and have the required access, records you synchronize are stored on our server, with device identifiers, record versions, synchronization cursors and pending-change information used to maintain your account. We use account-specific caches to keep different users' work separate. Browser-stored signed ownership or identity proofs allow a previously verified account to reopen its own cache offline. These proofs are not payment-card details.
MyTCLab and MyBusinessTree are related services with separate account configurations. Visiting the music catalog does not automatically publish or synchronize your lab records to MyBusinessTree.
Payments
Stripe handles checkout and payment-card processing when purchases are available. We receive purchase identifiers, payment status, product/version entitlement information and refund events needed to provide access and support. MyTCLab does not collect full card numbers through its own forms. Sales may remain paused while acceptance checks are completed.
Feedback and support
Submitting feedback sends your selected category, subject, message, current app section and app version to our server and private support inbox. A reply email is optional. Browser and screen details are included only if you select the diagnostics checkbox. Lab records and photos are not attached automatically; information you put in the message is sent as part of it.
Resend delivers support emails, and the support inbox is handled using Google Gmail. Server security controls may process your IP address and request information to limit abuse. Avoid sending passwords, payment-card details or confidential research that is unnecessary for your request.
Providers and external links
We use hosting and backup services, Clerk for identity, Stripe for payments, and Resend/Google for support email. Some pages or features load third-party fonts or libraries, including Google Fonts, jsDelivr or cdnjs; those services can receive normal browser request information such as IP address. These providers process data according to their service terms and policies.
The optional music control opens an embedded MyBusinessTree player on this page. The player loads only after you open the panel and does not start audio automatically. MyBusinessTree receives normal browser request information and handles its own cookies, playback events, accounts and purchases under its policies. MyTCLab does not send lab records to the player. We do not sell or rent your lab records or share them for third-party advertising.
Retention and deletion
Local data remains until you remove it, your browser clears it, or an account/cache action changes which copy is active. We retain account records as needed to operate the service and handle support, security, purchases and legal obligations. Support messages remain in support email systems as needed for those purposes. Backups and security records can remain after deletion until their retention or rotation processes remove them; deletion is not an instant purge of every backup.
The account deletion control removes MyTCLab's active server records and retains a minimal deletion marker. It does not automatically delete the underlying Clerk identity, every provider's payment record, support emails or copies on your devices. Local account caches may remain parked as backups. For broader identity, privacy or deletion requests, use the private request form below. Download your exports before requesting deletion.
Your choices and requests
You can use the free local workspace without creating an account, choose whether to synchronize, export records, turn optional feedback diagnostics on or off, and manage cookies and site data in your browser. Depending on where you live, you may have additional rights to access, correct or delete personal information. We may need information to verify that a request concerns your account; do not send passwords or complete card details.
For a privacy request, open the private feedback form. No sign-in is required to send a request. We will consider requests under applicable law and explain relevant limits rather than promising rights or deadlines that do not apply.
Children, security and updates
Accounts, purchases and feedback are intended for adults. Families may explore public educational materials with adult guidance. We do not knowingly collect personal information from children under 13; a parent or guardian should manage family accounts and contact us if a child has submitted personal information.
We use access controls, HTTPS and account separation to protect information, but no service or device is completely secure. Providers may process information in the United States or other countries where they operate. Material changes will be reflected in this policy's effective date, with additional notice where required.
Related: Cookie Policy · Terms of Service.
