Oribi 360
اللغة
اللغة

الاستفسار عن السعر

أخبرنا عن منشأتك وما تودّ استخدامه. سنرد عليك بالسعر بعملتك — دون أي التزام.

يحدد هذا العملة التي تُمسك بها دفاترك.

يُرجى تضمين رمز الدولة، بدءًا بعلامة +

ماذا يفعل متجرك؟

حدّد ما ينطبق. نفعّل ما تحتاجه فقط، ويمكنك طلب المزيد لاحقًا.

يترك لدينا العملاء أشياء لإصلاحها أو صيانتها أو صنعها: هاتف أو سيارة أو ثوب. سنجهز لك نقطة استلام وقسيمة لها.

نبيع الهواتف أو الأجهزة، ونريد متابعة كل منها برقم IMEI أو الرقم التسلسلي.

نحوّل المواد إلى ما نبيعه: مخبز أو ورشة أو مصنع صغير.

نحتفظ بالمخزون في أكثر من مكان، مثل المتجر والمستودع.

نُصدر فواتير للعملاء أو ندفع للموردين بعملة أخرى.

سياسة الخصوصية

قبل إرسال طلبك

يُرجى قراءة سياسة الخصوصية الخاصة بنا. فهي توضح كيف نحافظ على معلوماتك.

هذه المستندات باللغة الإنجليزية. والنسخة الإنجليزية هي المعتمدة.

🔒 قراءة سياسة الخصوصية النسخة بتاريخ 19 نوفمبر 2026

This Privacy Policy explains how Oribi Tech, LLC ("Oribi Tech", "we", "us"), a Virginia company in the United States, handles information about people in connection with the Oribi 360 website and app (the "Service").

We sell the Service to businesses such as shops, workshops and small companies. In this policy, "shop" means any business that uses the Service. Selling to businesses does not make this policy only about companies. Some of our customers are sole traders, and the records in the Service are about real people.

This policy is for:

  • anyone who visits our website or opens a page of the Service;
  • anyone who asks us for access or a price, or writes to us;
  • owners and staff who have a login, and Oribi's own staff;
  • people a shop keeps records about, such as its customers, suppliers, sellers and employees.

1. Who is responsible for which information

We are responsible for information about people who deal with us directly. That means visitors to our website; people who ask for access or a price, or who write to us; the sign-in and security records of everyone with a login; prices, payments and billing; support; proof of agreeing to our documents; our own staff log; and the backups and logs we keep to run the Service. We decide how this information is used, as this policy describes.

The shop is responsible for what it enters or uploads about its own customers, suppliers, sellers and staff. In this policy we call these "Shop Records". The shop decides what to record, why, and who at the shop may see it. We store and process Shop Records for the shop, on its instructions. The shop must have its own lawful reason for keeping them, and must tell the people concerned, including that their details may be stored outside their country (section 8).

Some things do not fit neatly into those two groups, so we say so here:

  • Some rules are fixed parts of the Service, which we chose, for every shop: job photos are erased after a set time, device passcodes are forgotten when a job closes, job status pages stop showing the job after a set time, an audit history is kept, a trade-in needs the seller's identity number to help trace stolen phones, and a business may be deleted after its plan ends (section 10). A shop that uses the Service instructs us to apply them (Terms of Use, section 10.4).
  • Our software writes each shop's audit history for that shop. It includes the network address of the shop's staff. We designed what it records. The shop decides who may read it.
  • A shop chooses whether to switch on job status links and supplies what they show. Our staff can also change this for a shop, with a reason recorded in its audit history. We decided how those pages work, including the fonts they load and the limit on visits from one network (section 3).
  • If someone puts a shop's customer or staff details in a support ticket, our staff will read them (section 6).
  • Our server staff may look at Shop Records in the cases section 6 describes.

Other companies are responsible for their own part. We chose to load fonts from Google, so your browser contacts Google when a page opens. Google handles that request under its own terms. We chose to play the Help Center's videos, and the videos on our website, from YouTube, so your browser contacts YouTube when you press play. YouTube handles that viewing under its own terms. WhatsApp and phone companies are responsible for messages sent from a person's own phone. Mobile-money companies, PayPal, banks and money-transfer firms are responsible for payments made through them. Our host and email service work for us (section 7).

2. What information we collect, and where it comes from

Most of this information comes from you or from the shop you deal with. Some comes from your browser or device when you use the Service.

