Opt-in connection
Koreshield applies only to a Melaya workspace whose authorised administrator chooses to connect it. Other Melaya users are not enrolled in Koreshield and do not need a Koreshield subscription merely because they use Melaya.
Verified launch and attribution
Melaya's backend requests an authenticated, customer-specific launch link from Koreshield. The link is bound to the intended email address, expires after 10 minutes, and can be consumed only once. Koreshield records Melaya attribution only after verifying and consuming that token. A reusable public signup code does not qualify.
Customer authorisation
After signing in or creating an account, a Koreshield workspace owner must separately confirm contractual authority and authorise the Melaya connection. Koreshield records the versions accepted and the time of that decision. The owner then creates a dedicated scan-only API key and transfers it to Melaya. Koreshield shows the secret once and does not store it in browser local storage.
Three checks, one scan-only connection
The dedicated key can submit only input, retrieved-context, and proposed-action scans. It cannot administer workspace policy, read retained evidence, manage billing, or act in the customer's downstream systems. Melaya decides where the three checks run and controls its own timeout, retry, fail-open or fail-closed behaviour and user messaging.
Data and responsibilities
Koreshield processes scan requests under the customer's Terms and DPA. Hash-only storage is the default. Melaya remains responsible for its application, model, connectors, execution controls, and its own notices to users. Koreshield returns a decision; it does not execute a proposed action.
Disconnecting
A workspace owner can revoke the dedicated API key in Koreshield. Melaya can remove the connection from its workspace. Revocation stops future authenticated scans but does not alter records that must remain under the configured retention period or applicable law.