Jon Croft Privacy Policy
Last updated: 13 November 2026
This policy explains what personal data Jon Croft collects, why, who we share it with, how long we keep it, and the choices and rights you have. It covers joncroft.si, app.joncroft.si, and the Jon Croft Slack app (the "Service").
1. Who we are and how to reach us
- Ascendant Media Strategies - FZCO, Building A1, Dubai Digital Park, Dubai Silicon Oasis, Dubai, United Arab Emirates. DSO trade licence no.: 70341. UAE VAT TRN: 105245549800001.
- Privacy requests and questions: support@joncroft.si (please put "Privacy request" in the subject line).
- Security issues, including suspected data breaches: security@joncroft.si
- Data protection officer: we have not appointed one.
1A. Where Jon Croft is offered
Jon Croft is not offered to businesses established in the European Union or the European Economic Area (EEA), and we do not target or market to people there. If we learn that an account belongs to a business established in the EU/EEA, we may close it and delete its data. If your personal data reaches us because a customer's workspace includes you (for example, you are in a Slack channel where Jon Croft is used), please contact that customer first; you can also write to us at support@joncroft.si.
2. Two roles: controller and processor
- We are the controller for data about our customers and visitors that we use to run our business: account details, billing, security logs, support emails, and usage records.
- We act as a processor (service provider) for the content your workspace puts into Jon Croft: prompts, messages, files, Slack messages Jon Croft can see, data from connected services such as Meta ad accounts, memory, and outputs. Your organisation (the workspace owner) is the controller for that content and decides what goes in. If you are a person whose data appears in a customer's workspace (for example, a colleague in a Slack channel), please contact that organisation first; we will help them respond. Our Data Processing Addendum (DPA) forms part of our Terms for business customers and applies automatically; no separate signature is needed.
3. What we collect
| Category | What exactly | Where it comes from |
|---|---|---|
| Account | Name, email address, password (stored only as a hash), email-verification status, workspace name, role (owner/admin/member), language and appearance preferences | You |
| Single sign-on (if used) | Identity details your company's sign-in provider sends us | Your identity provider |
| Workspace content | Conversations, prompts, AI outputs and reasoning summaries, uploaded files, generated files (charts, CSVs, PDFs), sandbox code and results, saved skills, schedules, and "memories" you ask Jon Croft to keep (stored with a vector embedding) | You and your workspace members |
| Slack data | Slack team ID, an encrypted bot token, Slack user IDs linked to Jon Croft accounts, and the text and files of messages in channels where Jon Croft has been added and mentioned, in threads it is part of, and in direct messages to it | Slack, when your admin connects it |
| Meta ads data (when connected) | An encrypted access token; ad account IDs and names; campaign, ad set, ad and performance data (spend, CPA, ROAS, etc.); before-and-after snapshots of changes; spend-cap records | Meta, when you connect it |
| Other connected services | If you connect other business tools (such as Google Workspace, Notion, or HubSpot) through our integrations provider: connection credentials (OAuth tokens and API keys) and the data you ask Jon Croft to read from or send to those tools | Those services |
| Billing | Stripe customer ID, plan, subscription status, credit purchases and balance, billing name and address and tax ID (collected by Stripe Checkout). We do not see or store full card numbers. | You, via Stripe |
| Usage and credits | Each AI model call (model, tokens), sandbox time, tool calls, credits charged, per-task receipts | Generated by the Service |
| Security and anti-abuse | Login attempts and lockouts, session records, audit log of actions and approvals, email domain and a random device identifier used to stop repeat free trials, verification-email rate limits | Generated by the Service and your browser |
| Technical logs | IP address, browser/user agent, request logs kept by our hosting provider | Your device |
| Referrals | Referral code used at sign-up and the link between referrer and new workspace | You |
| Support | What you send us | You |
We do not knowingly collect special category data. Please do not put it into the Service unless agreed. The Service is not for children. We do not knowingly collect personal data from anyone under 18 (or the age of majority where they live, if higher). If we learn that we have, we will delete it. Tell us at support@joncroft.si.
Data we receive but do not use: Slack sends us event data (for example IDs and metadata of events in channels Jon Croft is in, and app install/uninstall events). We use it only to route the request and to avoid processing the same event twice, and we do not use it for any other purpose.
4. Cookies and similar technology
| Name | Type | Purpose | Lasts |
|---|---|---|---|
joncroft_session | Cookie, HttpOnly, first-party | Keeps you signed in | 30 days |
oidc_state | Cookie, first-party | Protects single sign-on against forgery | Duration of the sign-in |
joncroft-device | Browser local storage | Random ID to stop the same device claiming free trial credits repeatedly | Until you clear it |
We found no analytics, advertising, or tracking cookies in the app.
5. How we use data and our legal bases
For users in the UK, the legal basis under the UK GDPR is shown in brackets.
- Provide the Service: create accounts, run tasks, answer in Slack, run code, keep memory, run schedules, connect services (contract).
- Billing and credits: charge, grant credits, issue invoices, handle refunds and disputes (contract; legal obligation for tax and accounting records).
- Security and abuse prevention: lock accounts after failed logins, rate-limit, stop trial abuse, keep audit logs, investigate misuse (legitimate interests in keeping the Service and users safe).
- Service emails: verification emails and alerts (for example when a schedule keeps failing) (contract). We will not send marketing email without consent where consent is required, and never to email addresses obtained through Slack without explicit consent.
- Support and improvement: respond to you, fix bugs, measure cost and margin per task type (legitimate interests). We use aggregated usage data, not the content of your conversations, to improve the Service.
- Legal: comply with law, respond to lawful requests, enforce our Terms (legal obligation; legitimate interests).
No training. We do not use your content, or any Slack data, to train AI models. We do not sell or "share" personal information for cross-context behavioural advertising, as California law defines those terms, and we do not pass identifiers to advertising or attribution partners. AI providers: see section 6.
No automated decisions with legal effect. Jon Croft does not make decisions about you that have legal or similarly significant effects. Its outputs and suggested actions are reviewed by the people using it; consequential actions (such as Meta ad changes) need human approval.
Under UAE law (Federal Decree-Law 45/2021), where processing is not covered by an exception such as performing a contract or a legal obligation, we rely on your consent.
6. AI processing
To answer you, Jon Croft sends the relevant parts of your conversation, files, memory, and tool results to AI models through OpenRouter, which routes them to model providers such as Anthropic, OpenAI, Google, DeepSeek, Mistral, and Perplexity (depending on the model chosen and the task, for example image generation, transcription, or web research). Embeddings for memory may be created through the same route. You are interacting with an AI system, not a person.
7. Who we share data with
We share personal data only with:
- Sub-processors that host and run the Service (hosting, database, AI routing and models, payments, email, file storage, and connections to the third-party apps you choose to link). The current list, with what each receives and where, is in our Sub-processor list. We give customers 30 days' notice of new sub-processors, and they can object, as set out in the DPA.
- Services you connect (Slack, Meta, others). When Jon Croft posts in Slack or changes a Meta campaign at your request, data goes to that service under its terms.
- Other members of your workspace, for shared (not private) conversations.
- Authorities or others when the law requires it, to protect rights and safety, or in a merger or sale of our business (with notice).
We do not sell personal data.
8. Where data is stored and international transfers
We are based in the UAE. Customer data is hosted primarily in the United States. Some of our service providers, including AI model providers and our email forwarding provider (which relays email sent to our @joncroft.si addresses through infrastructure in France), may process data in other countries. See our sub-processor list.
From the UK. Your data is transferred to the UAE (where we are) and to the US (where our providers host it). Support email may also pass through France, which the UK treats as providing adequate protection. The UK has not made adequacy regulations for the UAE. We protect these transfers as follows:
- Customers: our DPA includes the UK Information Commissioner's International Data Transfer Agreement (IDTA).
- Our US providers: we rely on their certification under the UK Extension to the EU-US Data Privacy Framework where they are certified, or put the IDTA (or the UK Addendum to their standard clauses) in place.
- Account and billing data that we control: we rely on the safeguards in our provider contracts, and on the UK GDPR exception for transfers necessary to perform our contract with you (Art. 49(1)(b)), where that applies.
You can ask for a copy of these safeguards at support@joncroft.si.
From the UAE. Transfers outside the UAE rely on.
9. How long we keep data
| Data | Kept for |
|---|---|
| Account | While your account exists; deleted with your workspace or on request |
| Sessions | 30 days, or until you log out |
| Workspace content (conversations, files, memory, Slack messages) | Until deleted by you, by the workspace owner's retention setting (1 to 3,650 days, applied by the owner), or with the workspace. Memories tied to a connection are deleted when that connection is removed. |
| Slack tokens and links | Until Slack is disconnected, the app is uninstalled, its access is revoked, or the workspace is deleted |
| Meta tokens and ad data | Until Meta is disconnected, a deletion request, or workspace deletion |
| Billing, invoices, credit ledger | |
| Audit logs and security records | |
| Backups | |
| Data at AI providers |
When an owner deletes a workspace, we remove its database rows, stored files, and sandbox directory, and detach the Stripe customer. When we receive a verified deletion request, we delete the data from live systems within 30 days. Backup copies are removed as backups expire. After a customer's contract ends, we keep workspace content for up to 30 days so the customer can export it, and then delete it, unless the law requires us to keep it.
10. Your rights
Depending on where you live, you can ask to access, correct, delete, export (portability), restrict, or object to our use of your data, and withdraw consent at any time. Owners can export or delete a workspace from settings. For anything else, email support@joncroft.si. We will reply within one month (UK GDPR and UAE law) or 45 days (California), and may need to verify your identity. We do not discriminate against you for using your rights.
- UK: you can complain to us at support@joncroft.si, and we will acknowledge your complaint within 30 days. You can also complain to the Information Commissioner's Office (ico.org.uk).
- California: you have the rights to know, delete, correct, and opt out of sale/sharing (we do not sell or share), and to limit use of sensitive personal information (we use it only to provide the Service, for example login credentials). You may use an authorised agent.
- UAE: you have rights under Federal Decree-Law 45/2021 including access, correction, erasure, restriction, objection, and portability.
Deleting data from Slack
A Slack admin can uninstall the Jon Croft app from Slack, and a workspace owner can disconnect Slack in Jon Croft settings. When the app is uninstalled or its Slack access is revoked, we automatically delete the Slack thread content Jon Croft stored for that Slack workspace. You can also delete your own Jon Croft account at any time in your account settings, and a workspace owner can delete conversations or the whole workspace. For anything else, email support@joncroft.si.
Deleting data from Meta (Facebook Login)
To delete the data Jon Croft holds from your Meta account:
- In Jon Croft, open workspace settings and choose Disconnect Meta ads.
- Or remove Jon Croft in Facebook under Settings & Privacy > Settings > Apps and Websites and send a deletion request.
- Or email support@joncroft.si with the subject "Meta data deletion". We will delete the token, the ad account list, and stored ad data within 30 days, and confirm by email.
11. Security
Highlights: tenant data separated with database row-level security; Slack, Meta and integration tokens encrypted with AES-256-GCM; passwords hashed; HttpOnly secure cookies; login lockout after five failures; code runs in an isolated per-workspace sandbox; audit log that cannot be edited. No system is perfectly secure. We will notify you and regulators of a personal data breach as the law requires.
12. Changes
We will post changes here and update the date. For material changes we will notify account holders by email or in the app.
13. Contact
support@joncroft.si (privacy requests) · security@joncroft.si (security) · Ascendant Media Strategies - FZCO, Building A1, Dubai Digital Park, Dubai Silicon Oasis, Dubai, United Arab Emirates.