Shelfexa
Back to home

Shelfexa Daily Android / Privacy

Privacy Policy

This policy covers the Shelfexa Daily Android application (Shelfexa Android / Shelfexa) and the Shelfexa corporate website. Mobile application and website data handling are described separately below.

Application / brand: Shelfexa Daily — Shelfexa. Privacy, data access and account deletion contact: support@shelfexa.com. These disclosures describe the current Free Release; inactive features are not presented as active.

Türkçe okuyunRequest account deletionRetention and deletion

1. Mobile application: account, profile and work data

Name, email address, Firebase UID (account identifier) and session information are processed through Firebase Authentication for accounts and session management. Google Sign-In is used for Firebase sign-in if the user chooses it.

Profile and work-context data include department, role, company and store information. Depending on the features used, task, expiry-date, shift, planogram, barcode/catalogue and team-operation records are processed through Cloud Firestore/Firebase. Salary/payroll records are also processed if the user enters them.

These data operate the account and relevant features, including tasks, shifts, expiry tracking, catalogue queries and company/store team operations. Shared company/store work records can have different deletion boundaries from personal account records.

2. Notifications, device information and camera

If notifications are used, a push token and technical device/installation information are processed through Expo and Firebase Cloud Messaging (FCM) to deliver notifications to the correct application installation.

The camera is used for barcode scanning. GPS location, microphone and contacts are not used.

Selecting an image from your device for a profile, task or planogram is initiated by you. Custom Firebase Storage uploads are disabled in the current Free Release; the selected file itself is not uploaded to Shelfexa servers. A local URI/reference may be retained in the relevant record to use the image for that feature; saving a reference does not mean the file is uploaded.

Your Google avatar or external product images may be displayed from their own providers. This is different from uploading a file selected from your device to Shelfexa servers; the relevant provider processes the image request on its infrastructure.

3. Kendine İyi Bak and optional Wear sharing

Water, break, feeling, optional smoking and personal-note records in Kendine İyi Bak are primarily stored on the device and are not uploaded to the server. They support personal tracking and should not be confused with work records uploaded to Firestore.

If the user enables optional Wear sharing, the shared information is limited to water and date/time information. This is not sharing the full wellbeing history or personal notes.

4. Service providers and sharing

Firebase Authentication and Cloud Firestore are active services for account/session handling and the cloud work records described above. Google Sign-In is used for authentication when selected by the user. Expo and FCM are used for notification delivery when that feature is used.

A barcode may be sent to Open Food Facts when needed for a product lookup, to obtain product/catalogue information. This does not describe sending account or wellbeing records to that service.

The RevenueCat package is present, but purchase and restore flows are inactive in the current Free Release. Custom Firebase Storage photo flows are also disabled in this release.

The current application has no data sale or advertising-targeting flow. This does not mean service providers have no technical request, operational, security or logging processes of their own. The listed services may process data on their infrastructure when the relevant feature runs.

5. Secure data handling

Data in transit are protected using HTTPS. Firebase and API access controls are used to restrict access to account and application data. This policy does not claim end-to-end encryption, absolute security or that providers keep no logs.

Do not send passwords, one-time sign-in codes or unnecessary sensitive records in support requests. Information needed for ownership verification should be limited to the request.

6. Retention and deletion policy

Cloud data are retained while needed to operate the account and features used. Device-held wellbeing and other local records are separate from cloud account records. Retention depends on the purpose for which the data are needed and applicable obligations; no unconfirmed fixed day/month/year periods are stated.

In-app account deletion deletes the Firebase Authentication account and the personal Firestore user tree; cleanup of related local device data is attempted. This is not temporary account deactivation or freezing.

Shared company/store operation records may be retained only to the extent needed for genuinely applicable business-continuity, security, fraud/abuse-prevention, audit or legal-obligation purposes. These records may contain user references, but are not an unlimited retention exception. Once no longer needed, deletion or, where possible, de-identification is applied to remove the association between personal records and the account.

Some technical logs, account-deletion records, provider logs/backups and copies previously transferred by the user to third-party services may follow separate retention cycles. Copies transferred by the user to other services are distinct from records held by providers processing data on behalf of Shelfexa. Relevant records, applicable retention reasons and required provider-side deletion steps are assessed separately when handling a deletion request; immediate erasure of every external copy is not guaranteed.

No absolute deletion guarantee is given for unverified remnants such as old Firebase Storage images. These are separately assessed during a deletion request and removed to the extent possible. Technical limits alone are not a reason for indefinite retention; deletion of the personal account and personal Firestore tree is distinct from assessment of these separate records.

7. Account deletion and privacy requests

You can use the in-app account deletion flow or email support@shelfexa.com to request deletion of your Shelfexa Android account and associated personal data without reinstalling the application.

To initiate a web request, you must actually send the email to support@shelfexa.com; opening an email draft does not submit a request or delete the account. Include your account email. Ownership verification may be required to prevent unauthorized deletion. After verification, the request is processed within a reasonable time without unnecessary delay; you receive an email response about completion, including the scope and reasons for any retained records. Review of shared records and provider processes may affect timing; no unconfirmed fixed deadline is promised.

The account deletion page explains the request pathway, the scope of in-app deletion and records that may remain. You can also contact support@shelfexa.com with privacy questions or requests concerning data access, retention and deletion.

8. Separate scope: corporate website

The website is informational and does not provide access to mobile accounts or records. The demo form asks for your name, company, store count, employee count and email address. When submitted, these details are sent to Shelfexa through its configured email provider, Resend, for delivery to support@shelfexa.com; the form does not save them in the website database. If sending fails, the form reports that and provides support@shelfexa.com as an alternative.

Submitting the form sends its contents to Shelfexa and the email providers involved in delivery. The email service may process message contents under its own service terms; the website cannot verify delivery. Hosting infrastructure processes technical requests, such as IP address, requested URL and browser headers, for page/file delivery and abuse prevention, and may use operational logs or cookies. Google Fonts requests send technical request information to Google’s font services.

The website application code has no added advertising trackers. HTTPS does not mean hosting/email providers keep no records. No unconfirmed retention periods or automatic deletion promises are made for their records.

Privacy contact

Send privacy and deletion requests for Shelfexa Daily / Shelfexa Android to: support@shelfexa.com.