Security & data handling

Roles on every application

Viewers read; editors create, import and request reviews; approvers also decide reviews; managers also change tables, members, keys and automation. Access is checked again on every API request and background job, so a removed member loses access straight away.

Sign-in

Shared Yakware accounts with email verification, multi-factor authentication and single sign-on policies.

Independent approvals

Nobody can approve work they requested or created. Approvals are bound to the exact version reviewed and stop counting when that data changes.

Guests

Guest access is limited to one table and to the fields and records you choose. Invitations only work for the invited, verified email, expire after 7 days, and accepted access ends after 90 days. Revocation is immediate.

API keys

Keys are bound to a single table, can only narrow their creator's own access, expire after 90 days and can be revoked at any time. Only a hash of each key is stored.

Audit trail

Every record keeps its revision history and activity. Edits are revision-checked, so a stale change is refused instead of silently overwriting someone else's work.

Exports

CSV exports neutralise cells a spreadsheet would run as a formula.

Connected services

Outbound requests to YakPipes, YakDocs and YakFiles use a protected client that refuses redirects and internal addresses. Credentials are never sent to browsers.

AI

AI triage is off until a manager turns it on, sends only the fields you allow, and can never approve work.

Payments

Card payments are handled by Stripe. YakTables never sees or stores card numbers.

Found a security issue? Email security@yakware.com. Read our Privacy Policy and Terms of Service.