Handoff Academy / Legal
Privacy Policy
What information this website uses, how we handle it, and the choices available to you.
Effective and last updated
Read our Terms of ServiceHandoff Academy is operated by Miranda & Valdes Collective, LLC, a Florida limited liability company ("MVC," "we," "us," or "our"). This Privacy Policy explains how we handle information in connection with this website and communications about it.
What this website does. It presents the Academy and sells Academy memberships through a checkout page hosted by Stripe. Marketing enrollment has no customer account database. The separate summit guide uses verified attendee accounts, private notebooks, a professional attendee directory, registration insights and limited first-party engagement records, as described below. Marketing pages have no live AI chat or newsletter signup. The summit guide offers the optional AI roadmap interview described below. Public marketing pages offer optional analytics and Meta advertising measurement, controlled by your privacy choices. Summit has no advertising analytics. The website does not send text messages. Ordinary website requests still involve technical information, and we receive information you choose to send us by email.
1. Scope of this policy
This policy applies to handoffacademy.com and its Vercel deployment aliases, including the brand guidelines, demonstrations, and the enrollment and checkout flow. It also covers correspondence you send us about Handoff through the listed contact address.
It does not replace the privacy notices for the existing Mother of AI website, the Academy member portal, or a separate third-party service. Your membership is created and delivered in that portal, which sends its own account-setup email and is governed by its own notice. We will update this policy before introducing member accounts on this website, member tools or other materially different processing beyond what this policy describes.
2. Information we handle
2.1 Checkout and purchase information
When you choose a plan, this website asks Stripe to create a checkout session. It sends Stripe the plan you selected, the number of seats for a team order, the result and version of the readiness check, the offer version and access term, the version of the Terms you are asked to accept, the IP address of your request, a marker identifying this website as the source, and, if you arrived through an ambassador's referral link or entered an ambassador code, that ambassador referral code so the ambassador can be credited.
Stripe's hosted checkout page, not this website, collects your name, email address, phone number, billing address, payment method, and your acceptance of the Terms of Service. We never receive your full payment-card number. Stripe handles that information under its own Privacy Policy.
After a completed payment, Stripe sends this website a signed notification containing your name, email address, phone number, plan, amount paid, and Stripe's session, payment, and customer identifiers. We use it to email an internal purchase notification to our own team and, when a members contact list is configured, to add your name and email address to that list at Resend, our email provider.
For a team order, we send Stripe the seat count you chose, and Stripe collects your details as it does for any purchase. After your payment completes, you enter each learner's full name and email address in the Academy member portal. The portal uses those details to create the learners' accounts and send their invitations under its own privacy notice. This website never receives them.
Your access is provisioned in the Academy member portal, which sends your account-setup email and handles your member information under its own notice. Mother of AI is another brand operated by MVC, the same company, and the Academy uses one payment account for both brands. The Academy's existing Mother of AI systems therefore also receive the same notification, record your purchase, and may add your email address to a Mother of AI contact audience. MVC uses those records across its Handoff Academy and Mother of AI brands. Service providers supporting those systems also process the information as described in Section 5. We do not sell this information.
2.2 Academy Prep Checklist
If you ask for the Academy Prep Checklist, we use the email address you enter to send you that one email and to avoid sending it to you twice. Requesting it does not add you to a list, create an account, or start marketing email.
With your analytics choice, a successful checklist request also sends a lead event to Google Analytics. With your advertising choice, the browser and our server report a lead event to Meta after our email provider accepts the checklist email. Both Meta reports use the same event identifier to avoid counting the request twice. Google Analytics does not receive your email address. If you accept the expanded advertising choice described in Section 2.5, our server also sends Meta a SHA-256 hash of the checklist email address for matching, together with permitted browser identifiers, your IP address and browser/user-agent details. Your readiness answers are excluded.
2.3 Information you choose to send us
If you email support@handoffacademy.com, Resend, our email provider, receives your message and forwards its sender and recipient addresses, subject, and body to a monitored support mailbox on our Mother of AI domain so a person on our team can respond. Attachments are named in the forwarded copy but are not included; a team member retrieves them from Resend when needed, and Resend keeps the received message for about 30 days. We may also receive information needed to respond to a privacy, copyright, security, or legal request. Please provide only what is necessary and avoid sending passwords, payment-card details, government IDs, sensitive health information, or confidential third-party material.
On public marketing pages, apart from checkout and the checklist request described above, the website does not ask you to submit personal information. Contact links open your chosen email application; the website does not send the message for you. The separate Summit guide is described in Section 2.7.
2.4 Blog videos
The blog offers optional video walkthroughs hosted by Mux. A Mux player loads only when you choose to play a walkthrough. Mux then processes requests and playback diagnostics, including technical information such as IP address, device/browser details and video playback events, to deliver the video. See the Mux Privacy Policy. Ordinary article reading does not load the Mux player. Short silent portal clips are served by this website.
2.5 Technical request information
Our hosting provider, Vercel, processes information needed to serve and protect website requests. This may include IP address, browser or device information, requested URL, referring URL when supplied by your browser, request time, response status, and security or diagnostic logs. Such information can be personal information under applicable law.
Images, fonts, and downloadable brand assets are served from this website's infrastructure. Requests for those files involve ordinary delivery information; downloading them does not require registration. With your analytics choice, public marketing pages use Google Analytics 4 for visits and enrollment events, and Microsoft Clarity for interaction measurements, heatmaps and masked session replay. With your additional advertising choice, Meta Pixel measures public page views, content views, enrollment steps, checklist requests and checkout starts. Fit-check events record only that the step started or finished, not your answers or readiness result. Enrollment inputs are masked from session replay.
Browser requests to these providers also convey ordinary technical information, including your IP address, browser/user-agent details and referring-page information when the browser supplies it. Pseudonymous identifiers are not the same as anonymous data: a provider may associate them with information it already holds under its own privacy policy. Handoff reuses MVC's Mother of AI Meta dataset, so consented events from both brands can appear together in Meta's measurement tools.
These browser tools do not run on Summit, checkout result, redemption or brand-guideline pages. Google Analytics receives page URLs without query parameters or fragments. We separately retain bounded campaign tags such as source, medium and campaign, and advertising click identifiers when you allow the relevant category. Known campaign parameters are removed from the address bar after capture. Meta and Clarity do not start while other query parameters remain. Automatic Meta form collection and automatic advanced matching remain disabled by this integration. We manually supply only the matching fields described below.
For a paid Academy checkout that carries your permitted attribution, we attach campaign tags and pseudonymous browser/session identifiers to the Stripe purchase record. With the expanded advertising choice, we also attach the visitor IP address and browser/user-agent details from the checkout request, so later server reporting uses that visitor context. After Stripe verifies payment, our server sends the purchased product, final seat count, currency and amount to Google Analytics and/or Meta according to those choices. An irreversible hash of the transaction identifier prevents duplicate reporting. Meta matching uses advertising browser/click identifiers and the same hashed random visitor identifier in browser and server events. With your expanded advertising choice, server events also include your visitor IP address and browser/user-agent details, plus SHA-256 hashes of the email address and, for a purchase, international-format phone number you provide when available. We normalize and hash those contact details before sending them to Meta; raw contact details and their hashes are not put in the attribution cookie or sent to Google Analytics or Clarity by this integration. Hashing supports matching to information Meta already holds; it does not make the information anonymous. We do not send buyer names, postal addresses, individual readiness answers, gift codes or payment-card details to these measurement providers. Gift redemptions and test payments are excluded. No tracking script is added to the payment confirmation page. Visitors who made the earlier advertising choice are asked to choose again before new advertising collection begins. Earlier checkout records without the expanded permission retain their original, limited matching fields.
The checkout and checklist endpoints keep a short-lived count of recent requests per IP address in server memory so that they can limit abuse. That count is never written to storage and disappears when the server instance stops.
2.6 Local interactions
Readiness answers, plan selections, and a team seat count stay in the current page's browser memory until you continue to checkout. They are not saved in cookies, local storage, or session storage, and they are not linked to an account. Reloading the page resets the application's state. When you continue to checkout, the plan you chose and your readiness result go to Stripe as described in Section 2.1.
The brand manual includes a sample form for demonstrating component behavior. Its input is processed locally for that demonstration and is not submitted to us or stored by the application. Your browser may independently offer its own autofill or form-restoration behavior according to your settings.
Decorative grid and dot effects respond locally to pointer movement and do not themselves identify visitors or send movement data. Separately, with your analytics choice, Clarity can record pointer movements and other public-page interactions for the masked session replay described in Section 2.5. Selecting a color swatch can copy that color value to your clipboard; the site does not read your clipboard.
2.7 Summit guide
The Mother of AI × Handoff Academy summit guide requires an approved Luma registration and verified sign-in. You may sign in with LinkedIn or with your Luma registration email, the event password and a one-time code sent through Resend. We receive the LinkedIn account identifier, name, portrait and email when LinkedIn supplies them. A different or missing LinkedIn email requires the registration-email sign-in path; we never establish ownership from a matching name or profile URL.
We store your registration identity and approval status, professional profile, and the Luma answers about AI comfort, challenges, well-being goals and tech stack in Neon Postgres through Vercel. We do not import addresses, phone numbers, wallet information, registration QR credentials or attribution fields into the guide database. Before the summit, organizers may send you a small number of event-logistics text messages using the phone number you gave at Luma registration, read from Luma at send time and not stored in the guide database; replying STOP stops them. The authenticated people directory shows professional fields only; it does not publish registration emails or survey answers.
Your notebook stores notes, preparation progress, selected contacts and preserved versions of conflicting edits. Note text and replay/conflict payloads are encrypted before database storage, and application endpoints restrict access to the signed-in owner. The application decrypts notes to display them; this is not end-to-end encryption. Organizer database access excludes notebook content and authentication secrets. Your browser stores unsent drafts under your account; sign out on shared devices. An earlier anonymous notebook can be attached only after verified sign-in, proof of its original device or recovery secret, and your explicit attachment action. Its old recovery access is then retired.
Optional roadmap interview. Signed-in attendees can speak or type with an AI interviewer to identify a first task to improve and prepare a brief for a Saturday consultation. OpenAI processes the audio and text needed for this feature. MVC stores text conversations, extracted and reviewed answers, alternate edits, and brief revisions in encrypted, attendee-owned storage separate from professional profiles. Organizer reporting excludes this content. Attendees choose whether to show, copy or export a brief. We retain answers and briefs until deletion is requested and keep account-scoped unsent drafts on the attendee’s device until synchronized or discarded.
MVC does not store audio recordings. We set optional OpenAI Live session and Responses storage to false. This does not establish zero retention: OpenAI may retain abuse-monitoring data for up to 30 days under its applicable API data policy. API inputs and outputs are not used to train OpenAI models by default. Technical voice duration, token counts and generic failure records are kept separately from interview content. No connected work accounts, advertising analytics or automated outreach are added. Avoid supplying passwords, identifiable customer records or confidential information. See OpenAI API data controls.
Organizers can see registration answers, sign-ins, last activity, preparation completion, session-guide opens and resource opens/downloads. A session-guide open does not prove attendance. We do not record note text, searches or selected-contact identities as engagement, and we do not use advertising pixels or session replay. Profiles, registration answers, notebooks and engagement summaries remain available until deletion is requested. Detailed engagement is aggregated and removed after 90 days. Sessions expire after 30 days and can be revoked; verification codes expire after 10 minutes. Protected migration backups expire after 30 days, with provider recovery copies subject to their configured recovery windows. We retain a keyed deletion marker to prevent a future Luma import from recreating a deleted record.
Original photos and workshop resources remain in private Vercel Blob storage and require attendee authorization. Export is available in My Notes. Contact us using the details below for access, correction or deletion requests. We send requested sign-in codes, but no automatic LinkedIn invitations, attendee outreach or marketing messages. A concise explanation is available at Your summit data.
3. How we use information
We use the limited information described above to:
- Deliver the website, images, fonts, and downloads and diagnose delivery problems.
- Create your checkout session, complete your purchase, tell our own team about it, and support your membership, refund request, and guarantee.
- Send the Academy Prep Checklist when you request it, and send member news to a members contact list you can unsubscribe from.
- Record your purchase in the Academy's shared purchase records and, where configured, add your email address to the Mother of AI contact audience described in Section 2.1 so that brand can send Academy news; those messages include an unsubscribe link.
- With your analytics choice, understand public-page visits, interactions and enrollment results, including campaign attribution and paid purchases.
- With your advertising choice, measure Meta ad effectiveness and report public marketing, checklist and purchase events using the identifiers described in Section 2.5.
- Protect the website and our infrastructure against abuse, unauthorized access, and security incidents.
- Respond to messages, questions, support requests, and rights requests you initiate.
- Keep appropriate correspondence and business records, resolve disputes, enforce applicable terms, and comply with legal obligations.
We do not use this measurement to make solely automated decisions with legal or similarly significant effects. We do not sell personal information for money. Optional Meta measurement may constitute sharing for cross-context behavioral advertising or targeted advertising under applicable law; it requires your advertising choice and can be disabled as described in Sections 4 and 10. Google advertising signals and Google ad personalization are not enabled by this integration.
Where a law requires a legal basis for processing, the bases relevant to these activities may include performance of the membership contract you enter at checkout, steps you request before a contract, our legitimate interests in operating and securing the website and answering correspondence, compliance with legal obligations, or your consent where required. We apply those bases only as permitted by the law that applies; this statement does not assert that every privacy law applies to MVC.
Our optional analytics and Meta advertising measurement rely on your relevant privacy choice, separate from buying a membership or requesting the checklist. You can withhold or withdraw that consent without losing access to enrollment.
4. Cookies, tracking, and browser controls
Marketing enrollment does not persist plan selections in browser storage. The summit guide sets essential authentication cookies and stores account-scoped unsent drafts in browser storage. Legacy device cookies are accepted only as proof during an explicit notebook attachment after verified sign-in. If you arrive through an ambassador's referral link, this website sets one first-party cookie named handoff_ref that holds only that ambassador's code. It lasts 30 days, it is used for nothing but crediting that ambassador if you enroll, and it is sent with your purchase to Stripe and to the Academy member portal as part of the purchase record described in Section 2.1. It is not a third-party or advertising cookie. Deleting it or letting it expire stops future crediting; it does not remove a purchase record already created. The handoff_privacy cookie remembers your choice for up to 180 days. Optional tracking stays off until you choose Analytics only or Allow analytics + ads. Earlier analytics permission remains valid; earlier advertising permission does not enable the expanded matching described in Section 2.5. When permitted, handoff_attribution retains bounded campaign tags and pseudonymous measurement identifiers for up to 30 days from its latest permitted update. Google Analytics may use analytics cookies; Meta may use advertising cookies such as _fbp and _fbc. Clarity runs with advertising and analytics cookie storage denied. We do not enable Google advertising signals or personalized advertising.
Use Privacy choices in the footer to change or withdraw your choice. Withdrawing reloads the document to unload tracking scripts and clears the site's measurement cookies. It stops future browser collection but does not erase earlier records or a purchase already submitted with your permitted attribution. Enrollment remains available with Essential only. Global Privacy Control or Do Not Track prevents these optional tools and future checkout attribution, regardless of a saved choice.
Stripe's checkout page is a separate website. It sets its own cookies for payment security and fraud prevention under Stripe's policy, and we do not control them.
Infrastructure providers may process technical signals needed for delivery, security, and abuse prevention. Browser caching of public assets is separate from advertising tracking. You can manage cookies, caching, autofill, and storage in your browser settings.
Global Privacy Control and Do Not Track are treated as a refusal of optional analytics and advertising measurement. They override the saved privacy choice for the browser integration and new checkout attribution. They do not remove purchase records or events already sent, or turn off the essential delivery, payment-security and Summit services described in this policy.
5. How information may be disclosed
We may disclose information for these purposes:
- Hosting and infrastructure: Vercel and infrastructure providers process technical requests and logs to host, deliver, secure, and maintain the website. Information about Vercel's practices is available in its Privacy Notice.
- Marketing analytics: With your choice, Google Analytics processes public page visits, campaign attribution and enrollment/purchase events under Google’s Privacy Policy. Microsoft Clarity processes public-page interactions and masked session recordings under Microsoft’s Privacy Statement.
- Advertising measurement: With your advertising choice, Meta processes public marketing, checklist and purchase events with the permitted identifiers, technical details and hashed contact details described in Section 2.5 under its Privacy Policy, to measure ad effectiveness and support advertising. These analytics and advertising integrations exclude enrollment answers and private Summit content.
- Payments: Stripe hosts the checkout page, processes the payment, and returns the purchase details described in Section 2.1. Stripe receives your name, email address, phone number, billing address, and payment method, and handles them under its Privacy Policy.
- Email delivery, inbound support mail, and contact lists: Resend sends the Academy Prep Checklist and our internal purchase notification, holds the members contact list when one is configured, and receives mail sent to our support address, forwarding its content (without attachments) to the monitored mailbox described in Section 2.3. It processes names, email addresses, message content, and delivery metadata.
- Academy member portal: the portal receives your completed purchase from Stripe, creates your membership, and emails your account-setup link. It handles member information under its own privacy notice.
- The Academy's existing Mother of AI systems: because MVC operates both brands on one payment account, those systems receive the same purchase notification, record the purchase, and may add your email address to a Mother of AI contact audience. MVC uses these records across its two brands, with processing by the service providers described in this section.
- Email and business communications: Our email service providers process correspondence you choose to send, including message content, attachments, addresses, and delivery metadata, so we can receive and respond to it.
- Professional advisers: Legal, accounting, insurance, or security advisers may receive information reasonably needed for their services, subject to applicable confidentiality requirements.
- Legal and safety needs: We may disclose information as permitted or required by law to respond to legal process, investigate abuse, enforce rights, protect people or systems, or address a security incident.
- Business transfers: Information may be disclosed in connection with a merger, financing, reorganization, acquisition, bankruptcy, or sale of the relevant business or assets, subject to applicable law and privacy obligations.
- Your direction or consent: We may disclose information when you direct us to do so or give valid consent.
For the summit, Neon stores the records described in Section 2.7, LinkedIn provides optional account sign-in, Luma supplies registration information, Resend sends requested sign-in codes, and OpenAI processes the optional roadmap interview and recommendation. These services process information under their own notices and their agreements with MVC.
Stripe, Resend, and Vercel handle information in connection with the services described above, subject to applicable law and their agreements with MVC.
The brand-guideline sample form sends no inputs to a provider. Homepage demonstrations do not send your interactions to AI providers; optional analytics can record the public-page interactions described in Section 2.5. We send your selected plan, readiness band, and quiz version to Stripe as checkout metadata. These details also reach the shared purchase systems and internal purchase notifications described in Sections 2.1 and 3. We do not transmit your individual readiness answers. We do not publish private support correspondence as a testimonial or promotional endorsement without separate permission.
6. AI demonstrations and screenshots
Mai, the Prompt Enhancer, and workflow examples on this website are product explanations and demonstrations. They do not start an AI conversation, generate personalized output, create memories, or send your interactions to an AI model. Selecting an example does not upload information about your business.
Screenshots show the existing Academy platform, sometimes within Handoff styling. Viewing one does not sign you in to that platform or make its member-data practices apply to your visit. If you separately use Claude, ChatGPT, or another external tool, review that provider's privacy policy before sharing information there.
7. Email and other communications
This website sends no text messages. It runs no SMS program, no phone-based marketing, and no automated calling. Stripe collects a phone number at checkout so that support can reach a member about a purchase or refund. Providing your phone number at checkout is not consent to autodialed, artificial-voice, or prerecorded marketing calls or texts, and we do not use it for that purpose.
Separately, if you registered for the Mother of AI × Handoff Academy Summit, you may receive a small number of event-logistics text messages from Mother of AI through its registered messaging provider. Those messages use the phone number you gave at Luma registration, which is read from Luma when a message is sent and is not stored in the summit guide database. They are event operations, not marketing. Replying STOP stops them.
Visiting the site, trying a demonstration, or answering the readiness questions does not add you to an email list or create an account. This website uses Resend to send the one-time Academy Prep Checklist if you ask for it, internal purchase notifications to our team, and forwarded support messages to our monitored support mailbox. The internal purchase notifications and support forwards are not sent to you. After a purchase, Stripe emails your receipt and the Academy member portal emails your account-setup link.
When a members contact list is configured, we add buyers to it and use it for Academy news and member updates. Those messages carry an unsubscribe link. Unsubscribing does not affect your membership, your receipt, or messages from the portal.
If you contact us directly, we may reply and retain correspondence as described in this policy. This does not enroll you in marketing. You can ask us to stop optional follow-up correspondence; we may still need to respond to a legal request or preserve records required by law. Separate subscriptions or accounts you already have with MOAI remain governed by their own notices and preferences.
8. Retention and deletion
We retain information only for as long as reasonably necessary for the purposes described in this policy, including responding to correspondence, operating and securing the website, maintaining appropriate business records, complying with law, and resolving disputes.
Retention depends on the type of information, whether a request or dispute remains open, security needs, applicable legal requirements, and relevant provider retention settings. As described in Section 2.3, Resend keeps original inbound messages for about 30 days. Forwarded copies, attachments retrieved for support, and other records may be retained longer for the purposes described in this section; their retention periods depend on the relevant systems and obligations.
When information is no longer needed, we delete it or de-identify it as appropriate. Copies may remain temporarily in backups or provider systems until their normal retention cycles expire, or longer when preservation is legally required.
Marketing enrollment keeps purchase records with its payment and email providers. The summit guide separately retains the records described in Section 2.7. Enrollment creates internal purchase-notification emails and, when configured, audience contacts through our email provider. Records of your purchase live with Stripe, the Academy member portal, our email provider, and the Academy's existing Mother of AI systems, each under its own retention practices. A deletion request for purchase information is handled through those systems and may be limited by tax, accounting, and fraud-prevention obligations.
The browser-cookie lifetimes in Section 4 do not set the retention period for event records held by Google, Microsoft or Meta, or attribution attached to a Stripe purchase record. Those records are retained separately according to their purpose, applicable provider settings and policies, and legal obligations. Withdrawing consent stops future browser collection; use the contact details in Section 10.4 to request access or deletion of existing records.
9. Security
The public website uses HTTPS to encrypt information in transit. We use reasonable safeguards appropriate to the limited information and services involved, including access controls for operational systems and hosting-provider security capabilities.
No transmission, email system, or storage method is completely secure. We cannot guarantee absolute security. Please keep your devices and email account secure and avoid sending unnecessary sensitive information. If a security incident requires notice to individuals or authorities, we will provide notice as required by applicable law, including Florida's Information Protection Act where applicable.
10. Privacy rights and choices
10.1 Rights that may apply
Depending on your location and which laws apply to MVC and the processing, you may have rights to confirm whether we process your information; access it; correct it; request deletion; receive a portable copy; restrict or object to certain processing; or withdraw consent where processing relies on consent. Withdrawal does not affect processing that was lawful before withdrawal.
Where applicable, you may also opt out of sale, advertising sharing, or targeted advertising; use an authorized agent; appeal a denied request; and exercise rights without unlawful discrimination. Optional Meta measurement may constitute advertising sharing under applicable law. Choose Essential only or Analytics only to withhold or withdraw advertising permission; recognized Global Privacy Control also disables it. Exceptions may apply for security, legal obligations, dispute resolution, another person's rights, or other legally permitted purposes.
10.2 Florida, California, and other U.S. residents
State comprehensive privacy laws, including Florida's Digital Bill of Rights and California's CCPA/CPRA, have applicability requirements and business thresholds. This policy does not represent that MVC meets all those thresholds. Where a law applies, we will honor the applicable rights and response requirements.
The relevant categories are identifiers and contact information you provide at checkout or in correspondence, commercial information about your purchase, and technical internet or network activity information, all described in Section 2. Sources, purposes, and recipient categories are described in Sections 2, 3, and 5. We do not sell personal information for money. Optional Meta advertising measurement may be considered sharing for cross-context behavioral advertising under California law; it requires your advertising choice and can be disabled through Privacy choices or Global Privacy Control. We do not knowingly sell or share minors' information.
10.3 European and UK visitors
Although this website is intended for U.S. adults, if the GDPR, UK GDPR, or another applicable law protects your information, you may exercise the rights it provides and lodge a complaint with your competent data-protection authority. If MVC is required to appoint an EU or UK representative, we will identify that representative and provide its contact details in this policy. Where applicable law requires safeguards for an international transfer, MVC must ensure that the required safeguards cover the transfer; contact us for information about safeguards applicable to your information. We send optional marketing email to EU or UK recipients only after obtaining any consent required by applicable law. You can unsubscribe through the link in the message or by contacting us; this does not affect necessary purchase, account, or support messages. Nothing in this policy waives mandatory rights based on your location.
10.4 Making a request
Email support@handoffacademy.com with the subject "Privacy Request", describe your request, and identify the address you used to correspond with us, if any. You do not need a Handoff account. Do not include a password, government ID, or payment-card number in an initial request.
We may request information reasonably necessary to verify identity or an agent's authority and avoid disclosing information to an unauthorized person. We will respond within the period required by applicable law and explain any permitted limitation or refusal. If you have an applicable right of appeal, reply to our decision with "Privacy Appeal" in the subject line. We will provide information about further recourse where required.
11. Children's privacy
The Services are intended for adults 18 and older. We do not knowingly collect personal information from people under 18 and do not knowingly collect personal information from children under 13 under COPPA. If you believe a minor has provided information to us, contact support@handoffacademy.com so we can investigate and take appropriate steps to delete it, subject to legal obligations.
12. International processing and external links
MVC operates in the United States. Our providers may process information in the United States and other places where they operate, whose privacy laws may differ from yours. Where applicable law requires safeguards for an international transfer, we must use the safeguards that law requires. This policy is not a waiver of those requirements.
When you follow an external link, the destination may receive ordinary request information and handle it under its own policy. We do not control independent third-party sites. Review their terms and privacy notices before providing information or enabling an integration.
13. Changes to this policy
We will post updates with a revised last-updated date. Changes apply prospectively. For material changes, we will provide any additional notice and obtain any consent required by law. We will update the relevant disclosures before introducing materially different data uses or additional account, AI, analytics or communication services beyond those described here.
A future update does not automatically authorize materially different uses of information already collected; any required notice, lawful basis, or consent must still be provided or obtained.
14. Contact
Miranda & Valdes Collective, LLC — operator of Handoff Academy
8621 SW 184th Ln, Cutler Bay, FL 33157, United States.
Email: support@handoffacademy.com. Use this address for privacy questions and requests.
Website: handoffacademy.com. See also our Terms of Service.