[ Privacy Policy ]

1. Information We Collect

Account Information

When you create an account, we collect:

• Email address
• Authentication credentials and session information needed for supported sign-in methods
• Name (if provided)
• Authentication-provider identifiers

You may also sign in using Google Sign-In, in which case we receive basic profile information (name, email) from Google in accordance with your Google account settings.

You may also sign in using Sign in with Apple, in which case we receive basic profile information (name, email, or a private relay email if you choose to hide your email) from Apple in accordance with your Apple ID settings.

Business and Inventory Data

• Company/business information, company settings, memberships, roles, and permissions
• Inventory and asset data, including item names, categories, quantities, stock/availability status, locations, photos, expiration information, and other details you enter
• Historical inventory events (scans, edits, imports) you or your team perform
• Employee/team member information if you invite others to your company account

Item Photos

Item photos you upload are stored server-side in object storage and associated with inventory items. The current item-photo serving route is publicly readable: someone with an object URL may be able to retrieve a photo without signing in. Do not upload a photo on the assumption that its URL is restricted to company members. Removing an association in the app is not a verified guarantee that every underlying storage object is physically deleted.

Menus, Documents, and Recipes

We process uploaded menu images and PDFs, extracted menu content, recipes, ingredient mappings, and confirmed quantities. Original restaurant menu files use a separate private storage namespace and are blocked from the public item-photo serving route.

AI Photo Recognition

When you use AI-assisted recognition, menu extraction, or recipe suggestions, item photos, menu images/PDFs, and prompts containing relevant category or context information are transmitted to Anthropic's Claude API. Images may be encoded as base64 for transmission. Anthropic processes those inputs to produce recognition results, extracted content, or recipe suggestions. Its handling is subject to the applicable service terms and agreement; we do not promise zero retention, immediate deletion, or exclusion from model training without verification of the applicable account terms and configuration. See Anthropic's privacy policy at anthropic.com/privacy.

Clover Connection and Sales-Related Records

When an authorized company owner connects Clover, we store merchant identifiers and connection credentials, with access and refresh tokens encrypted server-side. Authorized reads can include inventory items, orders, line items, modifiers, payment state/timing, refund identifiers and amounts, and related identifiers and ingestion/deduction records. These records are received from Clover for connected inventory, ingredient usage, and availability functionality. The reader accesses order, payment, and refund endpoints, but GLOUT does not process Clover payments through this reader. This policy does not make a blanket claim that upstream responses contain no financial or customer-related fields.

Tasks, Meetings, Chat, and Work Activity

We process task and recurring-task information, meetings/calendar information, chat messages and conversation participation, recorded employee work activity, and calculated performance information. Activity records can include actor/company identifiers, activity types, timestamps, item/task references, and metadata. Performance reporting includes qualifying inventory changes and task completions, rather than simply counting app opens or raw scans.

Push Notifications

If you grant notification permission, we collect and store a device push token on your user record to deliver supported alerts and chat notifications. Notification text and routing identifiers are sent to Expo's push service; content can include inventory alerts or chat text. You can disable notification display/delivery through your device's notification settings. Revoking OS permission does not establish that a stored token has been deleted. Logging out revokes the authentication session but does not clear the stored push token; account deletion removes the user record and its token field.

Barcode and QR Scanning

If you use the app's scanning features, we process images or scanned data (such as barcodes or QR codes) solely to identify and record inventory items. This scan data is not stored as an image — only the resulting item information is saved.

Device and Usage Information

• Application usage events used to understand and improve the Services; the Firebase/Google Analytics integration includes a session event carrying an app user ID, so not all analytics is anonymous
• Operational logs associated with running, diagnosing, and protecting the Services

Website Contact and Browser Storage

If you contact us by email, we receive your email address and the information you include in your message. The reviewed public marketing-page source does not include a marketing analytics tag or active local-storage/session-storage use. The published site was observed setting a hosting-layer cookie named GAESA with an approximately 30-day expiry; its purpose and consent requirements must be confirmed before this draft is adopted. The website also loads fonts from Google-hosted endpoints, which receive the associated network request information. A sidebar preference-cookie helper exists in the component library but is not used by the current public marketing pages. This review does not establish all hosting-layer logs or the storage behavior of the separately linked web app and third-party websites.

Payment Information

The mobile subscription flow uses Apple's In-App Purchase system. Apple handles the purchase transaction; GLOUT receives and verifies receipts and subscription lifecycle information to determine plan access. This is distinct from sales-related information read from an authorized Clover connection, including payment state/timing and refund amounts.

2. How We Use Your Information

We use the information we collect to:

• Provide and maintain the core inventory management functionality of the app
• Store and display inventory, assets, photos, menu uploads, recipes, and history
• Provide requested AI recognition/extraction and recipe suggestions
• Read authorized Clover records, support separately activated ingredient tracking, and monitor unavailable items independently of ingredient deductions
• Provide company permissions, tasks, meetings, chat, and personal or authorized team performance reports
• Send you notifications about inventory conditions (low stock, out of stock, items expiring soon) based on your notification preferences
• Provide analytics and insights about your inventory (e.g., inventory value, turnover, overstock detection) as part of paid subscription tiers
• Authenticate your account and protect against unauthorized access
• Communicate with you regarding account matters, such as password resets
• Improve and maintain the app's performance and reliability

