How Aegispeak Handles Your Data On This Site
This page explains how Aegispeak uses cookies and similar technologies on our website, and how we process personal data collected through forms, subscriptions and analytics.
It covers website data only. For client engagements, NDAs and security architecture work, we use stricter controls that are set out in our contracts and data processing addenda.
Answers You Can Trust Short, straight answers to the questions we hear most from fintech and cloud-native teams.
What Data We Collect On The Website
-
Who is Aegispeak for?
Aegispeak works best with:
Fintechs, wallets, BNPL and payment platforms
SaaS products that handle card, PII or financial data
Cloud-native teams already shipping to production and scalingIf you’re dealing with PCI DSS, SOC 2, KYC / AML or bank / investor due diligence, you’re in the right place.
-
What types of services do you offer?
We focus on four core service lines:
Fintech Security Architecture Reviews
API & Microservices Security
Fraud & Transaction Monitoring
KYC / AML & Compliance IntegrationEach has a dedicated service page with scope, steps and deliverables.
-
How do we get started?
Three simple options:
Book a 30-minute review call from the hero/CTA.
Send us context via the Contact form (stack, current concerns).
We’ll propose scope, timeline and a fixed-fee quote.No long discovery project, just enough information to scope the first engagement properly.
-
Do you only work with fintech companies?
Fintech and payment-heavy platforms are our primary focus, but we also work with:
SaaS products that store or process sensitive data
Marketplaces and platforms with complex payment flows
Cloud-native B2B products that need PCI / SOC 2-aligned controlsIf your risk looks similar to a fintech stack, we can usually help.
Scope & Deliverables
-
What’s included in a Fintech Security Architecture Review?
A typical review includes:
System context and data-flow diagrams
Threat mapping for key payment and account flows
Risk-ranked issue list with clear owners
Recommended patterns for auth, tokens, secrets and logging
PCI / SOC 2-aligned control mapping for the reviewed scopeYou receive everything as a reusable pack your engineers, leaders and auditors can share.
-
How is API & Microservices Security different?
API & Microservices Security zooms in on:
Public and internal APIs, gateways and service-to-service calls
AuthN/Z models, rate limits and abuse-case defence
Secrets management and configuration hardening
OWASP API Top 10 and common fintech logic flawsWe map where traffic really flows and where attackers will actually hit you.
-
What do you cover in Fraud & Transaction Monitoring?
We look at:
Your risk signals: events, metadata, behavioural patterns
Rules, models and thresholds across vendors and internal engines
Case management flows, queues and SLAs
Reporting for banks, partners and regulatorsThe goal is fewer surprises and less “mystery” around declines, chargebacks and fraud losses.
-
What about KYC / AML & Compliance Integration?
Here we focus on how:
Identity, sanctions and transaction-monitoring vendors fit together
High-risk journeys (onboarding, top-ups, payouts) trigger checks
Results flow back into your product, risk and support tooling
Evidence is captured in a way regulators, partners and auditors can useWe don’t replace your vendors; we help you make them work as one coherent system.
Process & Timeline
-
How long does a typical engagement take?
For most architecture-level reviews:
Small / focused scope: 2–3 weeks
Broader / multi-product scope: 4–6 weeksWe’ll give you a more precise estimate once we understand your stack and priorities.
-
Do you need production access or customer data?
Usually no.
We work primarily from diagrams, configs and non-production data.
If log or event samples are needed, we prefer them anonymised.
Any exceptional access is agreed upfront and kept to the minimum necessary.We design around privacy and least privilege.
-
Can you work fully remote?
Yes. Most engagements are remote-first:
Workshops and reviews via video calls
Shared whiteboards and diagramming tools
Secure document and artefact sharingOn-site sessions can be arranged where there’s a clear benefit.
-
What do we need to prepare before you start?
It helps if you can share:
A list of key products / journeys (e.g. signup, checkout, payouts)
Existing diagrams or architecture notes (if they exist)
Current security / compliance goals or pain points
Any incidents, near-misses or upcoming auditsIf you don’t have diagrams yet, that’s fine – we’ll help you build them.
Pricing & Commercials
-
How do you price your work?
We prefer fixed-fee pricing per clearly defined engagement, based on:
Scope and complexity of your stack
Number of critical journeys and systems in review
Depth of analysis and deliverables requiredYou get a written proposal with scope, timelines and price before you commit.
-
Do you offer retainers or ongoing support?
Yes. Many clients start with a focused review and then move to:
A light retainer for periodic check-ins and design reviews
Ad-hoc follow-up support during implementation
Additional modules (e.g. API security or fraud stack review)We’ll shape something that matches your roadmap and team capacity.
Security, Confidentiality & Compliance
-
How do you handle confidentiality?
We’re used to working with sensitive systems and data. As standard:
We sign NDAs before going into detail.
Artefacts are stored in restricted, access-controlled locations.
We avoid copying production data and minimise any personal data.For regulated clients, we can align with your vendor-security or procurement processes.
-
Can you help us get ready for PCI DSS or SOC 2?
Yes. Our goal is to design controls that actually work for engineers, then map them to frameworks:
PCI DSS (especially for card-not-present platforms)
SOC 2 (Security, Availability, Confidentiality)
Support for ISO 27001 / 27002 alignment where relevantWe’re not a QSAC or audit firm; we make sure your architecture, controls and evidence flows can stand up to one.
-
Do you provide documentation we can show auditors and investors?
Yes. Your deliverable pack can be used as:
System and data-flow diagrams
Threat model and issue register
Control descriptions and mappings
Evidence plan for logging, monitoring and access controlMost clients treat this as their internal “source of truth” for audits, onboarding and future redesigns.
Data, Privacy & Legal
-
What data about me do you collect through the website?
On the site we collect only what we need to respond and improve:
Contact details you submit in forms
Email addresses for newsletter sign-ups
Aggregate usage and performance metricsFor full details, see our Privacy Policy and Cookies & Data Processing pages.
-
Do you use my data for advertising or selling to third parties?
No.
We do not sell your data to third parties.
We don’t run third-party ads or re-targeting campaigns.
Any third-party tools we use (e.g. analytics) act as processors under our instructions.Again, details live in the Privacy Policy and Cookies pages.
-
How can I update or delete my data?
You can:
Unsubscribe from emails using the link in any message we send.
Contact us through the Contact page and request an update or deletion.We’ll confirm your request and act within a reasonable timeframe, subject to any legal retention requirements.