Privacy Policy
This privacy notice explains what sparkspheretechnologies collects on sparkspheretechnologies.site and in a restaurant or retail workspace, why it is used, and how long the story of an outlet is kept.
Sample storefront detail — street address, phone number, and mailbox are not confirmed for this record. This notice is published for sparkspheretechnologies at sparkspheretechnologies.site. It is not a certificate of legal compliance, and it should be reviewed by the business before it is treated as final.
Who this notice is for
This notice is for people who visit sparkspheretechnologies.site, people who create an account, and people whose information appears inside a merchant workspace. A merchant is the restaurant, café, cloud kitchen, grocery, boutique, or other retailer that uses the platform. A guest or shopper is the person at the table or the counter. A staff member is someone on the roster. These roles are different, and the merchant is usually the one who decides why a guest’s visit or a cashier’s shift needs to be on record.
sparkspheretechnologies provides the software that holds those records. On this storefront the account, the demo request, and the support note are stored in the browser on the device you are using. A future hosted workspace would store outlet records on systems operated for the product. Until that hosting is confirmed, do not treat this website as a place that already receives card numbers, government identity numbers, or a live stream of bills from a real till.
Information you give us
When you create an account you give a name, a work email, a business name, and a password. The password is stored with the account in browser storage so the login form on this demo can recognise you. That storage is not a production identity system, and anyone with access to the device and the browser profile can read it. Use a password you can change, and do not reuse a password from a bank or another service.
Contact, demo, support, career, partner, and integration forms ask for the fields marked on the form. A message can include whatever you type. Do not include a guest’s payment card, a staff member’s government identifier, or a medical note in a demo message. The form does not need them, and this site is not a secure channel for that kind of detail.
Information created by using the platform
A visit to a page can create a technical log such as the time, the page address, and a browser type. This demo does not run a separate analytics collector. Browser storage is used for the account, for saved form notes, and for a recovery code while a password reset is in progress. Those keys stay on the device until you clear them or use logout for the session key.
Closing a ticket stores items, quantities, tenders, and totals in ₹. Voids, goods inward, and attendance are stored too. Those records are personal when they identify a guest, a rider, or an employee.
Direct ordering may store a pickup name and a phone number. Own-fleet dispatch may show the assigned rider. Collect only what the handoff needs.
How information is used
Account details are used to sign you in, to show your name on the account page, and to keep your saved notes attached to the browser. Demo and support notes are used so you can see what you sent. They are not transmitted to a server by this storefront.
Workspace records are used to run the outlet: to print or show a bill, to decrement a recipe, to prepare a tax invoice layout, to show a repeat visit, and to prepare pay inputs from attendance. They are also used to investigate a support question you raise, such as a day that will not lock or a sync that finished late.
We do not sell guest lists. We do not use a guest’s visit history to advertise unrelated products from other companies. A merchant may use its own customer list to speak to guests it is allowed to contact. That decision, and the consent or other basis for it, belongs to the merchant. The platform is the place the list is kept, not a broker of the list.
Who else may see information
People you invite into an account or a workspace can see what their role allows. A cashier should see the open ticket, not the payroll run. An accountant may see totals and tax, not a rider’s home note. Role design is part of the product because over-sharing is a common failure in small outlets where everyone shares one login. Outlets should not share one login.
We may disclose information if a competent authority requires it under applicable law, and we may share what is needed to prevent abuse of the service, such as an attempt to break into another merchant’s outlet. We do not volunteer operational data for advertising marketplaces. Supplier names for a future host are not listed because they are not confirmed, and no payment processor is appointed by this text.
How long information stays
Browser account data stays until you delete it from the browser or overwrite it by removing the saved keys. Logout removes the session key. It does not delete the registered user record, because you may want to log in again. You can remove that record by clearing site data for this domain in the browser.
On a hosted workspace, sales, tax, attendance, and guest profiles are kept for the period the merchant must operate and account for, then follow the export window after cancellation. The exact period should be confirmed with the merchant’s adviser rather than left to a silent default.
After cancellation, an export remains available for thirty days. After that window, the hosted copy of the workspace is removed from active systems, subject to any record the merchant has already downloaded and subject to any copy a law requires to be kept. Backups, if they exist in a future hosting design, age out on their own cycle rather than remaining as a second live outlet.
Security and international access
This demo relies on the browser’s storage and on the lock of the device. That is appropriate for a demonstration and inappropriate for a real dinner service. A hosted workspace would need access control, encryption in transit, and a way to restore a day that was recorded. Those measures will be described when they are actually in place. This page does not claim a certification, an audit seal, or a government accreditation.
People may open the product from more than one country. Until hosting locations are confirmed, do not assume a country of storage. sparkspheretechnologies.site is not aimed at children, and merchants should not build a child’s profile in the guest book.
Your choices
You may avoid optional storage. The account page shows the name, email, and business on the session, and you may correct the name and business there.
You may ask a merchant to correct or delete a guest profile the merchant holds. The merchant should have a way to do that inside the workspace. If you contact us about a guest record, we will point you to the merchant unless we are the right party for a platform log that does not belong to the merchant’s day-to-day book.
Changes to this notice will be posted on this page with a clear heading. Continued use of the website after a change means you have the new text available. A change that would use workspace data for a new purpose needs a fresh look at whether that purpose is fair to guests and staff, not only a quieter paragraph.
Commercial schedule shared by this site
The same commercial numbers apply on every policy page of sparkspheretechnologies.site. Prices are in Indian rupees (₹). Tax is confirmed on the quote. sparkspheretechnologies does not name a payment processor, a bank, or a card network, and this storefront does not collect payment fields. Software access is provisioned within one business day after the order is accepted. Optional hardware kits, meaning a terminal, a receipt printer, or a cash drawer, are dispatched within three business days. Typical transit inside India is four to eight business days. Delivery outside India waits for written confirmation. A kit the carrier confirms as lost before delivery is marked is replaced or refunded at the kit price in ₹. An unused, complete kit in its original packaging may be returned within fourteen days of delivery. The merchant pays return freight unless the kit arrived damaged or differed from the quote. Damage or a mismatch must be reported within forty-eight hours. A hardware order cancelled before dispatch is refunded. After dispatch, the fourteen-day return rule applies. A subscription is reversed in full, in ₹, within seven days of the start if no live sale has been posted. A live sale is a closed ticket from real service, including one later voided. Labelled training tickets do not count. After a live sale, or after seven days, the current period is not refunded. Cancellation stops the next renewal. Access lasts to the end of the paid period, then an export remains for thirty days. Plan changes apply on the next billing date unless requested in the first seven days, when the difference in ₹ is settled at once. An unused kit may be exchanged within fourteen days, with any price difference settled before the replacement ships. Approved refunds are credited within ten business days to the method recorded on the order, or noted in ₹ if no method was recorded.
Questions about this page can be sent through the contact form. Sample storefront detail — street address, phone number, and mailbox are not confirmed for this record.