Information about people who deal with us

  • If you visit our website or open a page of the Service: your IP address and browser details, held in a session record even if you do not sign in. Also your language, if you choose one.
  • If you ask for access or a price: the business's name and country; the owner's name; email address; phone and WhatsApp numbers; how you would like us to contact you; your language; any note you add; what your business does, from the questions on the form; the business's tax number, if you give it; for a US business, its state; for a Saudi business, your answer to our e-invoicing notice; a coded mark of the network you wrote from; whether you asked for a price; whether you proved your email address with a code; the date of any repeat try; whether and when we checked the names against the US sanctions list; our decision; and notes our staff write about your request.
  • If you use our contact form: your name, email address, phone number, country and message; a coded mark of the network you wrote from; and our staff's notes on the reply.
  • Proof of agreeing: which version of our Terms of Use you agreed to and which version of this policy you were shown, when, your IP address and browser, the form or page you used, and the request, login and business it belongs to. We keep this for applicants, invited staff and anyone asked to agree again.
  • Proof we told you of a change: when we email owners about a change to our Terms of Use or this policy, the address each email went to and when it was sent.
  • Login information: name, email address, language, display settings, your role and limits in each business, and when your email address was proven. Your password is stored only as a one-way hash. If you use two-factor sign-in, its secret and recovery codes are stored encrypted. When a shop invites you, we also hold the name, email address, WhatsApp number, language and role it gave us.
  • Sign-in and security records: the IP address and browser of each session; when you last used the Service, and in which business; coded records of wrong passwords and wrong codes, and of the networks you signed in from; a coded mark for browsers you have signed in on; sign-in locks; password-reset requests; and security alerts sent to you.
  • The business's own details: its legal name, address, phone, email address, website, tax and registration numbers, logo, country and time zone.
  • Owner contact and billing: the owner's name, email address and phone number, kept on the business's record; the agreed price, currency, billing period and paid-until date; the features, businesses and branches allowed; each payment's amount, currency, method, reference number and date, the paid-until date it set, and who recorded it; PayPal invoice links sent; receipts; reminders and warnings sent; any phone calls we tried before a deletion; any hold; and private notes our staff write about the account. The customer does not normally see these notes, although a person may be able to ask for what we hold about them (section 11).
  • Support and messages: support tickets, their messages and any files sent with them, such as a screenshot or a PDF; the business of the person who opened them; the phone number we hold for that business's owner; and our staff's notes on them. Copies of website messages and requests for access also appear in our staff's in-app notices.
  • Our staff log: the name, role and IP address of the Oribi staff member, what they did and their reason. An entry can include the name and email address of the person concerned, for example when a request is rejected.
  • Our staff's sign-ins: for each member of Oribi's staff, the time of their last 20 sign-ins to our admin area, the browser and system used, whether the browser was new to them, and when they were last active. No network address is kept.

You must give us what our forms mark as required. Without it we cannot consider your request or open your account.

Shop Records

What a shop records depends on the shop and the features it uses. It can include:

  • Customers and suppliers: names, phone numbers, email and postal addresses, tax numbers, credit limits, language, contact people, notes and follow-ups; invoices, bills, payments, mobile-wallet transaction numbers and statements.
  • Sellers and lost phones: the name and phone number of a person who sells an item to the shop, the type and number of their identity document, the item's IMEI or serial number, and the price. Also reports of lost or stolen phones, which can include free text.
  • Repairs and other jobs: the name, phone and WhatsApp number of the person who left the item, and of anyone who approved the work or collected the item, with their relation to the customer; proof of who agreed or collected; the item's make, model, IMEI or serial number, accessories and condition; a device passcode if the shop collects one; the problem and what was found; photos, which can show people; home addresses, map links and notes for visits; the staff assigned. For vehicles this can include the plate, VIN, engine number, mileage and belongings left inside. For tailoring it can include the wearer's name and body measurements.
  • Employees: names, phone, email and home address; emergency contact; job type, dates, manager and reason for leaving; attendance, lateness and corrections; leave requests and the reasons given, which can reveal health matters; documents such as photos, national ID copies, contracts and certificates; salary, deductions, net pay and payslips; loans, advances and expense claims; bank name and account number.
  • Money and other records: the shop's account numbers; bank and mobile-wallet statement lines, which can include a sender's phone number; cheques; loans, including notes on guarantors; tax registrations and withholding records; attachments; and imported lists, each row kept as it was imported.
  • Audit history: who recorded or changed what, when and why, with the old and new values (passwords, codes and similar secrets are hidden), and the IP address and browser used.

3. If a shop keeps records about you

A shop uses the Service to keep its own records. If you buy from a shop, sell to it, work for it or leave something with it, your details may be in those records. The shop decides what to record and should tell you. Your questions go to the shop first (section 11).

The Service does not email, text or message a shop's customers. If a shop presses a WhatsApp or text button in the Service, the message goes from the shop's own phone, through that app or phone company.

