Cafex Privacy Policy

Cafex on Google Play keeps hidden-menu notes on one unlocked phone

This Privacy Policy takes effect on 2026-10-05. Zhuzhou Jiwen Trading Co., Ltd. is the controller for Cafex. Letters reach No. 62 Xianfeng Road, Yushifang, Xiadu Subdistrict, and that street is the line printed here. Write TextsStatut@gmail.com. Desk staff usually send a first reply inside 15 business days.

Cafex is a Google Play Android listing for specialty-cafe notes. After unlock, a reader can open hidden-menu jottings and shop lists already stored on that phone. A visit card can take a new interior still. A tasting card can take a spoken remark. Those files remain with the unlocked Cafex copy.

Play store listing text may mention a community. Cafex still accepts no uploaded cafe post and stores no comments on servers we operate, and it has no public board. Cafex is not a map utility and does not carry a drink to a table.

Hidden-menu notes carry no subscription charge after Play unlock.

Distribution is worldwide except Brazil. Later appendix notes speak in turn to California, Virginia, and the EU/EEA.

What a visit card loses when Camera or Microphone stays unused

If the still control stays unused, Camera writes no new shop interior on Cafex, while typed hidden-menu notes remain available. Camera is not in the background while Cafex sits unlocked. Turn Camera off under Android Settings and later interiors halt on this listing.

If the spoken-remark control stays unused, Microphone writes no new tasting remark on Cafex, while typed notes and local stills remain available. Microphone is not in the background while Cafex sits unlocked. Revoke Microphone from Android Settings and later tasting remarks halt on this listing.

A picture already on the phone may be placed on a visit card through the Android picker. That picker is not a Photos runtime grant. The chosen picture stays on the phone. Location remains unused. Video capture remains unused. Photos are not in the background on a visit card. Location is not in the background.

A visit card can show an interior the reader just took, or a picture already sitting in the gallery. Neither path uploads that image. A tasting card can hold a spoken remark the reader records on purpose. Skipping that remark leaves the typed hidden-menu line as the whole card.

Eighteen-year readers, and children's meanings on this listing

Cafex is written for adults who have already reached 18 years, written eighteen on this notice. Minors must not keep Cafex. The publisher does not look for personal information from anyone under 18, and does not knowingly collect such information from a minor.

Children's sensitive identifiers stay unused on Cafex. Biometric data stays unused on Cafex. Artwork on the listing addresses grown readers. Screens inside Cafex were never designed around a child audience among grown visitors, are not marketed at children, and are not aimed at children. A visit card carries no child-focused features for grown readers. If a parent or a guardian believes children's information arrived at TextsStatut@gmail.com, that adult may write the same mailbox asking for access to it, deletion of that mail, plus stopping processing of that arrived mail on Cafex.

A grown household adult who finds a minor opened Cafex should write that mailbox. Staff then look only at mail that actually arrived. Shop interiors and tasting remarks that never left the phone stay with the person who unlocked that copy.

Inbox copies versus shop stills that never leave

Personal data we hold is a copy that actually arrived.

TextsStatut@gmail.com is one arrival path. The written body, the sending address, and any attachment the writer included become inbox records. Desk staff do not ask for a shop interior as an attachment. If an interior still arrives anyway, staff treat it as mail content, not as a Photos upload taken from Cafex.

The other arrival path is the in-app legal link. A hosting provider writes HTTPS server logs, and those logs let the host return the matching legal page to the handset.

Photos stay on the phone as shop interiors or picker pictures, and attaching one is optional; Cafex still opens typed hidden-menu notes without a new still. Microphone audio stays on the phone as tasting remarks, and recording one is optional; Cafex still opens typed notes without a spoken remark. App activity stays on the phone as save marks, list filters, and local caches, and that cache is required for the listing to remember a shop list between visits. None of those three groups is collected.

On this listing we do not sell personal data held at the mailbox. A reader who wants a mailbox path anyway may write TextsStatut@gmail.com a request to opt out of selling inbox records we hold.

This Privacy Policy is meant to stay consistent with the Play Data safety answers printed for Cafex covering collection status, sharing status, purpose meaning, and required versus optional fields.

A holder can like a shop, save it, and keep a short list of places to try. Those taps write only to the unlocked copy, so they never become a hosted feed, a comment thread, or a message another reader can open on a server we operate.

Grounds for processing: why we process mail and host records on Cafex

This chapter states why we process each copy that leaves a visit card. The General Data Protection Regulation (GDPR), when it applies, treats the grounds below as the legal bases for those visit card jobs.

• Arrived mail is read so staff can answer a privacy question about Cafex, a guardian question, or a product question about visit cards.
• Those logs let the host deliver this printed Cafex Privacy Policy on the handset, those Terms of Use pages, and the children's notice after the holder opens the matching in-app Cafex link.

Shop interiors plus tasting remarks stay outside those jobs on Cafex.

Where the GDPR applies on this listing, legitimate interests cover answering arrived mail, returning hosted legal pages, and keeping this inbox free of misuse. Performance of a contract covers completing a letter the writer already started about a visit card. A legal obligation covers correspondence a statute requires this desk to retain. Consent applies only if a writer freely sent a tasting note we had no separate visit card reason to hold; the same writer may withdraw that consent through a later note mailed to TextsStatut@gmail.com.

On Cafex, targeted advertising plus sale of personal data, together with profiling for a similarly serious visit card decision, stay unused as one group, because this package ships without an ads kit.

