Who we are and what this covers
Ayarly is developed and operated by Digitory Studio FZCO. This policy covers the Ayarly app on phones, the web and desktop computers, the admin console, and the website ayarly.app.
The shop that buys Ayarly owns its business data: receipts, stock and customers. We process that data on the shop’s behalf so the software works, and we apply the same rules on every device the shop uses.
What we collect
Every item here has a matching reason in the next section.
- Account details: each staff member’s name, the email address or phone number they sign in with, and their role in the shop (owner, salesperson and so on). Accounts are created by the Ayarly team together with the shop owner; there is no open sign-up.
- An optional device PIN: if the shop turns on quick sign-in with a PIN, we store a one-way hash of it that cannot be turned back into the PIN, plus a count of failed attempts so we can lock the account temporarily.
- Shop records: categories, karats and weights, stock movements and stock-takes, receipts and returns, and the gram rates the shop sets. If a staff member writes a customer’s name or phone number on a receipt, it is stored with that receipt, exactly as it would be on paper.
- Device details: an identifier for each device registered to the shop, with its name and platform (iPhone, Android or web), so receipts written offline upload correctly and the shop can see which device made which entry. If a staff member allows notifications, the device’s push notification token.
- Sign-in codes: a one-time code sent by email, WhatsApp or SMS. We keep only a hashed copy, for a few minutes, until it is confirmed or expires.
- Support conversations: if you contact us on WhatsApp or by email, we keep the conversation so we can follow up on your question.
Why we use it
- So staff can sign in and work, and the shop knows who did what.
- So receipts are priced and printed, stock is updated, and reports add up.
- So devices stay in sync and receipts written without internet are never lost.
- So the shop receives its notifications, such as a new receipt or a change in the gram rate.
- So accounts stay protected: we detect repeated failed attempts and stop unauthorised use.
- So we can answer support requests and fix faults.
- So we can write the AI summary of the reports when the shop owner asks for one from the reports screen.
We do not use the data for advertising, for building profiles of customers, or for any purpose other than running the software for the shop.
Who else sees it
We do not sell, rent or share data with advertisers. The only parties that receive any of it are providers that perform one specific job for us, and each receives only what that job requires:
- Delivering sign-in codes by email through Amazon Web Services (Amazon SES): it receives the email address and the code.
- Delivering sign-in codes on WhatsApp through Meta (WhatsApp Business Platform): it receives the phone number and the code, under WhatsApp’s own privacy policy.
- Delivering sign-in codes by SMS through SMS Misr, an Egyptian provider: it receives the phone number and the code.
- Delivering push notifications and app updates through Expo: it receives the notification token and text, and the device’s internet address when an update is downloaded.
- Summarising reports through Anthropic (the Claude model): when the shop owner asks for a summary, the totals of sales, returns and weights by day, category and karat are sent, together with each salesperson’s name and their figures. Customer names and numbers are never sent, and the data is not used to train models.
- Hosting our servers and databases with a hosting provider we contract with; data is encrypted in transit.
We may disclose data if the law requires it through a formal order, and in that case we tell the shop owner where the law allows.
How long we keep it
Shop records stay for as long as the contract runs, because they are the shop’s own books: last year’s receipts have to remain available for stock-takes and audits.
Sign-in codes are deleted after a few minutes. Sessions expire on their own and must be renewed. Support conversations are kept until the question is closed and for a reasonable period afterwards.
When the contract ends, or when the shop owner asks, we delete the shop’s data from active systems within 30 days and from backups within their normal cycle. The shop owner can ask for an export before deletion.
How we protect it
All traffic between the app and our servers is encrypted (HTTPS). PINs are never stored as typed, only as one-way hashes. Sign-in uses a one-time code rather than a fixed password, and an account locks temporarily after repeated failed attempts.
Inside the shop, the owner decides what each staff member may do: change a price, void a receipt, see the margins. Every entry is recorded under the name of the person who made it.
No system is perfectly secure. If a breach affects your shop’s data, we will tell you without delay, say what happened, and say what we did about it.
Your rights
A shop owner can at any time ask for a copy of the shop’s data, a correction of wrong data, deletion of a staff account, or deletion of all the shop’s data. A staff member can ask to correct their personal details or delete their account; we coordinate that with the shop owner, because the account belongs to the shop.
We answer these requests within 30 days. Ask through the contacts below, from the same email address or phone number registered on the account, so we know it is you.
Children
Ayarly is a work tool for shops and their staff. It is not directed at anyone under 18, and we do not knowingly create accounts for minors.
Changes to this policy
If we change something substantive, we update this page and the date at the top, and we tell shop owners by email or WhatsApp before the change takes effect.