Privacy Policy

1. What we collect

A. Your account

• Email address, name (if you give it), and password. We store your password only as a salted hash (PBKDF2-SHA256), never in a form anyone can read. Your account is a MingLLM account kept in a system shared with other MingLLM products (such as Loom), so the same email and password work there too.
• Confirming your email. When you make an account with a password, we email you a one-time 6-digit code and you type it once, to show the address is yours. Forgot password works the same way. We keep each code only as a keyed hash, for 10 minutes, and it works once.
• Signing in with Google, Apple or GitHub (optional). If you choose "Continue with Google", "Continue with Apple" or "Continue with GitHub", that company tells us your email address (with Apple, it may be a private relay address that forwards to you), your name if you share it, and an id for your account there, and we keep these with your account. We never get your password for that account, and we ask for nothing else from it.
• Your age group. When you sign up, we ask your birthday and keep only your age group (under 13, 13 to 17, or 18 and over), never the birthday. If you're 13 to 17, we also record that you told us a parent or guardian said it's OK.
• What you agreed to. Which versions of our documents you accepted and when, and, if you start a paid plan, the renewal terms you were shown.
• Devices you sign in from. To warn you about sign-ins from new devices (and to tell when an invite link is used in a browser its owner signed in from), the sign-in page sets a cookie (dh_device) and we keep scrambled marks (hashes) of that cookie and of your browser family plus the first part of your network address. We don't keep your full IP address for this. The sign-in page also remembers, in your browser only, that you're signed in there and which account you used last, so it can offer "Continue as" (see the Cookie Policy).

B. Your voice and conversations

• Your voice. While the pill is open and listening, audio from your microphone streams directly from your device to our AI service provider (from the app, over an encrypted WebRTC connection), which runs the live voice conversation. Our servers set up the connection but never receive or record your audio.
• Transcripts. When a session ends, the app sends us a written transcript of what you and Ducky said (up to the last 400 lines), the topics, and what Ducky put on the board. We use an AI model to write a one or two sentence summary for your dashboard.
• What you type to Ducky. When you type to Ducky instead of talking, your messages, with pictures of what you share when Ducky looks, go through our servers to our AI service provider so Ducky can answer. We don't keep the messages themselves; what Ducky saves from them (such as flashcards or a memory) is kept like the rest of your learning record.
• Code you run (older versions of the app). The Mac app no longer runs code, but some older versions do: when you or Ducky run code in a lesson there, the app runs it on your Mac. Running code doesn't make us keep a copy of it or of what it prints, apart from what is part of a session's transcript or board.
• Pronunciation practice. If you use the pronunciation card, a short recording of your try (about 30 seconds at most) goes through our servers to our AI service provider to be transcribed and scored. We don't keep it.
• Web searches. When Ducky looks something up to answer you, our AI service provider's web search runs the search for us.

C. Your screen

In the Mac app:

• Screenshots. When you start talking, when you point at something with fn + cmd, or when Ducky needs to look, the app takes a picture of your screen and sends it to the AI through the live session. DuckyHelper's own windows are left out. The app may first read the text in it on your Mac, using Apple's built-in text recognition, so Ducky can point at the right spot.
• Only when it looks. Ducky sees your screen in those pictures only: it doesn't watch your screen in between, except what a task works on while that task runs, and an app you set an automation to watch (section 1D). Some older versions of the app (before 0.10.17) could also watch it during a session, sending a picture when it changed (at most one every 2 seconds) through our servers to our AI service provider for a short description for Ducky's voice, and hold a picture of it on your Mac for up to 30 minutes. We didn't store those pictures or descriptions, and the watching paused while a password field had focus.
• Your camera. macOS asks before the app can use your camera, if you turn on a feature that uses it.
• Screens it remembers. The Mac app keeps the screenshots of the screens Ducky saw while you talked, on your Mac in DuckyHelper's folder there, with the words read on them, the app and window that were in front, when, and the short description of it Ducky's voice was already given, so Ducky can find one again and show it to you on its blackboard ("the worksheet from yesterday"). Each is kept 7 days after Ducky last saw it, one you ask it to remember 30 days, and at most 300 of them. We don't keep them: they leave your Mac only when Ducky looks for or brings back one while you talk, and then what is kept with the matching ones (the app and window, when, a label, the description) and the picture it brings back go to our AI service provider in that conversation, like any screenshot. It doesn't keep a screen while a password field has focus. Each account on a Mac keeps its own and is never shown another's, and a child's account (under 13) keeps none until their parent turns on Pictures and files in memory. Turn it off, or forget them all at once, in Settings, Memory: Remember my screens. Deleting your account in the Mac app deletes that account's, and uninstalling the app deletes them all.