Job status links. A repair or service shop may switch these on. Your slip or message may then carry a link to a page about your job. Anyone who has the link can open the page without signing in, so treat it like your slip.

  • The page shows the shop's name, address and phone; the job number; the kind, make and model of the item; how far the work has got; the promised date while work is still owed; and, while the job is open, one figure for what is still to pay.
  • The page does not show your name, phone number, IMEI or serial number, photos or notes, unless the shop typed them into the item's make or model.
  • The page sets no cookie and starts no session. It does load fonts from Google (section 7). To stop misuse, we count visits from each network for a short time.
  • From 30 days after the job closes, the page shows only who the shop is and the day the job closed, so you know whom to call.

Things that go sooner. A device passcode, if the shop collected one, is forgotten when the job closes. Job photos and answer files are erased 12 months after the job closes, or when its warranty ends if that is later. The rest of the job stays in the shop's records.

Identity numbers. The number of a seller's identity document is encrypted in the database. It is shown in full to shop staff whose role covers stock or purchasing, on the list of trade-ins and on the slip they print. Others see only that a number was taken. It is kept until the shop's business is deleted. A scan or photo of a document is stored as a file, and is not separately encrypted (section 12).

4. Why we use information, and our reasons

  • Running and supporting the Service. This includes keeping each shop's records and audit history, and printing and downloads. Our reason: our contract with the shop, and our agreement with each person who has a login (Terms of Use, sections 1.3 and 1.4).
  • Reviewing a request and contacting you the way you asked. Our reason: steps you asked us to take before any contract.
  • Keeping the Service and its users safe. This includes sign-in and security records, locks, alerts, limits on repeated tries, the staff log and finding misuse. Our reasons: our contract with the shop, our agreement with each person who has a login, and the legal duty to keep information secure.
  • Billing, payments, receipts and proof. This includes showing what was agreed and paid. Our reasons: our contract with the shop, legal duties such as tax records, and making or defending legal claims.
  • Seeing who is using the Service. We look at which businesses and people have used it recently, so we can help them, keep the Service secure and remind owners about renewal. Our reasons: our contract with the shop and, where the law of your country allows us, our legitimate interest in supporting customers.
  • Telling people about their account and the Service. This includes security alerts, reminders and changes to our documents (section 15). Our reason: our contract with the shop, and our agreement with each person who has a login.
  • Meeting legal duties and answering lawful requests. This includes checking the names on a request for access against the US sanctions list before we approve it. Our reason: the law that applies.
  • With your consent, where the law needs it. You can withdraw consent at any time (section 11). That does not undo what was done before.

Which of these reasons counts in law depends on your country (section 16).

Ticking the box on our forms is how you agree to our Terms of Use and confirm you have read this policy. It does not by itself mean you consent under privacy law. If you work for a shop, that tick is not your consent to the shop's own records about you. The shop needs its own reason in law for those.

We do not sell personal information. We do not use Shop Records to advertise to anyone. The Service has no advertising or analytics tools, our own or another company's, apart from YouTube's video player for our how-to videos and the videos on our website (section 7). It loads only when you press play, and YouTube may then count the view and show its own ads, under its own terms.

5. Who can see information inside a shop

A shop decides who gets a login and what each person's role allows.

  • By default, the shop's owner, manager and accountant can read its audit history. It shows what each person recorded or changed, when, and from which network address. A shop can change these permissions.
  • Payroll screens, payslips and bank details are for those the shop lets handle payroll, and for the person they belong to. Money paid or lent to a named person, such as an expense claim, an advance or a loan, also shows in the shop's cash and bank books and its audit history, which the people the shop lets keep its books can read.
  • An owner can make a new-password link for a staff member whose login belongs only to that shop. This is recorded in the shop's audit history.

If you work for a shop, it is responsible for your work records, such as attendance, leave, pay and documents. Your questions about them go to your employer first. If the shop's account is due to be deleted, staff with a login are warned so they can save their payslips first (section 10).

6. Who can see information inside Oribi

Our staff, and anyone who helps us with a staff login, work at three levels. Each has their own login, and two-factor sign-in is compulsory for them.

  • Moderators help customers. They can see who owns and works in each business (names, email addresses, roles, whether two-factor sign-in is on, and any locks); the owner's name, email address and phone; each customer's price, due date and payments; requests for access, apart from the IP address and browser; every support ticket from every business, with any file sent with it; every website message; when people and businesses last used the Service; and how a shop's Jobs feature is set up, including the names and job titles of people working on jobs. They can search for any person with a login. They can write private notes, record a payment, clear a locked sign-in, and send a password-reset email to the person's own address.
  • Admins can see all of that, plus the IP address and browser on a request for access, and when each member of our staff signed in to the admin area. They can also approve and reject requests, set prices and features, extend trials, correct a business's settings such as country, language, time zone and tax, change Jobs settings, edit website pages, switch a business or a login off, remove a member's access, change a member's role, limits and permissions, reissue or withdraw invitations, and help with logins as described below.
  • The Master account can do all of that. Only the Master account can manage our staff, read the staff log, delete a business, give lifetime access, reverse a recorded payment, or publish this policy and our Terms of Use.

