How Mockly handles your information

This Privacy Policy describes how Mockly (“Mockly,” “we,” “us”) collects, uses, shares, and retains information when you use usemockly.com, the Mockly application, and related email and support (the “Services”). It applies to candidates practicing interviews, people who create an account, and people who contact us.

It should be read with our Terms of Service. If you do not agree with this policy, do not use the Services. The product includes an AI interview coach presented as Wilber. References to coaching, scores, and sessions include that experience.

Account and profile

When you register or sign in, we collect:

• name, email address, and authentication identifiers;
• profile details you choose to add during onboarding, such as the kind of role you are preparing for;
• if you use Google or LinkedIn, the basic profile information that provider shares with us for sign-in, such as your name, email, and provider account id.

We do not receive your Google or LinkedIn password. Those providers authenticate you under their own policies.

Practice content

When you use interview practice, we collect the material you submit and the material the product creates from it:

• microphone audio from a voice session, and the transcript produced from that audio;
• the role, company, job description, and other setup details you enter;
• questions, follow-ups, scores, summaries, and coaching notes generated for that session;
• session metadata such as timing, feature used, and how much practice time was consumed.

Voice practice requires microphone access in your browser. Audio is captured so it can be transcribed and so Wilber can respond. You should not say government ID numbers, payment card numbers, or other people’s confidential information during a session.

Payments

If you buy practice time, Paystack processes the payment. We receive confirmation details such as your email, plan name, amount, currency, transaction reference, and whether the payment succeeded. We do not store your full card number or mobile-money PIN.

Device, usage, and support

• browser type, device type, general location inferred from IP address, and similar technical logs;
• pages and features you use, referring URLs, and diagnostic events that help us see what broke;
• messages, screenshots, and attachments you send to support, plus the email associated with the request.

We use information to:

• create and secure your account, including sign-in with email, Google, or LinkedIn;
• run practice sessions, transcribe speech, generate questions and feedback, and score answers;
• track practice-time balances, complete purchases, send receipts, and handle failed or reversed payments;
• remember preferences and keep a session signed in;
• detect abuse, fraud, and security incidents, and debug outages;
• understand which features are used, in aggregate and, where needed, at account level, so we can fix and improve the product;
• send service messages, such as verification, payment confirmation, and security notices;
• respond to support requests and enforce our Terms;
• comply with law and respond to valid legal process.

We do not use your interview audio to market third-party products, and we do not allow advertisers to target you based on the content of a practice session.

Where a privacy law requires a legal basis, we rely on the following:

• Contract. Processing needed to provide the account, session, score, or practice time you asked for.
• Legitimate interests. Securing the service, measuring product reliability, preventing abuse, and improving features, balanced against your rights. You can object where the law gives you that right.
• Consent. Where we ask for it, including optional communications or a browser permission such as microphone access. You can withdraw consent without affecting processing that already happened lawfully.
• Legal obligation. Keeping records we are required to keep, and responding to lawful requests.

A voice session sends audio to Deepgram so it can be recognized as speech and so the live practice conversation can continue. Questions, follow-ups, job-description parsing, and written feedback are produced with language models accessed through Groq and the model providers behind that service.

We send the portion of your content that the feature needs. A coaching turn receives the relevant transcript and session context, not your payment card details. Providers process that content to return a result to us. They are not permitted to use it to sell advertising.

Outputs can be wrong or incomplete. Scores and recommendations are coaching aids for you. They are not automated decisions that determine employment, credit, or legal rights. Hiring decisions remain with you and with employers, not with Mockly.

We use cookies, local storage, and similar technologies for:

• Sign-in and security. Keeping you authenticated and protecting the session. The product does not work properly without these.
• Preferences. Remembering choices such as interface state.
• Product analytics. PostHog helps us understand feature usage and errors. Vercel Analytics measures traffic to the site in aggregate. These tools receive technical and usage data, not the full contents of a practice answer as an advertising profile.

We do not use these tools to sell personal information. You can control cookies in your browser. Blocking strictly necessary cookies will sign you out or prevent sign-in. Browser controls and the preferences offered by analytics providers can limit measurement cookies.

