Noshra Privacy Policy

Material scope of this privacy policy and the parties bound

Use of Noshra on a Google Play Android copy follows this sequence. The holder installs the package, unlocks the phone, and may then pin a tin-lid card for a packed noon-desk meal. Rice, noodles, salad, or thermos soup may occupy that card. A typed name and a portrait still may sit on the card as its face. Each of those files stays on the handset the holder already controls.

In this privacy policy, Noshra means that Android package. The controller of personal information that actually arrives in connection with Noshra is Hongdong County Bijie Technology Co., Ltd. Paper mail and notices use this street: HongDong County, Xin Village Township South Duan Village 9 Group No.0942. The privacy inbox is StemqjVats@gmail.com. This wording takes effect on 2026-10-05.

Noshra is published for a grown reader who has already reached 18. Minors must not use it. Anyone short of eighteen is outside the audience this noon-desk lookbook was issued to serve.

What this privacy policy says about gathering, disclosure, the reason a record is handled, and which listed practices are required and which remain optional is intended to remain the same as the Data safety answers shown for Noshra on Google Play.

Result of granting Camera or Microphone on this Android copy

The result of a Camera grant is a still of the tin lid or of the packed meal, written into the lookbook on the phone. Camera waits for an explicit tap on a control the holder can see. Camera use is not in the background. After the holder leaves the capture screen, Camera does not keep watching the desk. What is stored is a still, not a moving picture.

A later tap can open the Android photo picker. The result of that tap is a still already sitting on the phone, copied into the same tin-lid card. The chosen still does not leave the device.

The result of a Microphone grant is a spoken pantry note stored in the same lookbook. Microphone waits for an explicit tap on a control the holder can see. Microphone capture stays not in the background. After the holder stops the recording, Microphone does not keep listening.

Revocation is done in Android Settings for this package. Once Camera is refused, fresh stills cease; typed names, portrait stills already saved, and spoken notes already stored continue to work. Once Microphone is refused, fresh spoken notes cease; stills and typed lines continue to work. Text features that never needed a sensor remain available.

A Camera tap runs only with the holder's consent. Withdraw that consent by refusing Camera in Android Settings. Microphone follows the same withdraw path.

Personal information that remains on the unlocked handset

Two sources matter. Most personal information is created on the unlocked phone and never travels. A thinner set reaches Hongdong County Bijie Technology Co., Ltd. only if the holder sends a letter to the inbox named above.

A tin-lid card on the handset can hold a still just taken, a still chosen through the Android photo picker, a spoken pantry note, a typed name, a portrait still used as the card's face, and working caches the package keeps while the holder moves between saved cards. A still filed under Photos never leaves this handset. Microphone audio is the spoken pantry note that stays in the same local card. App activity, meaning those working caches, is likewise confined to that handset. The controller does not receive a copy of any of those objects.

What staff can actually hold is a letter sent to StemqjVats@gmail.com. The letter might ask what is on file, ask for a line to be fixed, or report that a minor used the phone. Until such a letter is written, the inbox has no file about the lookbook.

Noshra does not collect a Google advertising ID. Stills and spoken notes stay inside the tin-lid card, so an advertising identifier is not read and is not used.

The controller does not sell personal information linked to this noon-desk lookbook. Anyone who still wants to opt out of selling may send a do-not-sell request by email to StemqjVats@gmail.com. That inbox method stands even though no sale is carried out.

A rice card or a thermos-soup card is already inside the installed copy. Pinning that card does not attach an in-app charge, and this Play listing carries no subscription and no paid catalog.

Purposes of processing and the legal bases relied on

A reader in the Union or the EEA is protected by the General Data Protection Regulation (GDPR). Those readers receive the bases listed next. When the GDPR applies, the legal bases below attach only to processing that actually happens.

Performance of a contract covers two acts: delivering a hosted legal text the holder asked to read, and answering a mailbox request that seeks a right described in those texts.

A legitimate interest in answering privacy-request mail covers the reading of a letter that arrived at StemqjVats@gmail.com.

Legal obligation covers a mailbox letter only where a court, a regulator, or a similar mandate requires that correspondence to be kept or shown.

The purposes themselves are narrow. A letter is read so staff can reply. A page request is handled so the chosen legal text can be returned. Tin-lid cards are not processed on the controller's systems, because those cards never arrive.

HTTPS server logs a hosting provider writes so a requested legal page can be returned

A tap that loads a hosted legal text starts the sole outbound HTTPS request this copy makes, and the host uses those logs to return the opened legal page. A hosting provider is the recipient that records HTTPS server logs when that request is made. After that disclosure, the host consults those logs and sends back the file the holder asked to read. The terms of use may be requested on its own tap. The children's notice may be requested on a later tap. This privacy policy may be requested on a further tap.