In the Windows and Linux app:

• Screen help, only if you turn it on. The app sees nothing on your screen until you turn on screen help (in its Settings, Permissions, or its tray menu) and allow it. Then, only while a conversation is open, it takes a picture of the display you're on when you start the conversation, when you point at something with Ctrl+Shift+P, or when Ducky needs to look, and sends it to the AI through the live session. It takes none while the conversation is closed. DuckyHelper's floating windows (the pill and its drawings) are hidden for a moment while the picture is taken; its dashboard can be in it if it's open on that display. The app may first read the text in it on your computer, with a text-recognition engine built into the app, so Ducky can point at the right spot. It doesn't save the picture, or keep the screens Ducky saw.
• Your microphone and camera. The app asks before it uses your microphone (the first time you talk) or your camera (if you use a feature that shows it to Ducky). Its Settings, Permissions turns the microphone off again (it then asks at your next talk). On Windows, Windows' privacy settings must allow them too.

Anything on your screen can end up in a screenshot, including other apps, messages and notifications. Close anything private before you ask Ducky to look. The AI that describes your screen is told to leave out passwords, codes and personal details, but that is an instruction, not a guarantee.

D. What you do on screen

The app doesn't follow your clicks or typing. Ducky points and draws on your screen to show you, and its drawings change nothing in your apps.

In the Mac app, where it's available on your account (early access), Ducky can also do a task you ask for: it clicks, types, presses keys, scrolls and drags in your apps, and opens apps and web pages the task needs. It's built to ask you first before it sends a message or pays for anything, but it may not recognize every send or payment, so keep an eye on tasks that involve messages or money. If you set up an automation to send messages by itself, it gives you a short time to undo each one. It's built not to type your passwords or card numbers. While a task runs, the app takes pictures of the windows the task works in, a few each second, and reads the words in them through macOS Accessibility. When a task drives your screen or works across your whole Mac (a task can switch to this by itself when it can't do the work in the background), the pictures are of your whole display, leaving out DuckyHelper's own windows, and the app also reads the names of your open windows. The pictures Ducky looks at and those words go through our servers to our AI service provider so Ducky can decide what to do next; we don't keep them. The app also keeps a recording and a log of the task's steps on your Mac, for your most recent tasks, and deletes older ones; they aren't sent to us. An automation you set up to watch an app reads that app's window from time to time, and what changed goes through our servers to our AI service provider. If you save a login in the Work tab, the password stays in your Mac's Keychain and the app fills it in for you itself: it isn't sent to us or to our AI service provider.

Some older versions of the app (before 0.10.17) could also, with the Accessibility permission, follow your clicks, which text field was active and what you typed in it (at most about 2,000 characters around your cursor, never in a password field) so Ducky could tell when you'd finished a step, used during the session and not kept as a separate record; and they could click, type, press keys, scroll and drag on your screen when you asked or to show you how, each action in the session's transcript, never in a password field and never to submit, pay, send or delete anything in your place.

E. Your learning record