We do not sell personal information. We share it only in these situations:

• Service providers. Companies that process data for us under instructions and contractual limits. The main ones are Supabase (accounts and database), Deepgram (voice), Groq and underlying model providers (coaching and document analysis), Paystack (payments), Vercel (hosting and site analytics), PostHog (product analytics), and our email delivery provider. Google and LinkedIn receive the sign-in request you start with them.
• Legal and safety. If we believe disclosure is required by law, regulation, or legal process, or is needed to protect the rights, safety, and security of Mockly, our users, or others.
• Business transfers. If we are involved in a merger, financing, or sale of assets, information may transfer with the business. We will notify you of a change in controller where the law requires it.
• With your direction. When you ask us to send information somewhere, or you connect a third-party account.

We do not share your audio or transcript with employers or recruiters. A practice session stays in your account unless you yourself export or repeat that content elsewhere.

Mockly is offered with pricing in Ghanaian cedis, and we describe governing law in the Terms. Our providers host and process data in the United States and other countries where they operate, which may not be the country where you live.

When information moves across borders, we use providers that offer contractual and technical protections appropriate to the service, such as access controls and encryption in transit. Those transfers are necessary to provide voice practice, model outputs, hosting, and payments.

We keep personal information for as long as your account is active and as needed for the purposes in this policy. In practice:

• account details last for the life of the account, then for a short wind-down period while deletion completes;
• session audio, transcripts, scores, and job details last until you delete them or delete the account, unless a longer period is required for security, disputes, or law;
• payment records are kept for as long as tax, accounting, and fraud-prevention rules require, even if you close the account;
• server logs and analytics events are kept for a limited operational period and then deleted or aggregated.

Backups and provider caches can retain fragments for a further limited time after you delete something. We isolate those copies from routine product use and let them expire on the backup cycle.

We use measures appropriate to the product, including encryption in transit, access controls on production systems, authentication for accounts, and separation between payment card data (handled by Paystack) and the rest of the application. Staff and provider access to personal data is limited to people who need it to operate the service.

No online service is perfectly secure. You can reduce risk by using a unique password, protecting the email account you use to sign in, and not practicing on a device you do not trust. If you believe your account has been compromised, email privacy.mockly@gmail.com.

Depending on where you live, you may have the right to:

• access the personal information we hold about you;
• correct inaccurate information;
• delete your account and associated practice content, subject to records we must keep;
• receive a copy of information you provided, where a portability right applies;
• object to or restrict certain processing, including processing based on legitimate interests;
• withdraw consent, including by revoking microphone permission in your browser;
• lodge a complaint with a data protection authority. We ask that you contact us first so we can try to resolve the issue.

To make a request, email privacy.mockly@gmail.com from the address on your account, or tell us enough to find that account. We may need to verify that the request is yours. We will respond within the time required by applicable law. If we deny a request, we will explain the reason and any appeal the law provides.

You can update some profile details inside the product. Signing out and revoking Mockly’s access in your Google or LinkedIn settings stops future sign-in through that provider; it does not by itself delete data already stored in Mockly.

We send transactional messages that are part of the service: account verification, security alerts, payment receipts, and replies to support. You cannot opt out of those while you keep an account, because they are how we deliver what you purchased or protect the account.

If we send optional product news, those messages will include a way to opt out. Opting out of news does not turn off receipts or security mail.

The Services are not for anyone under 16. We do not knowingly collect personal information from children under 16. If you believe a child has given us information, email privacy.mockly@gmail.com and we will delete the account and associated practice content.

We may update this policy when our practices, providers, or legal duties change. The new version will be posted on this page with a new “Last updated” date. If a change is material, we will also give notice in the product or by email before it takes effect, unless a shorter timeline is required for security or law.

Continued use after the update takes effect means you accept the revised policy. This version was last updated on October 4, 2026.

Privacy questions and requests go to privacy.mockly@gmail.com. Include “Privacy” in the subject line and the email on your Mockly account.

This policy describes our practices in plain language. It is not legal advice, and it does not expand your rights or our duties beyond what applies to the Services.