A privacy ask can name a field in a letter that already arrived. A household-adult ask can name children's information that already arrived. A product ask can name how a visit card stores an interior on the phone. Each ask is answered from the inbox, not from a hosted member page.

The hosted-page scene, and who receives those logs

When a holder opens a hosted Cafex legal page, the host writes HTTPS server logs, then those logs support the return of that page to the handset.

Personal information is not sent abroad except once that hosted Cafex legal page is opened and those logs are written.

Cafex never presents a registration screen, because visit cards never become a member record on our servers.

Cafex never reads a Google advertising ID from the handset, and no Android advertising identifier is collected on Cafex, because this package ships without an ads kit.

Opening a hosted legal page can let the host write those logs and then deliver the printed Privacy Policy, those Terms of Use pages, or the children's notice. Cafex has no other outbound path.

A reader who never opens the in-app legal link does not start that host scene. Typed hidden-menu notes, shop interiors, tasting remarks, and the local shop list stay on the phone in that case. Staff still read mail that a writer chose to send to TextsStatut@gmail.com.

How long mailbox letters, host records, and onboard files remain

Mailbox keep times follow the list below.

• Mailbox letters stay until the ask closes on Cafex, unless a statute asks this desk to retain the letter longer.
• Host records from a hosted legal page fall after that short host window.
• Shop interiors, tasting remarks, and list caches remain until this package is removed or Android storage is cleared on Cafex.

A later dated edition of this Privacy Policy governs from the date printed on it. After that date, use of Cafex follows the wording then shown on the in-app privacy link. Because Cafex keeps no hosted account, a holder reads the current wording on that link.

Uninstall ends the onboard copy. Clearing Android storage for this package has the same local effect. Neither step wipes a letter that already arrived at the mailbox. Write TextsStatut@gmail.com if that letter should be erased.

Staff handling rules, then HTTPS locks

Clerks open arrived mail to reply to the writer, leaving shop interiors off any marketing album and keeping letters away from an outside supplier this listing does not keep. Absolute security on this listing is not promised.

HTTPS protects a hosted legal page in transit. Only clerks who answer privacy letters may open inbox credentials. Local stills and tasting remarks sit behind the holder's device PIN and the phone's screen lock.

Staff do not browse visit cards on a phone they do not hold. They do not pull a tasting remark from a device they do not unlock. They work from mail that reached TextsStatut@gmail.com, and from those logs when a hosted legal page was opened.

Erasure, a portable extract, then access on Cafex

Write TextsStatut@gmail.com. The usual reply clock is fifteen business days.

A holder may ask desk staff to erase inbox mail that actually arrived. A holder may ask for a portable extract of personal data sitting in that inbox. A holder may request access to the personal information held at this Cafex mailbox. Restriction is available while a visit card dispute stays open: ask desk staff to pause further use of a letter sitting in the inbox. Visit cards that never left drop away after an uninstall, or a storage wipe. Because registration is unused on Cafex, there is no hosted member page left to shut, so there is no account-deletion flow.

A portable extract covers inbox records we hold. It does not invent a shop interior that stayed on the phone. It does not invent a tasting remark that stayed on the phone. Those files leave only if the holder copies them by a path the holder chooses outside this listing.

Correction of inaccurate or incomplete personal data

Write TextsStatut@gmail.com to request correction of inaccurate or incomplete personal data that actually arrived. Name the field that is wrong. Staff amend the named field and do not treat that letter as a full wipe.

If the named field sits in a letter we hold, staff can amend it. If the named field sits only on a visit card that never left, the holder amends it on the phone, or removes the package.

Appendix for California, Virginia, and the Union

Under the California Consumer Privacy Act (CCPA) as amended, each California resident may ask to know whether we collect personal data or share it, which inbox records we hold on Cafex, the source of those records, and which party received a disclosed copy. The same resident may ask this desk to erase a letter we hold, then correct a mistaken field, plus receive a portable travelling copy. You may ask us to confirm whether personal data is sold on this listing; personal data is not sold here. Cafex does not share personal data for those listed cross-context ads. A California resident may mail a do-not-sell request by writing TextsStatut@gmail.com about inbox records still held. Sending a privacy letter does not reduce Cafex service.

Readers in Virginia, under the Virginia Consumer Data Protection Act (VCDPA), may ask whether this desk processes personal data they named, then access, correct, delete, plus obtain a portable extract. Targeted advertising, sale, and profiling that yields a legal outcome or a similarly serious outcome do not apply on Cafex, because those three activities stay unused on this listing. TextsStatut@gmail.com remains open if a Virginia reader still wants to refuse such a sale.

When the GDPR applies, readers seated in the EEA and the United Kingdom may seek access, rectification, erasure, restriction, plus a portable file, plus an objection where those interests are the basis used. A shop interior never leaves this listing for those regional asks, because that interior stayed on the unlocked visit card. A Union reader may lodge a complaint to a supervisory authority that sits for the reader's home Member State, or else for the United Kingdom. If an inbox letter rested on consent, a withdrawal is sent to this mailbox and leaves the earlier reply in that inbox.

A California ask, a Virginia ask, and a Union ask all use TextsStatut@gmail.com. Staff treat each ask as a privacy letter. They do not ask the reader to open a hosted member page, because Cafex never built one.

Data Protection Officer for Cafex correspondence

There is no separately named data protection officer on Cafex. Write that desk at TextsStatut@gmail.com.