What our staff screens do not open. Apart from those names and job titles, and files sent with a support ticket, no staff screen opens a shop's invoices, customers, employees, pay, job records or documents. We do see whatever anyone puts in a support ticket, including any file sent with it, so please leave out anything we do not need. A file cannot be taken back once it is sent, so check it before you send it.

Help with sign-in. To help someone who is locked out, an Admin or the Master account can make a sign-in link that appears on their own screen, and can reset two-factor sign-in. A sign-in link can open a login that has no two-factor sign-in on its own. On a login with two-factor it also needs a reset. Our rule is that these tools are for getting people back in, not for reading a shop's records. Each use needs a reason and appears in that business's audit history as Oribi support. We email the person concerned and the business's owners when we do either.

What is recorded. Changes our staff make to a business's logins, roles and limits appear in its audit history. Staff actions such as approving requests, setting prices and recording payments go in our staff log, which the app does not let anyone change or delete. Simply looking at a screen is not recorded.

Looking at a shop's records. We do not look through them as a routine. The people who run our servers may look when the shop asks for help, to fix a fault, to protect the Service, to deal with a legal claim, or when the law requires it. That kind of look is not recorded in the shop's audit history.

Direct access. The company that hosts our systems, and the people who hold our server login, can technically reach the database, files and backups without using these screens. Today the only person who holds that login is our founder.

7. Outside companies

We use outside companies for the kinds of work below. We choose these providers and may change them at any time. A new provider of the same kind handles information only for the same purposes, under the protections in this policy. We name a company only where you deal with it yourself, or your browser does.

  • Web hosting. Our web hosting company runs the servers that hold the website, the app, the database and uploaded files. A host holds everything stored on its servers.
  • Email sending. A mail service, which may be run by our web hosting company, sends our emails. It handles each email's address, subject and text.
  • Staff email and office tools. A business email and office-tools provider holds our staff's email, including alerts and messages about customers, and the office files our staff keep with it.
  • Encrypted backup storage off the host. A cloud storage provider may hold copies of our backups. Where it does, they are encrypted before they leave our server and kept in storage under our own account.
  • Our own bookkeeping and spreadsheets. Accounting software and cloud spreadsheets, from providers we choose, hold the names, amounts and dates of what customers pay us. We do not put a shop's own records in them, and we do not paste customers' information into AI or support tools.
  • Fonts from Google. Pages of the website and the app, including sign-in, printed slips and job status pages, load fonts from Google. When a page opens, your browser sends Google your IP address and browser details. On most pages it also sends the address of our website, but not of the page you are on. On a job status page it does not send even that.
  • Video hosting. The how-to videos in the app's Help Center, and on our own staff's training page, are hosted on YouTube (a Google company). A video's player loads only when you press play. Then your browser sends YouTube your IP address and browser details. It also sends the address of our website, but not of the page you are on. YouTube handles that viewing under its own terms, which may include its own cookies and browser storage, and it may show ads with a video.
  • Videos on our website. The short videos about Oribi 360 on our website's public pages, such as the home page, are hosted on YouTube in the same way. Nothing is sent to YouTube until you press play. Then the same applies as for the how-to videos above.
  • WhatsApp and phone companies. If you ask us to reach you on WhatsApp, or you message us there, WhatsApp (a Meta company) handles that conversation under its own terms. Our staff may send a link to set up your login that way, or a message about your account or a payment. Messages a shop sends with a WhatsApp or text button go the same way, from the shop's own phone.
  • Payment and money-transfer companies. You may pay us by bank wire, PayPal, a money-transfer service or another method we agree. That company handles your payment under its own privacy terms. We do not take card details. We record what section 2 lists. If we send you a PayPal invoice, we give PayPal your name, email address and the amount to create it.
  • Our representative in Bangladesh. You may pay us in cash or by mobile-money wallet through our representative in Bangladesh. Those payments go to our representative there, who sees your name, number and the amount. If our representative also holds one of our staff logins, they also see what that staff level sees (section 6), under the same rules as our staff.
  • Our advisers. Our accountant and other professional advisers see our billing records when they need to.
  • Authorities and others. We may share information when we believe the law requires it, or to protect the safety, rights or property of our customers, the public or us. If an authority demands Shop Records from us, we check that the demand is lawful and applies to us. We tell the shop unless the law forbids it or we reasonably cannot.
  • A buyer or successor. If our business is sold or reorganised, the information may pass to the buyer or successor, who must keep the protections in this policy.

