OpalSpan: optional customer case communications instruction

Version: dpa-instructions-en-2026-11-01-v11. Applicable supplement: dpa-en-2026-11-01-v11. Privacy supplement: privacy-en-2026-11-01-v11. Purpose: customer_case_communications_v1.

Use prospectively only with the attributable feature instruction identifying the existing underlying DPA/order binding and all three exact supplemental copies/hashes. This copy does not alter an earlier signed instruction or establish another person's authority by publication.

Ready IT ApS, CVR 38769383, Denmark; contact@readyit.dk.

Your limited instruction

You may choose optional case-specific service communications to an explicitly selected device owner, case customer or responsible contact. The three useful moments are work started, a meaningful update and work finished with a short explanation. No message is sent by default or on every internal event. Cases remain optional for device work overall.

Instruct only the necessary recipient name/address, responsibility and case/message identifiers; deliberately shared title and plain-text update; company/signature and verified reply information; and minimum instruction, review, submission, link, preference and recovery records. Do not include credentials, unrelated controllers' information, full internal prompts/conversations, command/log transcripts or arbitrary attachments. Additional sensitive categories need their independently applicable lawful instruction and safeguards.

The company determines an appropriate service recipient and lawful basis. A visible contact record is not permission to send. A deliberately reviewed responsible person's name/address can be used without an automatic directory or case mutation. Where you act for another controller, these instructions remain within your actual authority and that controller's instructions, including the applicable disclosed subprocessing and transfers.

One optional workspace instruction

The attributable acceptance statement is:

I enable optional case-specific customer communications for this workspace under its identified processing agreement and these exact supplemental instructions. I am authorised to instruct Ready IT ApS to process the selected recipient and message data for this purpose, including the disclosed AWS SES processing in eu-north-1 and recipient-scoped bearer/preference links. Anyone holding or forwarded a live case link can view the deliberately shared fields until expiry or revocation; recipient scoping is not authentication of the intended person. Where I act for another controller, these instructions remain within my authority and that controller's instructions.

The protected feature review identifies the workspace, human actor identity/authority and version, request, settings revision, existing underlying DPA/order binding, all three supplemental identifiers/hashes, provider/retention binding, this purpose, confirmation and UTC acceptance instant. The authority statement is part of that one review, not a new buyer-kind/controller questionnaire.

Missing publication/binding, refusal or lack of authority leaves real delivery and customer-link activation off. Company setup, message drafting and truthful human-private previews remain available. Earlier holders are not deemed to accept by purchase, installation, continued use or a saved checkbox. New orders retain the existing signup/Checkout journey and use the same optional feature instruction when required.

Exact message decision and agent routes

Each send separately shows the selected recipient, responsibility, case, actual platform sender, company branding, verified reply address, frozen rendered email and the customer-safe page for an attributable human confirmation. The website's trusted decision or Mech's controller Confirm is consumed inside admission. An agent may prepare, inspect model-safe content/digests and request the human review; a digest or model assertion never supplies consent.

Raw bearer/preference tokens and full rendered mail HTML stay out of model-facing Mech/CLI summaries, generic results and logs. Human-private website previews may receive the exact frozen content. Closing a preview, requesting an answer or refusing mail does not end independently authorised device work.

A committed dispatch claim prevents replay. Provider acceptance is not inbox delivery; no automatic mailbox/bounce observation is added. Read the original receipt after uncertainty rather than repeat that send. Genuinely independent messages and device work remain subject to their own current authority, not a blanket hold from an unrelated uncertain record.

AWS SES transport and shared links

The selected customer/device-owner transport is AWS SES API v2, through the existing verified opalspan.com domain in AWS account 270208331408, Stockholm/eu-north-1. Provider binding is aws_ses. One fixed authorised OpalSpan platform From identity is shown separately from the company's body/signature branding and verified selected member reply address. The feature's fixed platform From is OpalSpan updates@opalspan.com, admitted only with actual runtime sending authority. This is not a receiving service and grants no arbitrary shared-address verification, wider IAM/sender permission or workspace From-name override.

AWS receives the frozen addressed communication, minimal submission metadata and any included usable links. The recipient's own mail provider receives it too. The applicable AWS agreement, GDPR DPA, supplementary addendum and applicable SCC/alternative transfer terms govern this expressly instructed SES purpose and its supplier chain. The ordinary Danish-account contracting route is Amazon Web Services EMEA SARL, with the DPA's identified parties. An EU API region is not a promise of EU-only mail delivery, support or onward access; no zero-retention or end-to-end mail-encryption assurance is introduced.

The SDK submits once without automatic request retries. SES may perform its own delivery/queue handling after provider admission; that is not a repeated application send. Provider acceptance does not prove inbox delivery. Existing SES feedback forwarding and provider-level bounce/complaint controls are distinct from OpalSpan's case-scoped preference. No mailbox-read permission, receiving mailbox or new automatic bounce/complaint processing is introduced. Human-reported actual recipient return remains separate from provider authentication, throttling, content or service rejection.

A case capability restricts content to the deliberately shared fields for the reviewed case/audience, not the identity of the person opening it. Anyone holding the link, including someone to whom it is forwarded, can view those allowed fields until expiry/revocation. The default is seven days, bounded from one to thirty days. Full internal cases, other recipients' messages, conversations, prompts, commands/logs, secrets and unrelated files are never granted by it.

The separate preference capability exposes no case content and only stops optional updates for its own workspace/case/normalised recipient. No GET, mail-security prefetch or preview changes the preference. An administrator cannot silently lift recipient_opt_out. The feature does not add open/click tracking, SES contact-list marketing or customer data in tags. Existing Microsoft member/billing mail and Auth0 authentication mail/credentials keep their previous purposes and permissions.

Records, ending use and unchanged authority

Link expiry/revocation prevents later reads; it does not recall email or material already obtained. SES creates no Exchange Sent Items copy or receiving mailbox; AWS queue/delivery/security/operational, recipient and backup retention remain distinct. No account-specific SES erasure interval is verified or newly promised. Existing case/workspace records, recovery copies and the applicable return/deletion instructions determine retention; this instruction introduces no new erasure timer.

Use contact@readyit.dk for a specific rights/return/deletion/restriction instruction identifying the affected scope and your authority. Existing DPA assistance and statutory rights remain intact. Disabling future email and revoking an already shared link are separately named actions.

This instruction adds only the expressly disclosed customer-purpose use of existing AWS SES. It changes no customer price, plan, buyer type, device permission, telemetry profile, other mail purpose, AWS pricing plan, account, fee or mailbox-read permission. New credentials/IAM permissions, DNS/configuration resources, receiving service or wider sender identity require their own actual authority; Auth0 no-reply credentials are not reused. One reserved operator decision may select/publish the exact SES copies and name the prospective purpose/provider configuration without a second operator activation-approval ladder. It does not authorise a specific live test/customer send. Real sending additionally requires the applicable active workspace instruction, current access and verified reply, unchanged frozen content, no applicable suppression and that message's human decision.