Security and your data
Ayyra reads a short list of fields from your ERP, never writes to it, and shows each organization only its own stock. This page says exactly what that means, and what we have not yet had audited.
Ayyra reads. It never writes
Ayyra connects to your ERP with read access and nothing more. It does not change an order, a price, a stock figure or any other record, and it cannot, because it never asks for permission to.
That is the single most important thing on this page. Your ERP stays the system of record and your team keeps working in it.
What it reads, and nothing else
Ayyra asks for the smallest set of fields that can find stock at risk:
- Sales lines, so it can see how fast each line sells at each depot.
- Stock on hand by depot, so it knows how much is exposed.
- Batches and expiry dates, so it knows how long you have.
- The principal a line belongs to, so a return is costed against the right terms.
Not your customers, and not your staff
Ayyra does not need your customer list, your contacts, your staff records or your bank details, so it does not ask for them. If a field is not needed to work out whether stock will sell in time, it is not in the set above.
One organization, one view
Every request inside Ayyra is checked against the signed-in person's session, and the organization and role come from that session rather than from anything the browser sends. A person sees their own organization's stock and no one else's.
The check happens in the code that fetches the data, not only at the edge, so a direct request cannot step around it.
The product is not on the public web
Every signed-in screen is marked not to be indexed, and the app host serves a robots file that disallows crawling outright. Nothing behind sign-in is reachable from a search engine.
The prototype runs on made-up numbers. There is no real distributor's data in it.
Where it runs
This website is served by Vercel. Measurement, if you accept it, goes to Google Analytics, and those are the only two services that receive anything from this site.
Customer data in the product is to be held in Africa, with a Kenya-resident deployment for customers who require one. The privacy policy names every service that handles data, and we add a service to that list before it starts handling any.
What we cannot show you yet
Ayyra has no security certification to show you. We are not going to imply one with a badge or a vague phrase. When Ayyra is audited, this page will name the standard, the auditor and the date, and you will be able to ask for the report.
Until then, take this page as a description of how Ayyra is built, not as a claim that someone else has checked it.
Telling us about a problem
If you think you have found a security problem, write to daiwiblabs@gmail.com and say what you found and how to reproduce it. We will reply, and we will not take action against anyone who reports something in good faith and does not go looking through other people's data.