We keep this section current. A change from one provider to another of the same kind does not change what it says, so it needs no update first. If we start to use a kind of provider that this section does not describe, we add it here before that provider handles Shop Records, or as soon as we can if an urgent fault or security problem prevents it.

8. Where information is stored and moved

Our web hosting company keeps our servers in the United States. So information entered anywhere, including in Bangladesh and the Gulf, is stored on servers in the United States. That includes identity document numbers and copies, employees' pay and bank details, and everything else in section 2. Information held in the United States can be demanded by US courts and authorities. If we move the servers that hold Shop Records to a country outside the United States, we update this section before we move them.

Our staff may also read information from where they work. Today they work in the United States and Bangladesh. We may add staff or contractors in the Gulf countries, and we update this section before they start.

Other places:

  • Our backups, our staff's email and our own bookkeeping and spreadsheet records are kept by providers in the United States or in other countries where those providers operate, with the safeguards in this policy.
  • Google decides which of its servers answers a font request, and we do not know which country that is.
  • YouTube decides which of its servers plays one of our videos, and we do not know which country that is.
  • WhatsApp, PayPal, wallet and money-transfer companies work under their own terms and may hold your details in other countries.

These countries may not give the same legal protection as your own, and we do not claim that they do. What we do ourselves is in sections 6 and 12.

Storing and reading information in these places is part of how we provide the Service, under our contract with the shop and our agreement with each person who has a login (Terms of Use, sections 1.3 and 1.4). It is the same for everyone. Our forms also ask, separately from our Terms of Use and with its own tick, that each person confirm they understand where their business's records are stored. That box is never ticked for you, you can carry on without it, and we keep a record when you tick it. Information is stored in these places whether or not you tick it. If you do not want your information stored and read in these places, write to us. We cannot run the Service without them, so we would then close your login. If you are an owner, you can first take the shop's data out (section 10). For people in a shop's records, the shop is responsible for telling them and for any consent the law requires (see our Terms of Use).

We keep this section current. A change from one provider to another of the same kind, in the places described here, does not need it to change first. Write to us if you want to know more about this (section 19).

9. Cookies and browser storage

We use a few cookies and browser storage items. We set no advertising or analytics cookies. If you press play on one of our videos, YouTube's player may set its own cookies and browser storage, under YouTube's terms (section 7). We do not control them.

  • oribi-360-session (session): set for every visitor. It ends 2 hours after your last action.
  • XSRF-TOKEN (form protection): set for every visitor, for the same time.
  • remember_web_ followed by a code (Remember Me): set only if you tick Remember Me. It keeps you signed in on that browser for up to 30 days, then asks for your password again. Do not tick it on a shared device.
  • oribi_known_device (known browser): set when you finish signing in, or when you set a new password through an emailed link. It lasts 1 year. It holds an encrypted, coded mark, for up to 8 logins, showing this browser has signed in before. We use it to protect your account, so that a pause aimed at someone guessing does not shut you out, and to decide when to send a new-device alert.
  • oribi_locale (language): set when you choose a language. It lasts 1 year, and is used only while you are signed out.
  • oribi_page_language (page language): set for every visitor when a page is shown, to that page's language. It lasts 1 year. It is read only to show our maintenance page in that language while the site is being updated.
  • oribi-nav-open and oribi-fold (browser storage): these remember which menu sections and page sections you opened. The second is kept per login and per page. They stay in your browser until you clear them, and are not sent to us.

You can clear all of these in your browser. You will then need to sign in again. Job status pages set none of them.

10. How long we keep information

While a business is using the Service

We keep Shop Records while a shop's plan or trial is running, apart from the things that go sooner, below. A shop corrects its own records. A financial record is corrected by a new entry that reverses or adjusts it, so its history stays complete.

Things that go sooner

  • Device passcodes: forgotten when the job closes.
  • Job photos and answer files: erased 12 months after the job closes, or when its warranty ends if that is later. The job still shows that they existed.
  • Job status pages: stop showing the job 30 days after it closes.
  • Files chosen in an upload box but never saved: removed within a few hours.

