Scope and responsible owner
This policy concerns the Talabaty mobile application and talabaty-app.com. Talabaty helps sellers manage orders, products, inventory, customer information, business statistics and settings.
Legal owner: Radwan Atme. Country: Israel. Contact: support@talabaty-app.com. The website development agency is not identified as the owner of application data.
Information connected with the app
Accounts: email/password and Google authentication are currently supported through Supabase Auth.
Business records: customer information and order history; order details, products, quantities, order and payment statuses; product names, prices, descriptions, images, categories and stock; business, language and currency settings.
The dashboard uses sales, revenue, order and inventory information entered in the application.
Why information is used
The described information supports account creation and authentication, managing customers, orders, products and inventory, tracking payment status, displaying business statistics and configuring the app.
Recording an order’s payment status does not establish that Talabaty collects card details or processes payments.
Collect only what is necessary
Limit processing to information necessary for accounts, products, inventory, orders, customers, recorded payment statuses, statistics and support. Explain the purpose of each field and whether it is required or optional; optional fields must not become a condition of the core service.
Current website forms do not request identity documents, card details, contacts or customer information for marketing. Do not send support other customers’ data or sensitive details unnecessary for the request.
Limit staff/provider access by need and review information and permissions to remove what is no longer necessary. General acceptance of terms does not authorize AI training or a new purpose for customer data.
Offers and marketing: a separate, optional choice
If promotional or marketing messages become available, send them only after a prior, express and separate opt-in identifying the sender, purpose and chosen channel. Creating an account, using this website or accepting the terms or privacy policy is not marketing consent.
The subscription choice must be unchecked by default and must not be required for the core service. Users may refuse or withdraw without losing their account or core features. Provide a clear, easy unsubscribe method in messages; withdrawal can also be requested at support@talabaty-app.com.
Keep necessary service messages, such as security and account recovery, separate from promotions. Do not add advertising to bypass the user’s choice. Retain only necessary evidence of consent including time, wording and channel, and respect withdrawal before any subsequent marketing send.
This website currently has no marketing subscription form or marketing-list collection. Any future subscription must implement these controls in operation; consent wording in the terms alone is insufficient.
AI, customer data and website content
We do not permit account, customer or order information, including conversations and images, to be used for AI model training, improvement or fine-tuning without prior, express, separate and purpose-specific permission from the data subjects or a person with valid legal authority to act for them. A seller’s permission alone must not be assumed sufficient for customer data.
Before any future AI feature processes information, explain the data sent, provider, purpose, retention and no-training settings. Verify provider terms: API access alone does not establish a training exclusion. Do not send personal information to a public AI tool without the necessary authority and consent.
Refusing training does not prevent use of core management features. Respect future withdrawal as required by law and explain actual limitations before obtaining consent; do not promise reversal of completed training where that is not possible.
Some website content, copy and visuals were prepared with AI assistance. This does not mean AI features are currently available in the app.
Generated or edited output may need verification and is not evidence of unavailable features or legal/financial advice. Operational AI features remain planned and are not enabled by this website.
Information about a seller’s customers
Sellers may enter information concerning other people: their customers. Enter only information needed to manage orders, with appropriate authority to use it and notices to those people where required.
A person whose information appears in a seller’s records can contact the relevant seller or support to route a privacy request. Do not include other customers’ records or unnecessary personal information in an enquiry.
Providers, sharing and processing locations
The confirmed technical infrastructure includes Supabase Auth for authentication and Supabase PostgreSQL for application data. Google authentication is available; it is distinct from Instagram or WhatsApp messaging integration.
Additional external tools or processing purposes require disclosures matching the actual implementation.
Device permissions, analytics and tracking
Support for product images does not establish that camera or photo-library permission is requested. Disclosures must match the actual image-selection implementation.
Retention and deletion periods
Operational account information is retained while the account is active and only as necessary to provide the service and maintain records the user chooses to keep. An active account does not justify unnecessary collection or unrelated reuse.
After account ownership and the deletion request are verified, associated operational personal data must be deleted within 30 days of verification. Review covers related records, images and files, not just the authentication record.
Personal-data backup copies must expire or be deleted within 90 days of the verified deletion request. Temporarily retained backups must not be used for routine operations or marketing, and restoring a backup must not reactivate deleted data.
Where applicable law or a binding order requires particular records to be retained, identify the data, reason and retention period and inform the requester where legally permitted. Restrict use to that reason; an exception is not permission for indefinite retention.
Access, correction and deletion
Request access to your personal information, a readable copy, correction of inaccurate information, or deletion of your account and associated data using this page’s request links or support@talabaty-app.com. You do not need the app installed to initiate a website request.
Support verifies ownership and authority before disclosing, correcting or deleting information. Never email passwords, verification codes, recovery links, session tokens or unsolicited documents. Do not disclose another seller’s or customer’s data to someone without authority.
Deletion is a request handled after verification, not an automatic destructive button. The approved periods are 30 days for operational data and 90 days for backups from verification, subject to identified lawful exceptions.
If a request cannot be fully fulfilled, explain the reason, remaining scope and available review route. This policy does not waive mandatory rights or available complaints to the relevant authority.
Protecting information
Keep sign-in methods secure, do not share passwords or recovery links, and contact support if you suspect unauthorized access.
Website, application and current scope
The current website presents product information and support links and prepares email-confirmation and password-recovery pages. An email link opens the user’s email application and does not send a message by itself.
When you change the website’s accessibility options, larger-text, contrast and reduced-motion choices are saved locally in your browser so they can apply when you return or change languages. Remove them using Reset to defaults or by clearing the website’s browser data.
Storefronts, a unified inbox, WhatsApp/Instagram/Facebook messaging, order automation and AI analysis are planned features, not current messaging or AI processing practices described by this policy.
Approval and changes
An approved policy must reflect the released application and match its store disclosures. Review it when integrations or processing practices change.