3. How We Share Your Information

We do not sell your personal information. The following providers receive or process information for the functions described below. Their exact agreements, subprocessors, processing regions, and any international-transfer arrangements must be confirmed before this revised draft is adopted.

• Clover: Provides merchant OAuth authorization and authorized inventory, order, payment, and refund responses. Information received from Clover is used for the connected functions described above; connecting does not by itself activate ingredient deductions.
• Anthropic/Claude: Receives item photos, menu images/PDFs, and relevant context/prompts for AI recognition, extraction, and recipe suggestions.
• Expo push service: Receives device push tokens, notification text, and routing identifiers to deliver inventory and chat notifications.
• Firebase/Google Analytics: Processes application usage events, including a session event with the app user ID.
• Resend: Receives recipient email addresses and transactional/alert content for password-reset and inventory emails.
• Apple: Handles Apple sign-in where used, purchases, receipts, and subscription lifecycle information.
• Google sign-in: Provides authentication identity information when used.
• Google Fonts: The marketing website requests its typeface from Google-hosted font endpoints, which receive request information associated with loading those resources.
• Replit infrastructure: Provides application hosting and object-storage processing. Application records also reside in PostgreSQL.

We may also disclose information if required by law or to protect the rights, safety, or property of our users or the app.

4. Data Retention and Deletion

Self-service account deletion applies only to the authenticated user's own account. It removes the user record, associated authentication tokens, memberships, and the push-token field on that record. If another company owner exists, the company remains. If the departing user is the sole owner and other members remain, an eligible earliest-joined member can be promoted. If no other members remain, the deletion path deletes the company and associated cascading database records.

Selected inventory-history and notification references have their user IDs cleared. This is not complete anonymization: it does not establish removal of all names or identifying information in messages, metadata, or historical content. Shared company records may remain when the company continues.

Company deletion includes private menu-source object cleanup and reports failure if that cleanup cannot safely be completed. Physical deletion of every item-photo object after removing a photo, deleting an item, or deleting a company has not been established. No immediate deletion from every backup or third-party system is promised.

Owner-confirmed Clover disconnection removes production and sandbox credentials, stops tracking and availability monitoring, and cancels pending connection attempts while preserving inventory, recipes, and history. It does not uninstall GLOUT from Clover or cancel subscriptions. Provider-side credential revocation/retention and deletion timing require separate verification.

Automatic Clover cleanup triggered by account deletion is not currently available. Account deletion does not promise Clover disconnection, removal of Clover connection credentials, revocation of Clover authorization, or deletion of Clover-related records. Separate owner-controlled disconnection is distinct from account deletion; retention and deletion of remaining Clover-related data must be verified before this draft is adopted.

Exact retention periods for chat, tasks, performance and historical records, item-photo objects, backups, operational logs, and provider-held data are not yet established for this draft. These periods and deletion limitations must be resolved before adoption; this draft does not invent a universal retention or deletion deadline.

5. Access and Security

Implemented access controls include:

• Company access based on membership and role, with employee editing permissions depending on company settings
• Owner controls for membership/settings and Clover activation, and manager/owner authorization for team-wide performance reports
• Employee access to their own performance details
• Explicit-participant access for private conversations; being an owner or administrator does not provide an override
• Server-side storage and encryption of Clover access and refresh tokens

These controls do not make item-photo object URLs private, as described above. No method of electronic storage or transmission is 100% secure, and we cannot guarantee absolute security. Businesses are responsible for appropriately informing employees about recorded activity and performance reporting; implementation alone does not establish that employees have received notice or consented.

6. Your Rights and Choices

Depending on your location, you may have rights to:

• Access the personal information we hold about you
• Correct inaccurate information
• Request deletion of your account and associated data
• Make an export request for information associated with you, subject to applicable rights and the data available
• Manage notification permissions through your device settings

To exercise these rights, contact us at info@glout.app, or use the available editing and self-service account-deletion controls. This does not promise that every record type has a self-service export or deletion control. Company-held/shared records and private conversations may require a review of your membership, participation, applicable rights, and the business's responsibilities.

7. Children's Privacy

The proposed account minimum remains 13 years old, subject to applicable age requirements in supported markets and legal review before adoption. The App Store's 4+ content rating is not the account minimum. The Services are not intended for children under 13. If you believe a child has provided personal information, contact us so we can review and address it.

8. International Users

GLOUT TECHNOLOGIES LLC is formed in Texas. If you access the Services outside the United States, information may be processed outside your country by the providers used for those Services. The supported markets, hosting/database regions, provider processing locations, and appropriate transfer arrangements have not been fully confirmed for this draft. This statement is not a claim of GDPR, CCPA, or other legal compliance, or of a verified international-transfer mechanism.

9. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify users of material changes through the app or via email. Continued use of the app after changes constitutes acceptance of the updated policy.

10. Contact Us

If you have questions or concerns about this Privacy Policy or your data, contact us at:
Email: info@glout.app