Privacy notice

1. Information used by this website

The authored pages have no scripts, forms, analytics, tracking cookies or embedded external content. They load their images and styles from this site. Ordinary links to provider and regulator pages make no automatic connection to those sites.

Railway hosts the preview on the existing service in EU West (Amsterdam, Netherlands). Its infrastructure processes technical requests from your browser. Documented HTTP records include source IP address, browser information, host and page requested, time, response status, request identifier and duration. The authored page server writes startup or failure messages, not per-visitor request logs; this does not prevent Railway's processing. See Railway's HTTP-log information.

2. Contacting us

If you email the public contact, you provide your email address, any name or contact details you include, and your message. The operator and the providers delivering and storing business email can handle that correspondence. It may also be reviewed through the operator's separate Outlook/Codex workflow; sending an email is not a promise that it will never be handled with AI assistance.

Contact is voluntary. Share only what is needed for the enquiry or request. Do not send passwords, one-time codes, payment-card details or unnecessary confidential information. This website offers no secure document-upload or account-export form.

3. Purposes and lawful bases

For the limited website, our legitimate interests are delivering these pages reliably, diagnosing access problems and protecting the service from misuse. Technical connection information is needed to serve a request; we do not add behavioural advertising, visitor profiles or an authored analytics service.

For ordinary correspondence, our legitimate interest is answering the enquiry you choose to send. Where data-protection law requires us to handle a rights request or complaint, the relevant processing is for that legal obligation. We use the minimum information needed and may request proportionate identity confirmation where necessary to protect another person's data.

The local owner application processes information for the tasks its owner requests and the Microsoft access explicitly authorised. Microsoft permission consent is a permission to access that account; it does not by itself establish a lawful basis for every use of another person's information. The owner must have an appropriate basis and share only necessary evidence. No blanket consent or customer-contract basis is claimed for this preview.

4. The separate local Joe 90 application

The existing Microsoft integration requests basic account profile access (User.Read), read-only mail (Mail.Read) and calendar (Calendars.Read) permissions, and offline_access for maintaining the authorised sign-in. Bounded Graph reads can return subjects, sender details, calendar metadata and structural classifications. The current tool results exclude raw mail bodies, previews, full URLs and authentication headers; metadata can still contain personal or sensitive information.

Requested voice and agent work can send audio, delegated transcript text and relevant approved tool results to OpenAI. The app has no automatic customer mailbox, quarantine, message-sending or sharing-change service. A configured owner review schedule does not prove that an unattended review or notification succeeded; broader scheduled Agents exports remain held for specific approval.

Microsoft account and token information, session recovery and job data stay in private local files; jobs may retain task and result text. These files have owner-only permissions but are not encrypted by the app. Browser captions and results are held in memory; an explicit download saves displayed text locally.

Disconnecting Outlook removes this app's local account/cache and pending sign-in state. It does not revoke Microsoft consent or delete Microsoft, OpenAI or host conversation records. Remote permissions and retained sessions must be managed with the relevant provider. See Microsoft's privacy statement and OpenAI API data controls.

5. Recipients and international processing

The current website uses Railway hosting. Contact correspondence uses the operator's business email and, where used, its separate AI-assisted workflow. Microsoft and OpenAI process the local application's authorised account and requested session activity. Supabase, Stripe and a public Joe plugin backend are not connected to this website.

Amsterdam is the website workload location, not a promise that every provider record stays in the EU. Railway's published Data Processing Addendum describes primary US processing, separate provider-controller and customer-processor roles, and transfer safeguards including standard contractual clauses and a UK Addendum or an applicable Data Privacy Framework route.

The relevant Railway account agreement and applicable transfer safeguard have not yet been verified. The public document is not evidence of an executed account-specific agreement. Microsoft and OpenAI have their own processing locations and controls; no UK-only processing or zero-retention guarantee is made here. Ask the public privacy contact for information about the applicable safeguards.

6. Retention

Railway's log documentation lists a 30-day Pro history window; its Use Cases documentation describes service-log storage for up to 90 days. These are not a verified deletion deadline for all HTTP, security or account records. Other records follow Railway's published retention criteria, including operational need and legal obligations. We do not promise deletion after 30 or 90 days.

The retention criterion for operator-held correspondence is the time needed to deal with the enquiry, document the response and meet any applicable legal obligation or dispute requirement. Review and removal are manual; no automatic email-deletion timer is implemented by this site.

The local application has no automatic expiry for its private recovery and job files. The owner should retain only what is needed, while preserving recovery evidence until remote outcomes are known. Clearing a screen or local cache does not delete provider-held records. Provider retention depends on the product and account controls in use.

7. Your rights and complaints

Where UK data-protection law applies, you may request access, correction, erasure or restriction of your information, subject to the applicable conditions and exemptions. Data portability and withdrawal of consent apply where their legal conditions are met; not every right applies to every record.

Send privacy requests or complaints to mark@smarttmedia.com. The operator handles rights requests, normally within one calendar month, subject to the applicable verification, clarification and extension rules. Data-protection complaints are acknowledged within 30 days and investigated, with progress and outcome provided without undue delay. These are operator responsibilities; the website has no automated request or complaint system. Information held independently by a provider may also need a request to that provider.

You can complain to the Information Commissioner's Office about use of your personal information. You do not need to give up that right by contacting us first.

8. Future services and this version

This site does not collect plugin excerpts or subscriber records, take payment, make automated eligibility decisions or inspect your device. Customer identity, paid membership, hosted voice and monitoring will need their own verified arrangements and updated privacy information before activation.

This notice is dated 1 October 2026. It records the confirmed operator/contact and current processing, with provider-contract limits stated openly. It is not a compliance certification or Microsoft verified-publisher approval.