Security and data answers, without a sales call.
Review how the live service handles tender documents, workspace access, managed AI, payments, deletion, support and product boundaries before you create a workspace.
- Service
- Live controlled workspace
- Payments
- Stripe-hosted checkout
- Submission
- Manual buyer-portal handoff
- Updated
- 2026-07-14
Security posture
Controls implemented in the live product.
The current service is designed for controlled tender work. It does not use certification logos or enterprise claims that have not been earned.
- Provider-managed HTTPS/TLS protects traffic to the public application and APIs.
- Workspace access uses opaque scoped tokens; only hashes or fingerprints are stored server-side.
- Workspace records and document operations are tenant scoped and fail closed when access is missing or invalid.
- Private document bodies are stored separately from workflow, campaign, and evidence ledgers.
- Anonymous notice preview accepts only direct Contracts Finder, Find a Tender, GOV.UK, or Public Contracts Scotland notice pages; account, search, attachment, buyer-portal, credential, and third-party URLs are blocked.
- Checkout is hosted by Stripe and only entitlement metadata is retained by Smart Tenders.
- Secrets and model-provider keys remain server-side and are not exposed to customers or stored in tender records.
- Direct buyer-portal submission, portal credential capture, and autonomous final approval are not enabled.
Certification disclosure: Smart Tenders UK does not currently claim ISO 27001, SOC 2, Cyber Essentials, or other third-party security certification.
Service architecture
Customer documents stay separate from operating and campaign records.
- 1. WorkspaceAn opaque scoped session opens only the authorised workspace.
- 2. MetadataCloudflare-backed workflow records hold bounded tender and audit state.
- 3. DocumentsPrivate document storage holds file bodies outside campaign and workflow evidence ledgers.
- 4. PaymentsStripe handles payment details and returns entitlement state.
- 5. ExportReviewed Word, PDF, ZIP and compliance files are handed back for manual submission.
| Vercel | Customer-facing application hosting and private document storage. |
|---|---|
| Cloudflare | Durable workflow metadata storage and controlled supporting runtime services. |
| Stripe | Hosted checkout, subscription processing, and payment status. Smart Tenders does not store card details. |
| Support and operational email communications. | |
| Brevo | Double-opt-in product updates for people who explicitly request them. Smart Tenders does not add workspace or campaign contacts to this list automatically. |
| Managed AI providers | DeepSeek, Groq, OpenRouter, or Google Gemini receive bounded tender context only when an authorised user requests a provider-backed draft. |
Privacy and data
Collect what the workflow needs. Keep sensitive material out of public and campaign surfaces.
- Workspace metadata
- Work email, company, role, sector, workspace state, plan and entitlement metadata, feedback, and bounded product events needed to operate the service.
- Customer documents
- Real tender documents are accepted only through the protected workspace. File bodies are kept in private document storage; workflow records retain bounded file and audit metadata.
- Campaign analytics
- Attribution uses bounded campaign tags and short nonce hashes. It does not retain email addresses, IP addresses, referrers, user agents, cookies, form values, or private tender content in campaign telemetry.
- Product updates
- An email address and consent metadata are sent directly to Brevo only after the visitor ticks the updates consent box. Smart Tenders does not persist the address in its product or campaign ledgers, and Brevo requires email confirmation before subscription.
- Payment data
- Stripe processes card and payment details. Smart Tenders stores checkout handoff and subscription entitlement metadata only.
- Do not provide
- Do not provide passwords, portal credentials, card data, KYC or banking records, mailbox exports, special-category personal data, or unrelated confidential material.
Retention and deletion
The controlled live release does not claim an automatic fixed retention schedule. Workspace metadata is retained while access is active or until a supported deletion request is completed.
Authorised users can delete documents in the workspace. Stored file content is removed and bounded audit metadata is retained to record the deletion event.
Access, correction, export, or deletion requests are handled through mark@markhay.net. A specific retention requirement can be reviewed before paid onboarding.
Managed AI
Drafting support remains evidence-led and human-controlled.
Customers buy simple workspace credits. They are not asked to configure provider accounts or expose API keys.
- AI output is review-only and is never treated as approved evidence or a final tender answer automatically.
- Provider-backed drafting is initiated by an authorised user and sends bounded question, requirement, official-source, and approved company-evidence context.
- Customer provider API keys are not requested or stored; Smart Tenders manages provider routing and usage credits.
- Generated claims, commitments, missing evidence, and confidence are surfaced for human review before insertion.
- AI cannot unlock final approval, submit to a buyer portal, or guarantee compliance or a successful result.
Product terms
Clear responsibility and commercial boundaries.
- Users remain responsible for checking official buyer documents, reviewing generated or reused content, obtaining approvals, and submitting correctly and on time.
- Smart Tenders does not provide legal, procurement, or compliance advice and does not guarantee suitability, compliance, award, or win rate.
- Founding plans are monthly and may be cancelled for future renewal.
- If the service cannot provide a usable workspace or agreed founding-workspace output during the first paid month, the customer may request a first-month refund review.
- Direct buyer-portal submission is not part of the current service.
Support and data requests
One accountable route for product, billing and data questions.
Supported
- Workspace access
- Document and workflow problems
- Source corrections
- Credits and billing handoff
- Cancellation and export questions
- Product feedback and reasonable data requests
Outside support
- Legal or procurement advice
- Guaranteeing bid compliance or success
- Receiving portal credentials by email
- Acting as the customer's authorised portal submitter
Start without a card, call or private upload.
Paste one official public notice, review the extracted facts and create the first controlled tender pack before deciding whether the workflow belongs in your process.
Create a free workspace