When a plan or trial ends

  • Read-only. When a paid plan ends, the shop has 7 days of grace with a red banner, and saving still works. After that the business is read-only. A free trial has no grace days and becomes read-only on its end date. Read-only means people can still sign in, read, print, download, agree to updated documents and contact us, but nothing new can be saved.
  • How long we keep it. We keep a business's records for 1 year after its plan or trial ended. If it was a free trial in which nothing was saved beyond its set-up (no customer, supplier, product, employee, job, sale, purchase, payment, payroll or uploaded file that its people added), this is 90 days. Grace days do not add to this time. A later payment or extension moves the date and cancels any deletion in progress.
  • Deletion. After that date we may permanently delete the business's records, files and audit history. These dates are the earliest we may delete. We may keep the records longer, for example while we review a case, but do not rely on that. If a business is still here 6 months after its date, we review it again and either delete it or record why we kept it. Treat deletion as final. We do not promise to bring anything back, even if a backup still holds it (below).
  • Warnings. We warn the owners by email and in the app about 90, 30, 14, 7 and 1 days before the deletion date. Staff with a login get a notice in the app about 30 days ahead and an email about 14 days ahead. Automatic deletion runs only where those warnings really went out to a proven email address, the business is not switched off, and no hold, recent open support ticket or dispute we know of applies. Anything else goes to our Master account to look at by hand. If a warning failed or no owner's address is proven, we first try to reach an owner by phone, at least twice on different days.
  • Taking your data out. Until the deletion date, including while read-only, an owner can download one zip file with spreadsheet files of the shop's lists, key PDFs and uploaded files, as the download page sets out. The zip stays on our server for 7 days after it is made, so you can download it, and is then deleted. Inside it, identity numbers and bank account numbers are not encrypted. Staff can save their payslips as PDF. Keep the zip safe, because it holds staff and customer details. If it fails or looks incomplete, tell us before the deletion date.
  • Your own legal records. The law may make your business keep records for several years, which is often much longer than we keep them. That is your duty, not ours. Keep your own copy. Your accountant can tell you how long.
  • Holds. If you send us a tax notice, a court paper or similar proof before the deletion date, we place a free hold, with a reason and a review date. For other reasons we may place one. A hold stops warnings and deletion, and only our Master account can lift it. If it is lifted, we warn again before any deletion.
  • Lifetime access and no plan. A business with lifetime access or no plan record is not deleted automatically.
  • Deleting by hand. Only our Master account can delete a business by hand, and it must give a reason. The shop is locked for 14 days and the owners are emailed first. An owner can still download the zip during that time. It can be immediate only if nothing was ever saved beyond its set-up and its plan or trial has ended. Our Terms of Use say when we may do this.
  • Switching off. We may switch a business or a login off, with a reason. Nobody can then get in, and a page says how to reach us. No data is touched and it can be undone. Switching off does not stop the time above from running, but we do not delete a switched-off business automatically. A person at Oribi reviews it first, and gives an owner a way to take the data out unless the law or a security risk prevents it.
  • Logins. If a deleted business was your only one, and no other business's records name you, we delete your login. If another business's history names you, we lock your login and leave that history alone.
  • Closing record. After deleting a business we keep a small record for 7 years: its name and country, the owner's name and email address, its dates and the plan end date used, what we billed, the warnings sent with their dates, addresses and results, any calls we tried, whether an owner downloaded a copy, any hold, who decided what and why, and what was agreed to and when. It holds none of the shop's customers, invoices or staff records. We send the owners a final email.

Requests for access and website messages

  • A request we approved stays with the account's records until the business is deleted.
  • A request we reject or close, and a website message, are deleted 12 months after the decision or the last reply. We keep two things after that: an entry in our staff log showing the decision was made, which can include the person's name, email address and business name; and the record of which versions of our documents you were shown, and when.
  • A request never decided is closed and deleted 12 months after we received it, on the same terms.
  • Emails and WhatsApp messages our staff exchanged with you about a request or a message are kept in our staff's email and phones, apart from the app, and are not deleted on those dates.
  • The IP address and browser recorded with your agreement are deleted within 12 months of declining or closing your request, or within 12 months of receiving it if it is never decided.

Sign-in and security records

  • Sessions: end 2 hours after your last action, and a routine clean-up removes the record later.
  • Wrong-password and wrong-code counts: cleared as new records come in, once they are over a day old. A lock that requires a new password stays until the password is reset.
  • Records of networks you signed in from: cleared when that login next signs in, once they are over 90 days old.
  • Counts of tries from each network: used to slow down guessing and floods of forms, kept under the network's address, and cleared within a day after they run out.
  • Login details: kept while you have a login, and handled as described above when a business is deleted.
  • After you change your login email: we warn the old address, and it can undo the change for 7 days. If that address was never confirmed as yours, its button asks us to check the change instead of moving the login back.

