PositionLab · Bone-Dawg Studios LLC
Privacy Policy
Updated November 2, 2026 · Educational preview
How PositionLab handles account information, saved settings, community contributions and feedback.
Operator: Bone-Dawg Studios LLC, Illinois, United States ("we", "us", or "our"). This policy covers the PositionLab website and simulator at positionlab.net. It explains the current account-and-password version; future services may require updated disclosures.
- Guest preferences stay in your browser. Signed-in settings can be saved with your account.
- Community saves are public and include your login name. Personal settings are separate.
- Feedback is sent when you choose to submit it. A support report is prepared locally for you to review.
- Use synthetic educational information only. Do not enter patient information.
1. Information we handle
| Category | Information and purpose |
|---|---|
| Account and sign-in | Chosen login name, account identifier, salted password hash, account creation and last-login times, and session records. These support account access and security. The application stores password hashes rather than plain-text passwords. |
| Account settings | Saved keyboard shortcuts, named camera views, view-cycle choices, navigation order, workspace layout, sensitivity, camera-help preference, viewer appearance, scene colors, lighting and theme. Settings include a revision and update time and support access across devices. |
| Community activity | Published simulated patient/equipment configurations, position names, contributor login names and save times; account-linked votes and leaderboard activity. These support the shared position library and one vote per account per save. |
| Feedback and correspondence | Your message, any name/email you choose to supply, submission identifier and receipt time. We use this to review problems, improve PositionLab and respond when appropriate. |
| Security and connection information | Authentication uses short-lived hashed network/name rate-limit keys. Hosting providers may process IP addresses, browser/device information and request logs to deliver and protect the service. |
2. Browser storage and cookies
Guest preferences and temporary recovery information are stored in your browser. Existing guest settings are not automatically assigned to the next signed-in user; the application offers an explicit import option. Temporary account-specific recovery records remain on the device. Explicitly saved sessions also remain in this browser, separated by account, until replaced or cleared through browser controls. They are loaded only when you choose Load session; opening the lab starts fresh. Student answers, grades and exposures are not included in the account-settings upload described here.
Signing in uses a session cookie. It is marked Secure and HttpOnly and expires after seven days unless revoked earlier. Signing out revokes that session.
You can clear local records through browser controls. Doing so does not delete settings already saved to your account. Blocking cookies or storage may prevent sign-in, preferences or recovery features from working.
3. Public community contributions
When you save a community position, its setup, position name, your login name and save time are available to other users. Shared saves and vote totals contribute to leaderboards. Previous saves may remain in the public position history. Choose a login name and contribution names that you are comfortable displaying publicly.
Personal settings are not part of community saves. Do not include patient information, private information about another person or content you are not authorized to share. Other people may retain copies of information you make public.
4. Feedback, captures and diagnostics
Submitting feedback sends the text you enter, including any optional name or email. The feedback record does not automatically append your account identity, IP address, browser details, screenshot or current pose. Hosting logs are separate from that feedback record.
The feedback form preserves an unsent draft within the current tab when you close and reopen the dialog. Reloading or leaving the lab discards that unsent draft. Successful submissions are stored in the hosted database and may be copied into the operator's restricted review records.
Image capture saves a PNG to your device; that capture action does not upload the image. The support tool prepares a local diagnostic report containing build, browser, display and basic WebGL information. You can review it before downloading or deciding to share it. The diagnostic tool does not automatically transmit the report.
5. Service providers and other disclosures
Providers supporting hosting, database storage and business records may process information to help operate PositionLab. The current workflow also copies new login names and signup dates into an operator-controlled Google Sheet; passwords and password hashes are not included in that export. Feedback may be copied into restricted operator review records.
We may disclose information when legally required, to address fraud or security incidents, to protect legal rights, or as part of a business transfer subject to applicable obligations.
6. Advertising, analytics and payments
The simulator described here does not include advertising scripts, analytics tracking or payment collection. Hosting services may keep separate connection logs.
7. How long records remain
There is currently no published deletion schedule for account settings, community history, feedback, signup exports, hosting logs or backups. If you want a record removed, tell us which account, contribution or feedback message you mean. We can explain which copies we can identify and what can be removed.
The sign-in session lifetime is seven days. Expired authentication records are cleaned up during authentication requests, so expiration does not necessarily mean immediate physical deletion. Clearing your browser does not erase server records, exported copies or backups.
8. Requests and choices
You can change preferences through the application, clear local browser storage and choose whether to publish a community position or submit feedback. For privacy questions or requests concerning access, correction, account closure or deletion, contact customerservice@positionlab.net.
We may need proportionate information to verify that you control the relevant account. Never send your password. Your rights and any exceptions depend on applicable law; nothing here limits mandatory rights.
9. Audience and educational information
PositionLab is intended for users aged 18 or older. Do not submit information about children or real patients. A school or institution should arrange an appropriate agreement and data review before providing student records or using account-linked activity as part of an institutional service.
The simulator's educational subject matter does not by itself establish any particular health-data or student-record compliance status. Do not use it to store patient records or make decisions about an actual patient's care.
10. Security, external sites and updates
No online service or storage method is completely secure. We use password hashing and session cookies to protect account access. If you follow a link to another website, that website's practices apply to your visit.
When our practices change, we will update this notice and its effective date and provide additional notice or obtain consent where required. A future policy update does not authorize us to disregard commitments made when information was collected.
11. Contact
Bone-Dawg Studios LLC
Illinois, United States
Privacy contact: customerservice@positionlab.net