// Security
AI products touch private data: email, receipts, payments, calendars. These are the practices every CODELANK build follows, with the shipped projects that show them in use.
AI features that read private data are built on retrieval-augmented generation. Documents and email are indexed inside your system and only the relevant slice is sent to the model for a given question. ExecLens, a CEO briefing tool that reads company email, is built this way.
Seen in ExecLens
Marketplace payments run through Stripe and are held in escrow until the job is delivered. Tune4Tune holds the buyer's payment until the artist completes the dubplate.
Seen in Tune4Tune
Every multi-user build has explicit roles. On Freight KPI, warehouse managers can only enter and view their own site while administrators see both. Admin-only API routes check the role on the server, not in the interface.
Seen in Freight KPI
Sign in issues a JWT stored in an HTTP-only, secure cookie so scripts on the page cannot read it. Passwords are hashed with bcrypt. Repeated failed logins lock the account for a cooling-off window.
Stripe webhooks are checked against the signing secret before any order is marked paid, and paid events are applied once even if Stripe retries.
API keys, database credentials and model keys live in server-side environment configuration. The frontend only ever talks to the backend API.