Our own records

  • Proof of agreeing: kept while your business uses the Service and for 7 years afterwards, so we can show what was agreed. If your request was not approved, that time runs from the decision.
  • Proof we told owners of a change: kept for 7 years after the email.
  • Payment records, invoices sent and receipts: kept as our own business records after an account closes, for 7 years.
  • Support tickets, the files sent with them, and our notes on an account: kept while the business uses the Service, and removed when it is deleted, unless a dispute is open.
  • Our staff log: kept with no set end date.
  • Our staff's sign-ins: the last 20 for each member of our staff. Older ones go as new ones arrive, and all of them go when the person leaves our staff.

Backups and logs

  • Backups hold a copy of everything, including sessions and messages. Daily database copies are overwritten after 14 days, and weekly full copies after 8 weeks. Anything we delete stays in a backup until that backup is overwritten. Our web hosting company may also keep its own copies of its servers, for a time it sets.
  • Error logs are kept 14 days. They are for fixing faults. We remove known sensitive fields, but an error message can still contain someone's details.
  • Emails that could not be sent may stay in a failure list for about a week.
  • Our host's web server logs can include IP addresses and the addresses of pages opened, including job status links and password-reset links. The host decides how long it keeps them.

11. Your rights, and how to use them

You can ask us to tell you what information we hold about you, give you a copy, correct it, delete it, object to or limit how we use it, or stop using it where you gave consent. Depending on where you live, the law may give you further rights. Nothing in this policy or our Terms of Use takes away a right the law says cannot be given up.

How to ask. Write to the address in section 19 and say what you want. We may need to check who you are. We respond as the law that applies to you requires. If we refuse, we tell you why, in writing.

What we may keep. We may keep what the law, a dispute or security needs, and we will say so. Financial records and audit history are corrected by adding to them, not by removing entries. A login named in a shop's history may be locked rather than deleted.

What you can do yourself. An owner can download the shop's reports, documents and data from inside the Service (section 10). You can change your own login email from your menu, using your password and a code sent to the new address. The old address is warned and can undo it for 7 days. If that address was never confirmed as yours, its button asks us to check the change instead of moving the login back. An owner's change takes effect after 24 hours.

If a shop keeps records about you. If you are a shop's customer, supplier, seller or employee, ask the shop first. It decides what to do with its records. If you write to us, we pass your request to that shop and help it where we can. If the shop does not answer you, tell us.

Complaints. If your country has a data-protection authority, you may complain to it. Please tell us first if you can, so we can try to put it right.

12. How we protect information

  • Connections use HTTPS.
  • Passwords are stored as a one-way hash.
  • Two-factor secrets and recovery codes, device passcodes, sellers' identity numbers and employees' bank account numbers are encrypted in the database, using one key held on our server.
  • Other information is not separately encrypted by us. That includes uploaded files such as ID copies, employees' pay and bank names, tax numbers, customer lists, and backup copies on our host. These are protected by sign-in and by role.
  • Files a shop uploads, such as ID copies, contracts and job photos, are kept outside the public website. The app shows them only to signed-in people whose role allows it.
  • Job photos are re-saved when uploaded, which removes location data from the picture. Documents such as ID copies, contracts and receipts, and files sent with a support ticket, are kept exactly as uploaded, so a phone photo of a document may still hold its location.
  • Software keeps each business's records apart from every other business in the same database.
  • Important changes are recorded in the audit history, and each posted journal entry is sealed into it, so a change made later is seen. That check cannot catch someone with full access to our server (section 6).

We work to protect information, but no system is perfectly secure. Please keep your password private, use two-factor sign-in, and tell us at once if you get an alert you do not recognise.

13. If there is a security incident

If we learn of a security incident in which someone without permission reached, changed, lost or exposed Shop Records, or that is likely to harm people whose information we hold, we will tell the affected account owners promptly, with what happened, what is affected and what we are doing. We will tell authorities, and the people affected, where the law requires it. For Shop Records, the shop may have its own duties and deadlines. We aim to give it what we know in time to meet them, where we reasonably can.

14. Children

Accounts and logins are for adults, and we do not knowingly open one for anyone under 18. The Service is not directed at children. A shop's own records may include young customers or trainees. The shop is responsible for those records, including any consent from a parent or guardian that the law requires. If you believe a child gave us information directly, write to us and we will deal with it.

15. Messages we send: service and marketing

Service messages are part of the Service, and you cannot switch them off while you have a login. They include:

  • codes to prove your email address, a copy of your request (only to an address you have proven), and our answer to your request;
  • password-reset links, sign-in locks, repeated wrong passwords or codes, new-device alerts, password changes and two-factor changes;
  • notices to a person and a business's owners when we make a sign-in link or reset two-factor sign-in, and to owners when another owner is invited;
  • warnings to the old address when a login email changes;
  • team invitations, business offers and activation links;
  • payment reminders, receipts, and notices about your price, plan and payments;
  • deletion warnings, notices about a copy of your data, and a final email after a deletion;
  • notices when we switch a business or a login off or on, and emails about changes to our Terms of Use or this policy (section 17).

