Security

INKD does not collect, hold, transfer or process royalty payments. Your locations keep paying you directly, and you record those payments in INKD. Payments for your INKD subscription are handled by Dodo Payments; INKD never sees full card details.

Connections to INKD use HTTPS, so data is encrypted in transit. Passwords are never stored in readable form; they are hashed with scrypt and a unique salt. Sign-in cookies are HTTP-only and sent over secure connections in production.

Every record belongs to one business, and every request is checked against the signed-in user's business. Team members see their business's data. Locations only see their own reports and statements.

Inside your business: owners and admins manage the workspace; viewers have read access; locations see only their own records. You can turn on two-step verification with an authenticator app, and sign-in attempts are rate limited.

Inside INKD: platform access is limited to designated administrators who must pass two-step verification. When an administrator opens a customer account for support, that session is read-only and expires within an hour. Sensitive support actions are logged.

The database is backed up daily to private storage, and each backup is checksummed. Backups are kept for 30 days and then deleted.

The account owner can download all workspace data at any time from Settings as a ZIP: the records (everything except passwords, keys and other secrets), the original uploaded files and a file manifest. The owner can also permanently delete the workspace. Billing, terms and login records are retained for 2 years; backup copies are purged within 30 days. See the privacy policy.

Replit (hosting, database and file storage), Resend (email), Dodo Payments (checkout and billing), OpenAI (AI support) and Google Ads (ad measurement, only with consent where required). See the full subprocessor list. INKD's policy is that customer data is not authorized for AI model training.

Email support@inkdroyalties.com. We will tell you without undue delay after becoming aware of a personal data breach affecting your data, as set out in the Data Processing Addendum.