• Progress by topic and skill, tests you take with your answers and grades, flashcards and their review history.
• Mistake patterns: a kind of mistake Ducky noticed (for example, "sign error when dividing by a negative"), an example, and daily counts for the last 60 days.
• Your profile, if you fill it in or tell Ducky: name, age, grade or school level, subjects, goals, interests, learning style, language, pace and accessibility needs.
• Memories: short notes Ducky saves to help you next time (up to 200), and pictures and files you or Ducky keep (up to 300). For each picture we keep the image, a small preview and a short AI-written caption; for each file (PDFs, Word documents, text) we keep the file, up to 12,000 characters of its text and a one-line summary. Ducky won't save a note that looks like an email address, password, phone number, home address, or ID or card number, and won't save a picture its describer flags as showing private details. You can switch off "Use memory" and "Let Ducky save memories" in Settings.
• Reports for a parent or teacher, and your report settings (who it's for, their name and email, how often).
• Pictures Ducky makes for you, with the request and caption they were made from.

F. Google

DuckyHelper doesn't connect to your Google Calendar, Gmail or Google Docs. Ducky sees them only when they're on your screen as it looks (section 1C). If you sign in with Google, Google tells us only what section 1A says.

Google API data. DuckyHelper's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google data only to provide the features you turned on, we don't use it for ads, we don't sell it, we don't use it to train AI models, and no person at MingLLM reads it unless you ask us to (for support), it's needed for security, or the law requires it.

G. Payments

Payments are handled by Stripe. We never see or store your full card number. We keep your plan, your Stripe customer and subscription ids, your credit balance and when credits expire, your card's brand, last 4 digits and expiry (to show which card is on file), your auto top-up setting, recent usage by kind (35 days), and a record of each payment and refund.

The 10 minutes to try. If your new account uses its 10 minutes to try (see the Billing terms), we keep with your plan when they started and how much of them you've used. So they're given once per person, we also keep a scrambled mark (a hash) of your email address, with any "+" tag (and the dots some email services ignore) taken off, which stays after your account is deleted; we check the dh_device marks of the devices you signed in from (section 1A) and keep, for 400 days, which account each of those devices' 10 minutes went to; and to limit how many start from one network in a day, we count them under a scrambled hash of the network address that changes daily and is deleted after 2 days. We never keep your IP address for this. Children's accounts don't get the 10 minutes, and we keep none of this about them.

Promotion codes. If you use a promotion code (see the Billing terms), we keep with your plan which code you used, when, and the end of the period it was for, so the reminder before your renewal can say the promotional price is ending. So a code is used once per person, we also keep a scrambled mark (a hash) of your email address, with any "+" tag (and the dots some email services ignore) taken off, and Stripe's fingerprint of the card you paid with (we never see card numbers), each naming the account that used it, as payment records.

H. Emails

We send email from donotreply@mingllm.com through Amazon SES. We keep your email settings (which kinds you get, your timezone, your report recipient) and a log of each email we sent you (kind, status, delivery events) for 400 days. If an address bounces or marks us as spam, we keep it on a do-not-email list for good. Our emails don't use open or click tracking. Some emails load fonts from Google Fonts, which your email app fetches from Google.

I. The website

duckyhelper.com shows a cookie banner. Nothing beyond what's strictly necessary runs until you choose, and we honour Global Privacy Control signals. The Cookie Policy lists every cookie and what it does. In short:

• Necessary: your cookie choice (dh_consent, 182 days), the sign-in hand-off, the code of an invite link you followed (dh_ref, kept in that browser tab only and passed to the sign-up), and the code of a creator's or campaign's link you followed (dh_via, from ?via= in the address: the first one and when you followed it, kept in your browser for 30 days and passed to the sign-up, nothing else with it).
• Analytics (only if you say yes): a random visitor id (dh_vid, 13 months) and, sent to our own servers (no third party): pages viewed (without query strings), outside referrers, campaign tags, how far you read, clicks on the main buttons (and the download starting by itself on the download page), your coarse country, device type, browser and OS family, and, if you sign in on the site, the account it belongs to. Where your visit started (the first page, campaign tags and the outside site, dh_touch) is also kept in that browser tab and passed to the sign-up, so a new account can keep it (section 1K). We never store your IP address: only a scrambled hash with a random value that changes daily and is deleted after 2 days. Analytics records are kept 13 months; daily totals with no ids are kept. Turning Analytics off deletes the cookie and what we kept about that visitor id.
• Downloading the app: when you press Download for a Mac, Windows or Linux, the site sends our servers the campaign tags in the address of the page you pressed it on (utm_ parameters; nothing is stored in your browser for them) and the invite and via codes it would pass to a sign-up (and when you first followed the via link), nothing else. We keep them under a scrambled hash of your network address (with a random value that changes daily and is deleted after 2 days), so that an account made from the app on the same network within a day can keep where it came from (section 1K). The first such account takes it; otherwise it's deleted within 2 days. We never store your IP address, and nothing is sent when there's nothing to keep.
• Email sign-up: if you sign up for study tips and news, we keep your address, where you signed up, campaign tags, and a record of each consent step. Nothing is sent until you confirm by clicking the link we email you. Unconfirmed sign-ups are deleted after 30 days. You must be 13 or older to sign up; we keep nothing from someone who says they're under 13.
• The link by email: if you ask the download page to email you the link to DuckyHelper for your computer, we send that one email and keep only a scrambled record of it (and a count of these emails by the link that brought you, with no address). If you also ask us to send it again tonight, we keep your address until that one reminder goes out at 7 pm your time, then delete it. You must be 13 or older; we keep nothing from someone who says they're under 13.
• Waitlist: if you join the waitlist for DuckyHelper on another device (such as an iPhone), we keep your address, that device, when and on which page you joined, and the campaign tags of the link that brought you there (such as which video or post it was), so we can email you once when DuckyHelper comes to it and know which links bring people. We email you once to say you're on the list, with a link that takes you off it. We delete your place after 2 years, or sooner when you use that link or ask us. You must be 13 or older to join; we keep nothing from someone who says they're under 13.

J. Technical information

Our servers keep logs (requests, errors, timings) for 30 days. They may include your account id and network address. The Mac app keeps a log file on your Mac.

Setup steps. So we can see where people get stuck setting up, the apps tell us once each when they're first opened, reach the sign-in step, make or first sign in to an account, finish the setup and first talk with Ducky and get an answer, with only that step, which app (Mac, Windows or Linux), its version and the day: no account, email address, device or install id, so it says nothing about you or anyone (nothing about a child is collected), and we keep it only as daily counts, for 13 months; to stop misuse they're counted against a scrambled hash of the network address that changes daily and is deleted within 2 days.

K. How you found DuckyHelper, and invites

• Where your sign-up came from. When you make an account, we keep, once: the campaign tags of the link that brought you (utm_source, utm_medium, utm_campaign and utm_content), the outside website you came from (its name only, such as tiktok.com, never the page), the first page of your visit (its path only), the invite code if you came through a friend's invite, the code of a creator's or campaign's link (via) and when you first followed it, and when. They reach the sign-up with the link: duckyhelper.com adds them to its link to the sign-up only if you said yes to Analytics in its cookie banner (the invite and via codes always, because they're what you came for: the invite's minutes, or the creator who sent you; see the Cookie Policy), and app.duckyhelper.com reads them from the link it was opened with and the website that sent you there. An account whose sign-up no link reaches (such as one made from the app after downloading it) takes the campaign tags and the invite and via codes from a Download press on duckyhelper.com from the same network within the day before (section 1I), and we note that it came that way. No cookie carries them, and no other company receives them. If your browser sends Global Privacy Control, we keep only the invite and via codes.
• Where you made your account. Whether you signed up in one of the apps (the Mac app, or the Windows and Linux app, whose sign-in page opens in your browser) or on a website, and on which kind of computer (such as a Mac, Windows or Linux, or a phone; from the description your browser or the app sends with the sign-up), so our emails can offer the right download. It's kept with your email settings.
• "How did you hear about us?" Once, in the Mac app's setup, we may ask how you heard about DuckyHelper, with a list of answers (such as TikTok, a friend or a teacher) and Skip. Answering is optional. We keep your answer, or that you skipped (so we don't ask again), and when.
• Invites. If you share your invite link, we keep your invite code, how many friends joined, started talking and joined a plan through it, how many friends' minutes it gave today and this month, and the rewards you got or that were taken back. If you joined through a friend's invite, we keep whose invite it was, whether you got the invite's minutes (or why not), and, once you first pay for a plan, which plan, when, and what happened to your inviter's reward. To stop misuse, we check that your sign-up didn't come from a browser your inviter signed in from (the dh_device cookie) and, before a reward, whether the same card is saved on both accounts (by Stripe's card fingerprint; we never see card numbers). Rewards are account credit at Stripe: Stripe receives the amount and both account ids, and if the inviter has no Stripe customer yet, we create one with their email address. Your inviter sees only numbers (how many friends joined, started talking and joined a plan, and what they earned) and, when a reward is added, which plan the friend chose; we never show them your name or email address.
• What we use them for: to see, in totals, which websites, posts, campaigns and answers bring learners, where they make their accounts, and how many of them start using DuckyHelper; to send the right welcome emails; and to run invites and stop their misuse. Never for ads.
• Not for children. None of this applies to children under 13. The sign-up form never makes a child's account (a parent does, and that account has none of these records), and a child's account is never asked how they heard about us and can't use invites. If an account says it's under 13 after it was made, we delete where its sign-up came from, its answer and its invite records, and any unused minutes from an invite, when we ask a parent for consent (account credit already given stays in the payment records, and whether the account was made in an app or on a website stays with its email settings).