An alert helps you notice a problem. It is not a guarantee that we will catch every one. Email is not always encrypted on its way.

Phone calls and WhatsApp. We use the owner's phone number to call back about the account and payments, to try to reach an owner before a deletion, and to check who you are before changing a lost email address. Our staff may also send you a WhatsApp message by hand about your account or a payment. We do not send sign-in codes by text or WhatsApp.

Marketing. We do not send marketing email from the Service. If that changes, we will update this policy first, and each marketing email will have a way to stop them.

16. Notes for particular countries

Where we offer the Service. We offer the Service to businesses in the countries listed on our Request Access form. We do not offer it in the European Economic Area or the United Kingdom.

Bangladesh. The Personal Data Protection Act 2026 gives you rights over your personal data, and it says those rights cannot be given up by contract or notice. In that Act's words, we are the data-fiduciary for the first group in section 1, and the processor for Shop Records. Where we set a rule for every shop (section 1), such as requiring a seller's identity number on a trade-in, we may share the shop's responsibility for that rule.

  • You can use your rights by written request (section 11). If we correct your information, we tell you and others concerned within 30 days of the correction.
  • We rely on our contract with you where you are a party to it, including when you agree to our Terms of Use to work in a shop's account; on steps you asked us to take before such a contract; and on the other grounds the Act allows, such as making or defending a legal claim.
  • Some Shop Records could cause more harm if misused: identity documents and numbers; photos that show a person's face, such as staff photos and ID copies; leave notes that mention health; staff bank and pay details; and reports of lost or stolen phones, which can accuse someone of a crime.
  • National ID, passport and tax ID numbers entered by a shop are stored in the places named in section 8.
  • You may complain to Bangladesh's National Data Management Authority once its complaint process opens.

Kuwait, Qatar, Saudi Arabia and the United Arab Emirates. These countries have different rules, and they may not all reach a company like us in the same way.

  • Saudi Arabia's Personal Data Protection Law can apply to a company outside the Kingdom that handles the personal data of people living there. You may use the rights it gives you by writing to us (section 11), and you may complain to the Saudi Data and Artificial Intelligence Authority (SDAIA).
  • The United Arab Emirates and Qatar also have data-protection laws. In Qatar, a shop may need the regulator's permission before it records special kinds of information, such as health details, children's details or reports of a crime.
  • Some places have their own data law, such as the DIFC and ADGM free zones in the UAE and the Qatar Financial Centre. If your business is in one of them, ask us before you use the Service, because our Terms may not give you every contract term that law asks for.

Wherever you are: our name and address are in section 19, our purposes and reasons in section 4, who receives information in sections 6 and 7, the places it goes to, as far as we know them, in section 8, how long we keep it in section 10, and your rights in section 11. Section 18 says what we offer in Arabic.

United States. Depending on where you live, state law may give you rights over your personal information. If it does, write to us and we will respond as that law requires.

17. Changes to this policy

We post each new version on this page, with the date it was published. Write to us if you want an earlier version. Whenever we publish a new version, people who sign in to a shop's account are asked to read it before they continue. If a change is important, we also email account owners at least 30 days before the new version applies, unless it is urgent for security or legal reasons. A change of provider, including a change from one kind of provider to another that section 7 describes, is not a change that needs anyone to agree again, and we need not announce it first. We keep the list in section 7 current. The exceptions are a change that moves the servers that hold Shop Records to a country outside the United States (section 8), or that uses information for a new purpose. That is an important change, and we announce it to account owners first, as the notice rule above says. We will not use information we already hold in a materially different way without first asking the people concerned, or the shop where the records are the shop's. We cannot reach a shop's customers or staff who have no login, so the shop passes on what they need to know.

18. Languages

The English text of this policy is the one that applies. We may also publish Bangla and Arabic versions or summaries to help you. If a translation differs from the English, the English applies, unless a law that applies to you and cannot be changed by agreement says otherwise.

19. How to reach us

Oribi Tech, LLC, a Virginia limited liability company (Virginia State Corporation Commission entity ID 11301511). Woodbridge, VA 22193, USA.

Email: info@oribi360.com. Phone: +1 904-554-8184.

فتح في علامة تبويب جديدة ↗

نحتفظ بما يثبت ذلك: النسخة التي قرأتها، والوقت، وعنوان بروتوكول الإنترنت الخاص بك ومتصفحك.

هل تريد حسابًا فقط؟ يمكنك طلب صلاحية الوصول بدلًا من ذلك.

© 2026 Oribi Tech, LLC · Oribi 360 منتج من Oribi Tech, LLC.