Privacy
Privacy notice
How RJL Solutions, LLC handles the personal information you give us through this site and the Ontology Studio. Effective on release of this update, version 14 October 2026.
Who we are
This site is operated by RJL Solutions, LLC, a New Jersey limited liability company (“RJL”, “we”, “us”). For any privacy question or request, write to rwhite@rjlsol.com or to RJL Solutions, LLC, Five Greentree Centre, 525 Route 73 North, Suite 104, Marlton, New Jersey 08053.
What we collect, and why
- Working session and Studio access requests. Your name, email, organization, optional role, the request type, situation and message you write, plus the first page you visited on this site and the site that referred you, so we know which pages are useful. We use them to review and reply to your request, send an approved Studio invitation, or prepare and hold a working session and send its written summary. Requesting access does not subscribe you to marketing updates or automatically create an account.
- Studio feedback. The category, task and feedback you enter, plus your email only if you choose to provide it. We use these to investigate problems, prioritize improvements and follow up when needed. The form does not attach Studio projects, documents, account records, screenshots or API keys automatically. Please use non-confidential descriptions. Feedback does not subscribe you to updates.
- Whitepapers and updates. Your email address and subscription choice, used to send the updates you request. Reply to any update or email us to unsubscribe.
- Email you send us. What you choose to include, used to reply.
- The diagnostic. Your answers stay in your browser and are not sent to us. If you choose to continue to the contact form, the summary is copied into the message box, and it reaches us only if you submit the form.
- Ontology Studio, local work. Local file uploads are read in your browser. Collections, draft terms and practice records stay there; full backups and exports are files you download yourself. Optional public-page retrieval sends the requested URL through our hosted service and contacts the source website. Optional AI drafting sends selected evidence and request instructions through our hosted service to the provider you choose, after you confirm the destination and possible API charge.
- Ontology Studio, invited accounts. Cloud accounts are offered only by invitation after we review an access request or meet through an RJL workshop. For each account we keep the email address and name, sign-in records held by our account provider, the account’s creation date and any access end date, and the version and time you accepted the Studio cloud terms. We also keep the projects you choose to save and any read-only share links you create. We use this only to provide the Studio to you. Saved projects should contain business meaning, not personal data; the terms explain what not to store.
- Selected cloud model content. Research collections and practice records are excluded from cloud saves. Accepted private business-meaning excerpts can enter the model you choose to save. Hosted read-only shares filter private evidence; downloaded exports remain under your control. Review each selection before saving, sharing or exporting.
- Provider keys. You may enter a request-only API key or, when the optional account vault is enabled, explicitly save a connection for future visits. Request-only keys are not saved automatically. Saved keys are encrypted separately from projects using AWS Key Management Service in a configured United States region; encrypted records are held in Netlify storage in the United States. AWS processes the credential for encryption and decryption. The server can decrypt it for provider operations you request. Keys are excluded from project exports, share links, account reports and ordinary application logs. We keep limited connection metadata: provider, saved/replaced date, last request dates and safe outcome, and last reported generation token counts. Read the Saved AI Connections policy before opting in.
- Technical data. Our hosting provider processes standard request data, such as IP address, browser type and the pages requested, to deliver and secure the site.
We do not use advertising or analytics cookies, and we do not track you across other sites. Please do not send confidential client information, or personal information about other people, through the forms.
Who we share it with
We do not sell or share personal information for cross-context behavioral advertising, and we do not rent or trade mailing lists. We use service providers to run the site and our email, including Netlify, which hosts the site, receives form submissions and provides the Ontology Studio’s accounts and storage. If you choose AI drafting, the selected evidence reaches OpenAI or Anthropic through our hosted request service; the provider applies its own API terms and retention policies. Selecting a provider does not authorize sending your entire collection. AWS Key Management Service provides managed encryption for optional saved AI connections. Privileged service operators can technically control decryption; access is restricted to authorized operational, security or legal purposes. We may disclose information if the law requires it, or to protect our rights.
How long we keep it
We keep form submissions and correspondence for as long as needed to respond and to keep ordinary business records, and remove subscription addresses from the mailing list when you unsubscribe. Ontology Studio accounts have no automatic 90-day expiry. Chosen cloud projects remain until you or an administrator delete them, or the service ends with notice. We keep minimal account and cloud-activity metadata to operate and review the service: account email, role, creation and login dates, last authenticated cloud activity, project counts, last save date and share-link counts. Authorized Studio administrators can view this information on an access-controlled administration page and choose to download a CSV report. No scheduled account-report emails are sent. The report excludes project content, document passages and API keys, and does not track guest or local-only work. If an account is ended, we retain a short email/date record to prevent unintended reactivation. You can delete your cloud projects yourself at any time, or ask us to delete your information. Optional saved AI connections remain until removed or replaced, the account is deleted, or RJL removes them for an operational or security reason. Signing out does not delete them. Removal makes a key unavailable for new Studio requests; it does not revoke it at the provider or cancel an already-started request. Account deletion removes vault records, and restored access does not restore deleted keys. The vault retains current connection metadata and bounded recent request identifiers for safeguards, rather than a detailed prompt history. Residual encrypted copies in infrastructure backups or replicas follow provider retention and deletion processes; immediate erasure from every copy is not promised.
Your choices and rights
You can ask to access, correct or delete the personal information we hold about you, or to stop receiving whitepapers and updates. Depending on where you live, including some U.S. states, the United Kingdom and the European Union, you may have further rights, such as to object to or restrict processing. Write to us at the address above, and we will respond within the time the applicable law requires. We will not treat you differently for making a request.
Security and transfers
The site is served over an encrypted connection, and we limit who can see submissions. No method of transmission or storage is completely secure. Our service providers may process information in the United States and other countries. Ontology Studio cloud projects are stored in the United States, encrypted at rest and in transit by our hosting provider.
Children
This site is for business professionals and is not directed to children. We do not knowingly collect personal information from anyone under 16.
Changes to this notice
If we change this notice, we will post the new version here with a new effective date.