2. What stays on your device

On app.duckyhelper.com, your sign-in is kept in your browser's storage. In the Mac app:

• In some older versions of the app (before 0.10.17), the tiny thumbnails used to notice screen changes, and the 30-minute screen memory.
• The screens it remembers (section 1C), until their days are up, you forget them, or you uninstall the app.
• Code you or Ducky run in a lesson, in an older version of the app that runs code.
• Your sign-in token and app settings.
• DuckyHelper's windows talk to a small web server the app runs on your Mac, which only accepts connections from your own Mac.
• When Ducky shows a knowledge panel, the app fetches pictures and summaries straight from Wikipedia's public API, so Wikipedia sees your network address, as with any website you visit.

In the Windows and Linux app:

• Your sign-in and the app's settings (such as whether screen help, the microphone and the camera are allowed), in its folder on your computer.
• DuckyHelper's windows talk to a small web server the app runs on your computer, which only accepts connections from your own computer. Signing in goes through your web browser and comes back to it.
• The text it reads in screenshots, read on your computer; the screenshots aren't saved there.
• Knowledge panels come straight from Wikipedia, as in the Mac app.

3. How we use information

• To run the tutor: the voice conversation, seeing your screen, pointing, drawing and acting on it, tutorials, quizzes, graphs, flashcards, pictures and reports.
• To pick up where you left off: when a session starts, Ducky gets a short brief about you (your profile, memories, mistake patterns, the summaries of your last two sessions, the skills you're still working on, and cards due).
• To show your dashboard, your progress and the reports you ask for, and to email reports to the person you chose.
• To bill you and apply limits: plan limits, credits, fair use, receipts, renewal reminders.
• To send email you asked for or need (account, payments, reminders, recaps, the newsletter and offers if you didn't switch them off).
• To learn how people find DuckyHelper: where sign-ups came from and the answers to "how did you hear about us?", looked at in totals.
• To run invites: a friend's minutes, the inviter's account credit, and the checks that stop misuse.
• To keep the Services secure, prevent abuse, and find and fix problems.
• To meet legal obligations, such as keeping records of consent and payments.
• To improve DuckyHelper using aggregated usage numbers and site analytics you agreed to. We don't use your conversations, screenshots or learning record to train AI models.

4. AI providers and training

Our AI service provider, another company, processes your voice, what you type to Ducky, screenshots, transcripts, memory pictures and files and our prompts for us, through its API, as our service provider. Under its API terms, data sent to the API is not used to train its models unless the customer opts in, and we have not opted in. It may keep API data for up to 30 days to monitor for abuse, unless the law requires longer. See Subprocessors for the full list and links to their terms.

5. How we share information

We don't sell your personal information, we don't "share" it for cross-context behavioral advertising, and we don't show ads. We share it only:

• With our service providers that run parts of DuckyHelper for us, under contracts that limit how they can use it: Amazon Web Services (hosting, storage, email), our AI service provider (AI), and Stripe (payments). See Subprocessors.
• When you share, for example a report you send to a parent or teacher, or a session you share by link. A shared session's page shows what DuckyHelper drew and showed and, if you leave "Include the conversation" on, what you both said out loud, with emails, links, phone numbers, addresses and your name taken out. It never shows your screen, your voice or anything you typed. Anyone with the link can see the page until you stop sharing or it expires after 90 days. Accounts for children under 13 can't share sessions.
• With the friend who invited you, if you joined through their invite link: only numbers (how many of their friends joined, started talking or joined a plan) and, when their reward is added, which plan you chose. Never your name or email address.
• With a parent, for a child's account under 13 (see the Children's Privacy Notice).
• When the law requires it, or when we need to protect someone's safety, investigate fraud or abuse, or defend our rights.
• In a business transfer, such as a merger or sale, to the new owner, who must keep honouring this policy for information collected under it. We'll tell you before your information becomes subject to a different policy.

6. How long we keep it

We keep information only as long as we need it for the reasons above. Specifically:

Some of these have no automatic end date today (transcripts, progress, gallery entries for adults and teens). We're working on clearer limits; until then they last until you or we delete them.

7. Security

• The app, the website and our servers talk over encrypted HTTPS connections.
• Stored data is encrypted at rest with AWS. Files are never public; links to them expire after one hour.
• Passwords are stored only as salted hashes.
• Our AI provider keys stay on our servers and are never sent to your device.
• Every request is checked against your sign-in and can only reach your own information.
• The Mac app is signed and notarized by Apple, and its updates are signed so a tampered update is refused. The Windows and Linux app and its updates come from duckyhelper.com over HTTPS, and each update is checked against the checksum in our update feed before it installs (the Windows app isn't code-signed yet; see the App License).

No system is perfectly secure. If we learn of a breach affecting your information, we'll tell you and the authorities as the law requires. To report a security problem, see Security & Responsible Disclosure.

8. Your choices and rights

In the app you can:

• see and edit your profile, and turn "Use memory" and "Let Ducky save memories" on or off;
• delete single memories, pictures, files, mistake patterns, flashcards and reports, or clear all memory data at once;
• choose which emails you get, and unsubscribe from any non-essential email in one click;
• end a session at any time, and turn off permissions (in System Settings on a Mac; on Windows and Linux, screen help and the microphone in the app's Settings, and on Windows the microphone and camera in Windows' privacy settings too);
• in the Mac app, turn off Remember my screens, or forget every screen it kept (Settings, Memory).

By writing to privacy@duckyhelper.com from your account's email address, you can ask us to:

• give you a copy of your information (access and portability, in a common format),
• correct it,
• delete your session history, tests, progress, gallery, or your whole account and its data,
• stop any processing you can object to.

We'll confirm the request comes from you (usually by replying to your account's email) and answer within 30 days (45 days where the law allows, with notice). We won't treat you differently for using your rights. If we can't do something, we'll say why.

Website choices: "Your privacy choices" at the bottom of every page reopens the cookie choices. Global Privacy Control is honoured automatically.

9. California residents

This section is our notice under the California Consumer Privacy Act as amended by the CPRA, for California residents.

• Categories collected in the last 12 months: identifiers (email, name, account id, device marks, a random site visitor id); customer records (account and payment details through Stripe); commercial information (plans and purchases, invites and their rewards); internet or other electronic activity (site analytics with your consent, app usage, the link and website that brought you to sign up); audio information (your voice, processed live and not stored by us); visual information (screenshots; saved pictures); education-related information you choose to share (grades, subjects, tests and progress); inferences (learning profile, mistake patterns, memories); and sensitive personal information (your account log-in, and, for a child's account, a child's information).
• Sources: you, your device, your parent (for a child's account), and the company you sign in with, if you choose Google, Apple or GitHub.
• Purposes: the ones in section 3. We use sensitive personal information only to provide the Services you ask for and for other purposes the law permits, so the "Limit the Use of My Sensitive Personal Information" right doesn't apply.
• Disclosure: to the service providers in section 5, for business purposes. We don't sell or share personal information, and we have no actual knowledge of selling or sharing the information of consumers under 16.
• Retention: section 6.
• Your rights: to know what we collect, use and disclose; to access and get a copy; to delete; to correct; to opt out of sale or sharing (we do neither; we honour Global Privacy Control on the site); and not to be discriminated against for using them. You can use an authorized agent; we'll ask for proof of their authority and may verify your identity with you directly. Send requests to privacy@duckyhelper.com.

10. Children

DuckyHelper is for learners of all ages, and kids under 13 can use it only with a parent's verifiable consent. Our Children's Privacy Notice explains what we collect from children, how parents consent, how long we keep it, and parents' rights. If you think a child under 13 gave us information without a parent's consent, write to privacy@duckyhelper.com and we'll delete it.

11. People outside the United States

DuckyHelper is run from the United States, and our servers and providers store and process information in the United States. If you use it from elsewhere, your information is transferred to the United States, where privacy laws may differ from yours. Where the law requires it (for example, the EU or UK GDPR), we rely on our contract with you (to provide the Services), your consent (for site analytics and marketing email), our legitimate interests (security and improving the Services), and legal obligations, and you may also complain to your local data protection authority.

12. Changes to this policy

We'll update this policy when DuckyHelper changes what it collects or how it uses information, and before the change takes effect. Each version has a number and an effective date at the top, and every version is listed on the legal page. If a change is material, we'll tell you in the app or by email, and the app will ask you to accept it.

13. Contact

• Privacy questions and requests: privacy@duckyhelper.com
• Everything else: support@duckyhelper.com
• By mail (legal notices): MingLLM, Inc., c/o Legalinc Corporate Services Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, USA

MingLLM, Inc. is the controller of the personal information described here.