Least privilege
Connect only the records and actions a workflow needs. Review integration scopes and tool permissions before enabling access.
Security principles
Keep access clear. Keep people in control.
The principles that guide responsible setup and review. This page makes no certification, audit or compliance claim.
Authorization at the boundary
An interface or a model-generated instruction is not authorization. Sensitive actions should verify identity and permissions at the service boundary.
Separate reads and writes
Keep reading context separate from creating tasks or changing plans. Require approval where an action changes a commitment or affects other people.
Source-aware review
Keep source records and assumptions available alongside generated answers. Treat content from tools and documents as data, not as authority.
Data minimization
Collect only the details needed for a stated purpose. The public sales form asks for contact and team context to respond to an inquiry.
Controlled rollout
Discuss access, retention, logging, integration availability and incident contacts before production setup. Confirm specific controls in your service agreement.
Have a security question?
Share your requirements with the Stark team. Ask for evidence of the controls relevant to your intended use before making a purchasing decision.
Talk to salesThe public website
Know where your inquiry goes.
The contact form stores the details you submit in the site’s connected cloud database. It confirms success only after the request has been saved.
Public database access is limited to submitting the permitted inquiry fields. Anonymous visitors cannot read submitted requests through the application. Workspace processing and production controls should be confirmed separately during setup.
Meridian · illustrative workspaceFor review
Decision brief
A clear boundary for a sales request
01
You provide
Contact details, company and team context, and the message you choose to share.
02
The site stores
An inquiry for the Stark team to review. The success state confirms storage, without promising a response time.
03
Public access
Visitors can submit an inquiry. The public interface does not expose other visitors’ requests.
Do not include passwords, payment information or sensitive project records in a public inquiry.
Workspace due diligence
Bring your requirements to the setup conversation.
| Requirement area | Questions to resolve |
|---|---|
| Identity & access | How are invited users identified? Which resources and operations can each role access? Who can revoke a connection? |
| Data handling | Which records are processed, where are they hosted, and which providers support the proposed service? |
| Retention & removal | What retention periods and deletion processes apply to workspace data, logs and connected records? |
| Operational controls | What logging, review and incident contact arrangements apply to the intended workflow? |
| Evidence & agreements | Request the evidence relevant to your requirements and confirm specific commitments in the applicable service agreement. |
Questions & answers
A few useful answers.
Can anyone read my sales request?
Public visitors do not have read access to the submitted inquiry records. The request is stored for authorized review by the Stark team and its service providers as described in the Privacy Policy.
Does this page claim a certification?
No certification or audit claim is made here. Ask the team for evidence of the controls relevant to your intended use.
Can I send confidential workspace data in the form?
Use the form to describe requirements at a high level. Do not send secrets or sensitive records. Agree on an appropriate process before sharing regulated or confidential workspace data.
Ship what you promised.
Bring the plan, the work and the next decision together.