Logrico Privacy Notice

This Privacy Notice explains how Logrico handles personal information for the customer portal, friend and check-in features, merchant pilot tools, rewards and receipt features where available, support requests, and related pages at logrico.com.

1. What Logrico does

Logrico provides customer accounts with Member IDs, friend discovery, short-lived social check-ins and replies, and merchant-supported rewards or receipt features where available. Some features are pilot, merchant-specific, limited release, or coming soon.

2. Information we collect

Customer account information

• Name, email address, Firebase user ID, authentication provider, and account timestamps.
• Customer Member ID used by merchants to send receipts to the correct account.
• Optional display name, profile details, friend relationships, friend requests, check-ins, replies, selected-friend sharing choices, and related timestamps if the customer uses those features.
• Optional purchase notes, vault entries, reminders, comments, sharing recipients, and related timestamps if the customer uses those features.

Merchant account information

• Merchant name, merchant email, Firebase user ID, merchant profile details, configured loyalty settings, location or register identifiers, and merchant-issued reward or receipt history where applicable.
• Where integrations are enabled, authorization, connection state, and limited merchant account metadata needed to support those integrations.

Social and friend information

• Searchable account data such as Member ID and display name so signed-in users can find other users and send friend requests.
• Check-in content, reply content, selected duration, selected-friend audience choices, and timestamps.
• Friend-request status, friendship state, and activity needed to show who can see or reply to a post.

Receipt, rewards, and transaction information

• Receipt number, merchant/store name, date/time, amount, currency, line items, taxes, discounts, notes, and delivery status where applicable.
• Customer Member ID used to assign merchant-supported points, rewards, or receipts.
• Rewards balances, points earned, points shared, rewards redeemed, and merchant program settings where applicable.
• Where supported integrations are connected, transaction and device metadata such as location IDs, order IDs, payment IDs, or register/device names needed to match or display merchant-related data.

Operational and security information

• Basic logs, request metadata, webhook event IDs, error messages, timestamps, device/browser details, and security signals needed to operate, secure, debug, and prevent abuse of the service.

3. Information we do not need

• We do not ask customers for full payment card numbers.
• We do not intentionally store full card numbers, CVV codes, or magnetic stripe/chip data.
• We do not sell customer receipt history.
• We do not use customer receipt history for third-party advertising profiles.
• We do not intentionally collect government-issued ID numbers unless a user sends them to us in a support request.

4. How we use information

• Create and maintain customer and merchant accounts.
• Let signed-in users discover other users by Member ID or display name, send friend requests, and manage social connections.
• Show check-ins to the audience selected by the posting user and allow replies within that workflow.
• Connect merchant integrations that the merchant authorizes.
• Assign merchant-supported points, rewards, or receipts to a customer account when a merchant enters the customer's Member ID or uses a supported matching workflow.
• Let customers view, search, organize, delete, and retrieve data made available in their account.
• Let customers share selected records, comments, or split information with other people they choose to add.
• Prevent fraud, abuse, duplicate webhook processing, unauthorized access, and account misuse.
• Provide support, handle privacy requests, troubleshoot issues, and comply with legal obligations.

5. Friend discovery and social visibility

Signed-in users may be able to find other users by Member ID and, if a user has set a display name, by that name. Friend requests must still be accepted before a friendship becomes active. Check-ins may be visible to all active friends or a selected subset of friends, depending on the sender's choice for that post.

6. Integrations and merchant authorization

Where Logrico offers merchant integrations, merchants authorize those connections directly. We use the approved permissions only to provide the relevant merchant workflow for that merchant, such as receiving transaction details, matching a Member ID, awarding points, or displaying a receipt in Logrico where applicable.

7. Legal bases and consent

Where privacy law requires a legal basis, we process information to provide the service requested by customers and merchants, to meet legitimate business and security interests, to comply with law, and where required, based on consent. Customers should only provide a Member ID to a merchant when they want a merchant-supported feature tied to their account.

8. Sharing and service providers

We use trusted providers to operate Logrico. These may include:

• Third-party providers used for merchant integrations where enabled.
• Google Firebase and Google Cloud for authentication, hosting, backend functions, database, and secrets.
• Payment and billing providers if a merchant pays for a subscription or invoice.
• Email, support, or communications tools if you contact us for help.
• Authorities, regulators, courts, or law enforcement if required by law.

9. How sharing works

If you choose to share a vault item, purchase note, split record, or related comment with another Logrico user, the information you choose to share becomes visible to that recipient within Logrico. Please share only information you are comfortable disclosing.

10. Retention

• Customer accounts are kept while active and for a reasonable period after closure where needed for security, legal, accounting, or dispute purposes.
• Friend relationships, requests, and related account records are kept while needed to operate the service, unless deletion is requested and we are not legally required or permitted to keep them.
• Check-ins and replies may disappear from the user-facing feed after their intended visibility window, but we may retain related records for a reasonable period for security, abuse prevention, support, legal, and operational needs.
• Receipt, rewards, and customer-saved purchase records are kept so users can retrieve them later where those features are offered, unless deletion is requested and we are not legally required or permitted to keep them.
• Merchant integration connection records are kept while the merchant account is connected and for a reasonable period after disconnecting for audit, security, support, billing, or dispute needs.
• Operational logs, diagnostics, and webhook records are kept as needed for security, debugging, duplicate prevention, abuse prevention, and legal compliance.

11. Security

We use technical and organizational safeguards appropriate to the sensitivity of the information, including Firebase authentication, protected secrets, access controls, request validation, rate limiting, and data minimization. No online service can guarantee absolute security.

12. Your choices and rights

• Customers can choose not to provide a Member ID and can avoid using merchant-supported features tied to that ID.
• Customers can request access, correction, deletion, or export of their personal information where applicable.
• Customers can manage some information in-product, such as account deletion where available, and can contact us for other requests.
• We do not sell personal information or share it for cross-context behavioral advertising.
• Merchants can disconnect supported integrations or contact us for help.
• Privacy requests may require identity verification and may be limited by legal, security, accounting, or fraud-prevention requirements.

California residents

If the California Consumer Privacy Act, as amended, applies to your information, you may have the right to know, access, correct, delete, and obtain information about our collection, use, and disclosure of your personal information, subject to exceptions. You may also have the right not to be discriminated against for exercising those rights. Logrico does not sell personal information or share it for cross-context behavioral advertising.

Canadian residents

If Canadian privacy law applies to your information, you may request access to personal information we hold about you and ask that inaccurate or incomplete information be corrected, subject to applicable exceptions.

13. International processing

Logrico may process and store information in Canada, the United States, and other countries where our providers operate. By using Logrico, you understand that service providers may process information outside your country or province.

14. Children

Logrico is not intended for children under 13. We do not knowingly create accounts for children under 13.

15. Changes

We may update this Privacy Notice as Logrico changes. We will post the updated version with a new date. Material changes may be communicated in-product or by another reasonable method.

16. Contact

Privacy and support requests: [email protected]
Please include “Privacy Request” in the subject line if you are asking for access, correction, deletion, or export.