Legal
Privacy Policy
Effective date: November 4, 2026
1. Who We Are
The Algiz Guard (“we,” “us,” or “our”) operates the membership platform available at https://www.thealgizguard.com and the associated iOS and Android applications (collectively, the “Service”). This policy explains what personal data we collect, how we use it, and your rights regarding that data.
For questions, contact us at support@thealgizguard.com.
2. Data We Collect
Account & Profile Data
- Full name and email address (provided when you register)
- Profile photo (uploaded voluntarily; stored in Supabase Storage)
- Timezone (automatically inferred from your device at signup; can be changed in Settings)
- Membership roles and program access status
Usage Data
- Pages visited and features used within the Service
- Login timestamps and IP address (retained by Supabase Auth for security purposes)
- Content you create: community posts, comments, challenge check-ins, Time Audit entries
Device & Notification Data
- Push notification subscription tokens (web VAPID tokens or FCM/APNs tokens for native apps), stored only when you explicitly enable notifications
- Device platform (iOS or Android) - used only to route push notifications correctly
Payment Data
- Subscription status and Stripe customer ID - we store metadata about your subscription (active/cancelled, product) but never store card numbers or full payment details. All payment processing is handled by Stripe.
Advertising & Analytics Data
On public marketing pages, sign-in and account pages (including registration and password reset), the Skill Extractor, and this Privacy Policy and the Terms of Service, we load Google Analytics and the Meta Pixel. Neither tool is loaded inside the logged-in members’ area or in the native iOS and Android apps.
From those pages, the tools may receive:
- Pages you view, the page that referred you, and the date and time of the visit
- Browser type, device type, operating system, language, and screen size
- IP address. Google uses it briefly to estimate a general location, such as city or region, and states that Google Analytics 4 does not store the full IP address. Meta receives the IP address with the page event.
- Cookie identifiers, and a Meta ad-click identifier when you arrive from a Facebook or Instagram ad
Automatic advanced matching is turned on for the Meta Pixel. When you enter information in a form on one of those pages - including event registration, checkout sign-up, and sign-in - Meta may read the field in your browser, hash it, and send only the hash. The fields enabled for this are email address, phone number, and first and last name. Date of birth and gender are also enabled, and would be hashed and sent only if a form on the page asks for them. Our forms do not currently ask for date of birth or gender. City, state, postal code, and country are turned off and are not sent by the pixel. The pixel does not send an external customer ID.
Separately, our server sends Meta an event when a registration succeeds for the men’s circle, a masterclass, the Skill Extractor, or a workshop (a Lead), and when a Stripe checkout is paid (a Purchase). These are sent even if the browser blocks the pixel. Each event can include hashed copies of the email address, phone number (if we have one), and first and last name from that signup, plus a hashed id for the contact or account. A Lead also includes the IP address and browser of that request. We attach the Meta cookies from the browser, and for a purchase we store those cookie values on the Stripe Checkout session so the later Purchase event can include them. A Purchase also includes the amount, currency, and the checkout id. These server events do not include a password, card number, date of birth, or gender.
Passwords, payment card numbers, and health or government-identification information are not sent to Meta or Google. Google Analytics records that a page was viewed and, under its default settings, events such as scrolls, outbound clicks, and that a form was used. It does not receive what you typed into the form.
3. How We Use Your Data
- To create and manage your account and membership access
- To deliver the features of the Service (community feed, events, coaching tools, etc.)
- To send push notifications and in-app notifications you have opted into
- To respond to support requests
- To detect fraud, enforce our Terms of Service, and maintain platform security
- To comply with legal obligations
- To measure how public pages are used, see which ads lead to visits and sign-ups, and show our ads again to people who have visited the site (remarketing)
We do not sell your personal data for money, and we do not give it to anyone other than the providers in Section 4. Using the Meta Pixel, the server events described above, and Google Analytics for advertising measurement and remarketing can count as “sharing” for cross-context behavioral advertising under California law. Browser controls in Section 7 limit the cookies and the pixel. They do not stop a Lead or Purchase event after you submit a form or pay. Email us to opt out of those server events.
4. Third-Party Services
We share data with the following third parties only to the extent necessary to operate the Service:
Our backend-as-a-service provider. Hosts our database, authentication, and file storage. Your profile data, content, and session information are stored on Supabase infrastructure.
Payment processing. Handles all subscription billing. We share your email with Stripe to create a customer record; Stripe stores payment card data on our behalf under their PCI-DSS compliance. We also store the Meta cookie values from your browser on the Checkout session so a completed payment can be matched to an ad. Stripe does not use those values to advertise to you.
Used to deliver push notifications to iOS and Android devices. Your device’s FCM registration token is shared with Firebase only to route notifications to your device.
Video conferencing links for coaching sessions and group calls. We store Zoom join URLs and recording links; we do not share your personal data with Zoom.
Our hosting provider. Processes web traffic and may retain server logs including IP addresses for up to 30 days.
Loaded on the pages described under Advertising & Analytics Data. The Google tag sets cookies and receives the technical information listed there, including pages viewed and events such as scrolls, outbound clicks, and form interactions. It does not receive the contents of form fields. We use it to understand traffic and how those pages perform. If our Analytics property is linked to other Google advertising products, Google may also use this information to measure ads. Google’s partner policy is at How Google uses information from sites that use its services.
Loaded on the same pages. The pixel sets a cookie and receives the technical information listed under Advertising & Analytics Data. Through automatic advanced matching it may also receive hashed copies of an email address, phone number, and first and last name that you enter in a form, and of date of birth or gender if a form asks for them. Hashing happens in your browser before the value is sent. Meta uses this to match the visit to a Facebook or Instagram account, attribute sign-ups and other actions to our ads, measure how those ads perform, and include the browser in audiences for remarketing. The server events described under Advertising & Analytics Data send the same kinds of hashed customer details, along with the IP address and browser on a Lead, the Meta cookies, and the purchase amount, currency, and checkout id on a Purchase. Meta states that it discards the hashes after that match. Meta’s description of this feature is in its advanced matching help.
5. Data Retention
We retain your personal data for as long as your account is active or as needed to provide the Service. If you close your account, we will delete or anonymise your personal data within 30 days, except where we are required to retain it for legal or financial compliance purposes (e.g., Stripe transaction records, which Stripe retains per their own policy).
Community posts and comments may remain visible after account deletion in anonymised form (“Deleted User”) unless you specifically request their removal.
Meta states that it discards hashed customer information after using it to match a visit. Other event and cookie data sent to Google Analytics and Meta is kept by those companies under their own retention settings. Closing an account on our Service does not delete that event data from their systems. The browser controls in Section 7 limit cookies, Google Analytics, and the pixel. Email us to opt out of later Lead and Purchase events.
6. Your Rights
Depending on your jurisdiction, you may have the right to:
- Access - request a copy of the personal data we hold about you
- Correction - update inaccurate data (most profile data can be changed directly in Settings)
- Deletion - request deletion of your account and associated data
- Portability - request your data in a structured, machine-readable format
- Objection - object to certain processing activities
- Withdraw consent - disable push notifications at any time in Settings or your device settings
- Limit advertising data - use the browser controls in Section 7 to limit Google Analytics and the Meta Pixel. Those controls do not stop a Lead or Purchase event after you submit a form or pay. Email us to opt out of those server events. California residents can use either path to opt out of sharing for cross-context behavioral advertising.
To exercise any of these rights, email us at support@thealgizguard.com. We will respond within 30 days.
7. Cookies & Local Storage
The logged-in members’ area uses a browser cookie to keep you signed in (via Supabase Auth). That area does not load Google Analytics or the Meta Pixel. The native iOS and Android apps use on-device storage for the same session purpose and do not load either tool.
On the pages listed under Advertising & Analytics Data, we also use:
- Google Analytics cookies (including _ga and a cookie beginning with _ga_). These distinguish browsers so we can measure visits. They typically last up to two years.
- Meta cookie (_fbp), which identifies the browser to Meta, typically for about 90 days. If you arrive from a Facebook or Instagram ad, Meta may also set _fbc to store that ad click.
You can block or delete cookies in your browser. Blocking them limits the pixel and Google Analytics. It does not stop the server from sending a Lead or Purchase event, with the hashed details described above, after you submit a form or pay. To opt out of those server events, email support@thealgizguard.com. You can also limit browser advertising directly:
- Google Analytics: Google Analytics Opt-out Browser Add-on
- Google ad personalization: Google Ads Settings
- Meta ads: Ad preferences and Off-Facebook activity
- Industry opt-out pages: YourAdChoices and Network Advertising Initiative
8. Children’s Privacy
The Service is intended for users aged 18 and over. We do not knowingly collect personal data from anyone under 18. If you believe a minor has provided us with personal data, contact us at support@thealgizguard.com and we will delete it promptly.
9. Security
We implement industry-standard security measures including encrypted connections (TLS), row-level security on our database, hashed session tokens, and role-based access controls. No method of transmission over the internet is 100% secure; we cannot guarantee absolute security but commit to promptly notifying affected users in the event of a data breach.
10. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the “Effective date” at the top of this page and, for material changes, notify you via email or an in-app notification. Continued use of the Service after changes constitutes acceptance of the updated policy.
11. Contact
The Algiz Guard
Email: support@thealgizguard.com
Website: https://www.thealgizguard.com
© 2026 The Algiz Guard. All rights reserved. Terms of Service