Authenticated access
Users sign in through POSNek’s identity flow (Appwrite-backed authentication). Keep credentials confidential.
Authenticated access, business isolation, role permissions, and server-side authorization — explained honestly.
Users sign in through POSNek’s identity flow (Appwrite-backed authentication). Keep credentials confidential.
Data is scoped to your business/tenant. Server-side checks enforce membership and permissions.
Staff see what their role allows (for example owner, manager, or cashier capabilities where enabled).
Feature and permission enforcement happens on the API, not only in the client UI.
Paid POSNek subscription upgrades use verified payment flows via third-party payment providers such as Paystack. POSNek is not designed to store full card numbers.
Administrative and sensitive actions may be logged where implemented, to support security and troubleshooting.
Production services are intended to be accessed over HTTPS. Do not treat this page as a penetration-test report or certification.
We do not claim SOC 2, ISO, PCI DSS, bank-level, or other security certifications on this page unless and until they are independently verified for Dikoder Recording Studio (DikoderGroup).
Report security concerns to dikodercom@gmail.com. See also security.txt.
Start your 7-day Business trial. When it ends, keep going on Free forever — upgrade only when you need more.