A letter sent to StemqjVats@gmail.com is seen by the staff who answer that inbox. That is how a privacy request is handled.

A rice still, a spoken pantry note, and a typed name stay on the unlocked handset. Those objects are not sent with the request that reaches the host.

Protective measures and retention listed by class of record

Technical steps and staff rules are described together. No system is promised to be completely secure.

The request that loads a hosted legal text travels over HTTPS. Only people who need a mailbox letter in order to answer it may open that letter. Staff cannot open a tin-lid card on a remote system, because no such card is held there.

Retention, listed by class of record:

• Tin-lid cards, including stills, spoken pantry notes, typed names, portrait stills, and local caches, last until the holder removes Noshra or wipes this package's storage through Android Settings. Because those files never reached the controller, no remote purge timetable applies.
• After the host has used those logs to return the chosen text, the host deletes them on the host's own cycle. The controller does not announce a numbered deletion day for equipment it does not run.
• Mail that arrived at StemqjVats@gmail.com is kept while the answer is being prepared. Staff aim to finish a verified request within 15 business days. The letter is then erased unless a legal obligation requires a short remainder.

Removing the package, or wiping its storage, is how a tin-lid card ends. A mailbox request to StemqjVats@gmail.com is how a letter that actually arrived ends.

Erasure, a portable extract, rectification, then inspection

Every request in this chapter is sent to StemqjVats@gmail.com. Staff deal with a matched letter in the order set out here.

Erasure is first. The writer may ask staff to delete a mailbox letter the controller actually received. Files that stayed on the phone are removed by uninstalling Noshra or by wiping this package's storage. Staff cannot remotely wipe a card they never held.

A portable extract is second. The writer may ask for a copy of a letter staff still hold, returned in a form the writer can keep. The extract covers what arrived at the inbox. It does not invent a remote copy of a tin-lid card.

Rectification is third and stands on its own. The holder may request correction where personal information held in the inbox is inaccurate. The same mailbox request covers rectification where personal data is incomplete. Both requests are submitted by email to StemqjVats@gmail.com. Staff verify the writer where that is appropriate and then fix the line they hold.

Inspection is fourth. The writer may ask staff to say what, if anything, is held about that writer. Until a letter is sent, the honest answer is that staff hold no lookbook file.

These rights attach to mailbox letters and to those logs. They do not attach to a remote membership, because none is created.

Absence of a hosted account and overseas movement of personal information

Saving a rice card or a thermos-soup card never opens a sign-in screen. A remote membership is not created, and no login wall is placed in front of the lookbook. Account deletion therefore does not arise; there is no account page inside the package.

Aside from the legal-text request described above, personal information does not travel to another country. Those logs may sit on the host's equipment wherever that equipment is located; the purpose remains delivery of the chosen text.

California, Virginia, and EEA claims mapped on one mailbox

Duties that depend on place and duties that depend on the claim a reader makes are answered at one inbox: StemqjVats@gmail.com.

Under the California Consumer Privacy Act, also called the CCPA and later amended by the CPRA, a California resident may write StemqjVats@gmail.com and ask the controller to confirm whether Noshra collects or shares that resident's personal information. The package does not share for advertising. Sale of personal information does not occur on this listing. The same inbox accepts a do-not-sell request and any wish to opt out of selling.

Virginia readers rely on the Virginia Consumer Data Protection Act, abbreviated VCDPA. Profiling, targeted advertising, and any sale of personal data are not run on this noon-desk lookbook, so those VCDPA categories do not apply. A reader who still wants to refuse a sale uses StemqjVats@gmail.com.

A Union or EEA reader may lodge a complaint. Residence, the place of work, or the location of the alleged infringement decides the supervisory authority that can receive the complaint.

Data Protection Officer function without a named officer

There is no dedicated Data Protection Officer. StemqjVats@gmail.com is the address for that function as well as for every other privacy letter.

Adult audience for this noon-desk lookbook and guardian correspondence

The package was not designed for children. Store sentences are not marketed toward children. The Play listing speaks to adults who pack a noon-desk meal. In-app screens are not aimed at children, because this lookbook records those meals for grown readers. Child-focused features are absent from the Play listing and from the screens on this copy.

Children's sensitive identifiers stay unused, and biometric data of a child is not gathered. Knowing collection of personal information from a writer below 18 does not occur.

If a parent or guardian believes children's information reached the inbox, that adult may write StemqjVats@gmail.com seeking access, deletion, and stopping processing of what staff actually received. Uninstall or a storage wipe clears files that never left the handset. Staff cannot halt a remote copy of a card they never held.

Substitution of later wording of this privacy policy

When this privacy policy is revised, the replacement carries a later date and is shown inside Noshra. From the day that later date appears, the newer wording governs. The holder sees the change by opening the in-app legal link. There is no mailing list for revisions, because no hosted membership exists to receive one.