Privacy Policy

Last updated: November 17, 2026

PageDuo.ai is operated by PageDuo Inc. ("PageDuo", "we", "us"), the data controller for the personal data described in this policy — except where Section 1 notes that a published page's owner is the controller for what their forms collect. This Privacy Policy explains what we collect, where it lives, and your choices. Section 13 covers our PageDuo Truffle app.

1. What we collect

Account data: your email address, display name, optional country, and authentication credentials (password hash or OAuth identity). Workspace data: the HTML files, folders, media, comments, and form submissions you create or upload. Technical data: IP address, browser type, and — only with your consent (see Section 5) — usage events such as page views and feature usage, used to operate and improve the service. Our advertising tags and Cloudflare also collect some technical data when you visit our pages; Section 5 explains what and when.

Activity data (account-bound). When you are signed in and using the Service, you agree that PageDuo collects and stores all of your activity on the site bound to your account — including your usage, interactions, engagement, navigation within the app, the edits and AI generations you make, and the actions you take on your content and the feed. This first-party operational record is a term of using the Service (see the Terms & Conditions, "Your account"); we use it to operate, secure, analyze, and improve the Service and to rank and recommend the public feed. This is distinct from the product analytics in Section 5: those cover the specific analytics-cookie and anonymous-visitor tracking, which you can decline, whereas this account-bound activity record is the operational data the Service needs to function for your account.

If you provide a phone number (optional, asked during signup), we collect it for account recovery and authentication purposes only — plus, if you use the booking feature, to pre-fill your own notification settings. You can view, change, or delete it any time in Settings. We do not sell your phone number, and we share it only with the service that texts you a sign-in code (Section 6).

If you submit a form on someone else's published page, the values you enter and your browser's user-agent are transmitted to and stored by PageDuo on behalf of that page's owner, and your IP address is processed for spam and abuse prevention (only a hash is stored). The page owner is the data controller for what their forms collect; PageDuo stores it as their processor. The page owner is responsible for any additional privacy notice their jurisdiction requires.

If you try PageDuo as a guest, the content you create is stored under a temporary guest account. Guest accounts inactive for more than 90 days are deleted along with their content and storage.

Firewall log. The firewall in front of our servers, which also covers published pages and Truffle, keeps a security log of the requests it blocks, for up to a year: the IP address and country, the web address requested, the browser and other request headers, a technical fingerprint of the connection, and the time. It leaves out cookies and the sign-in tokens sent in request headers.

2. Where your content lives

Your files and media are stored in cloud object storage and a managed database operated on Amazon Web Services in the United States. Content is scoped to your workspace: only workspace members and people you explicitly share with can access it. Pages you publish are public at their published URL — publishing is always an explicit action.

3. AI processing

PageDuo is an AI-native editor. When you use an AI feature — generation, editing, beautify, media search, comment summaries, prompt suggestions, and the optional AI Auto-fix that repairs page errors automatically (on by default; disable it in Settings) — the relevant content is sent to our AI providers to produce the result: your prompt, the page or element being worked on, and any reference materials you attach. The UI discloses when attached materials will be sent to the AI.

We use these AI providers, and each one receives only what a request needs: Anthropic (Claude models) and OpenAI (GPT models) for chat, writing and building pages, documents, slides and sheets, images, embeddings for search and some voices; Google (Gemini models) for grading answers and translating templates; and ElevenLabs for narration, voices, sound and music in videos and for turning speech into text. Some requests may run on AI models we host ourselves (no third party receives those). If you bring your own API key (BYOK), your requests go to the provider whose key you supplied under that provider's terms.

In the PageDuo app for iPhone, iPad and Android, we ask your permission before the first time anything you write or attach is sent to these providers. You can withdraw it at any time in Settings → Privacy & safety; the AI features then ask again before they send anything.

We retain a per-account AI activity log — your chat history with the AI, meaning the prompt you typed and the response produced (both size-capped) — so you can review and re-run your past AI requests; it is deleted with your account. Files created through the AI Agent may include your original prompt as a hidden note inside the document for traceability; it travels with the file if you publish, share, or export it, and you can remove it by editing the file.

We do not sell your content, and we do not use your private content to train models. Our AI providers process your content to serve your request; Anthropic's and OpenAI's API terms do not permit using it to train their models.

4. Email

We send transactional email (verification, invitations, password reset, share notifications) via Amazon SES. Invitation emails contain single-use codes. We do not use third-party marketing trackers in email; links go directly to pageduo.ai (or the environment that sent them).

5. Cookies, analytics and advertising

Necessary cookies. We use strictly-necessary cookies to keep you signed in and to remember your cookie choice. They are always on. A browser that has used Truffle with a test account, or one of our team's, also carries a cookie saying only that, so its visits stay out of our counts.

Product analytics. Our own product analytics — usage events and an anonymous visitor identifier cookie — follow the same country rule as the advertising tags below. In the countries listed under "Where we ask first", and wherever we cannot tell where you are, they run only after you choose "Accept all" (in our apps, only after you turn them on in Settings → Cookies & analytics). Everywhere else they run from your first visit, and you can turn them off at any time with "Necessary only" under "Cookie choices" or in Settings → Cookies & analytics; they also stay off while your browser sends Global Privacy Control. Once you decline, none of it is recorded or sent, wherever you are. One narrow exception: if the app crashes, we send a crash report so we can fix it — while product analytics are off it is identifier-free (a one-time random id, no page address, no browser details); the fuller report ships only while they are on.

Usage counts. Separately, the app and our pages keep daily totals of how they are used — for example, how many writing suggestions were shown and how many were accepted, or how many times a section of the feed was opened. Each total holds only what was used, the kind of page it was on, and whether it came from a signed-in account, a guest account, our own team or a visitor. It holds no account, device, session or page identifier and none of your content, sets no cookie, and is kept whatever you choose about cookies.

Page counts. Separately, our server counts the pages it serves, for every visitor. For each page load it records the page address, your country, a coarse device and browser type, the referring site, whether you are signed in, and any campaign tags in the link (such as an ad click id). This count stores nothing on your device and is not linked to your account or to a visitor identifier.

Advertising tags. PageDuo's own pages (such as the home page, the feed, sign-up and the app) carry two advertising tags: the Meta Pixel and the Google Ads tag. We never add them to pages that you or other customers publish. They tell Meta and Google when someone who saw one of our ads visits, signs up, or runs a first AI generation, so we can see which ads work. They also let Meta and Google show our ads again to people who have visited PageDuo (remarketing). To do this, the tags can set cookies in your browser and send Meta and Google details of your visit: your IP address, your browser, the page you are on, and identifiers they use to recognise your browser or match it to an account you have with them. Meta and Google also use this data under their own privacy policies.

Where we ask first. In the EU and EEA, the UK, Switzerland, Brazil, India, Vietnam, China, South Korea, Saudi Arabia, Nigeria, South Africa, Canada, Bangladesh, Egypt, Indonesia, the Philippines, Thailand, Turkey, Kazakhstan, Malaysia, Kenya, Sri Lanka and the United Arab Emirates, the tags wait for your answer to the cookie banner. If we cannot tell where you are, we treat you the same way. Until you choose "Accept all", the Meta Pixel does not load at all. The Google tag does load, but in Google's Consent Mode with every signal set to "denied": it sets no cookies and strips ad-click identifiers, and it sends Google only cookieless signals (for example, that a page was viewed or an account was created), which Google uses to estimate ad results in aggregate. Like any web request, these signals show Google your IP address and browser type.

Everywhere else. In all other countries, including the United States, both tags run as soon as you arrive, and we do not show a blocking banner. You can turn them off at any time.

Turning the tags off. Choose "Cookie choices" at the bottom of our pages (in the United States it reads "Your privacy choices") to reopen the cookie banner, then choose "Necessary only". If you are signed in, you can also use Settings → Cookies & analytics. We record your choice in your browser. From the next page load, the Meta Pixel is not loaded in that browser and the Google tag runs only in the denied mode described above, until you change your choice. Because the choice lives in your browser, you need to make it in each browser and on each device you use, and again if you clear your cookies. We also honour Global Privacy Control: if your browser sends that signal and you are not in one of the countries listed above under "Where we ask first", we treat it as your request to opt out of sharing for advertising. The Meta Pixel does not load and the Google tag runs only in the denied mode described above, for as long as the signal is on, even if you chose "Accept all" earlier. The signal does not change the choice stored in your browser. Declining never limits core functionality.

US state privacy laws. We do not sell your personal data for money. But some US state privacy laws treat letting advertising companies such as Meta and Google collect data on a website, to measure and target ads, as "sharing" personal information or as "targeted advertising". Under those laws, our advertising tags may count as that. You have the right to opt out. You can do it with "Your privacy choices" at the bottom of our pages, or by turning on Global Privacy Control in your browser.

Cloudflare. Cloudflare delivers our site and protects it from attacks. It also runs Cloudflare Web Analytics on our pages: a cookieless script that counts page views and measures how fast pages load. It sets no cookies, and it runs whatever you choose in the cookie banner.

Published pages. Pages customers publish carry none of our advertising tags. They show their own consent banner and keep their own opt-in rule for analytics.

Feed ranking and recommendations. PageDuo's public feed ranks and recommends published pages. To do that we use information about published content only: the published page itself (it is public by your choice to publish), aggregate engagement statistics (view/play counts, copy counts, comment counts — counts, not who did them), and comments left on published pages (which are publicly visible on those pages). Product analytics events (Section 5) additionally feed this ranking, except for people who have declined them or, where we ask first, not accepted them. We may also use these same published-content signals to train and tune the ranking and recommendation models behind the feed. Private, unpublished workspace content is never used for feed ranking or for training those models, and unpublishing a page removes it from the feed. If you are signed in and told us about yourself when you signed up, we use that description — processed by our AI provider — to estimate which published pages match your interests and order your feed; it is used only to serve you, is never shown to other users, and you can change it by updating your profile.

6. Sharing and third parties

We share data with the service providers needed to run PageDuo. Each receives only what its job requires:

Published pages that display live data (for example weather, market prices, or encyclopedia extracts) may fetch it from public data services either through our servers or directly from the visitor's browser — in the direct case those services see the visitor's IP address, as with any website that embeds third-party content.

Payments. Card payments are processed by Stripe. When you buy a plan, you pay on a checkout page hosted by Stripe. Stripe collects your card details; we never see or store your full card number. We keep what we need to run your plan: your Stripe customer id, the plan, the billing period and the payment status. In Vietnam, plans may be sold by our local partner, Thang Long Academy, which invoices you and takes payment by bank transfer. A plan bought through a reseller is activated with a licence key. When you redeem a key, we record the key, who redeemed it, when, and the workspace it was applied to.

We do not sell your personal data for money. Some US state laws may treat our advertising tags as "sharing" personal information; Section 5 explains this and how to opt out.

7. Retention and deletion

Your content is retained while your account is active. Deleting your account removes your user record, your AI activity log, and the workspaces only you own — their folders, pages, versions, comments, audit logs, and stored files; the deletion cascades through our database and object storage. Your analytics data is an exception: it is retained for 180 days after you delete your account, then permanently removed — we keep it for that period for security, fraud-prevention, and aggregate product-statistics purposes, after which it is deleted. A workspace you share with other members is transferred to a remaining member instead of deleted, so their content stays available; content you contributed to OTHER people's workspaces (pages, versions, comments) stays with those workspaces and is disassociated from you. Deleted data may persist for a limited time in operational backups before those rotate out.

8. Your rights

You can download any folder as a ZIP and any file as plain HTML from the app, and export form submissions per page as CSV. You can correct your profile (including your phone number) in Settings, change your cookie choice at any time with "Cookie choices" ("Your privacy choices" in the United States) or in Settings (which also opts you out of the advertising tags, Section 5), and delete your account from Settings or by emailing support@pageduo.ai. Depending on your jurisdiction you may have additional rights (access, portability, erasure, objection, complaint to a supervisory authority) — contact us and we will honor them.

9. Children

PageDuo is not directed at children. You must be at least 13 years old (or the digital-consent age in your country) to create an account. If we learn we have collected personal data from a child below that age, we will delete it and close the account.

10. Security and incidents

Content is encrypted in transit; access is scoped by workspace membership and verified on every request. If a security incident affects your personal data, we will notify you and the relevant authorities as required by applicable law.

11. Changes

We will update this policy as the product evolves and change the "Last updated" date above. Material changes will be announced in-product.

12. Contact

Questions about privacy: support@pageduo.ai.

13. PageDuo Truffle

PageDuo Truffle ("Truffle") is our app for finding a file on your own devices or a teammate's computer and sending it. It runs on computers, on iPhone, iPad and Android, and in a browser at truffle.pageduo.ai. Truffle uses your PageDuo account, so the rest of this policy applies to it too. This section explains what is different.

Search runs on your devices. Truffle looks only in the folders you choose to share and, on iPhone, in its photo library if you allow it. The one exception is your own devices: once you link a second device of your own, such as your phone or another computer, each of your computers also indexes your whole home folder, so that you can search it, and that computer's Photos library, from your other devices. It skips system folders, app data and caches (such as ~/Library or AppData), passwords and keys, browser profiles, hidden folders and the bin; that index stays on the computer, only your own linked devices can search it (never a teammate), and you can turn this off on each computer in Settings with "My devices can search this computer". The search index (file names, the text inside files, and for pictures the labels and text your device's own system reads from them) is built and kept on that device, and is never uploaded. On a computer where "Understand your videos" is on (it is on by default on computers that can do it, and its switch sits beside your folders), the index also holds text that the computer makes from the speech in your videos and audio files (such as voice memos), and labels for the sounds in them. That text and those labels are made and kept on that computer and never leave it, and they are deleted when you remove the folder or turn the switch off. Truffle does not send your files, your index or your searches to any AI provider. When Truffle keeps settings or what it has learned in step across your own devices, those copies are end-to-end encrypted.

Your photo library. On iPhone, Truffle asks for access to your photos only when you tap to search them. What it reads from each photo stays on the phone, in protected storage, and is never sent. A photo leaves your phone only when you send it.

Files are end-to-end encrypted. A file, and the list of files a search found, is encrypted on the sending device for the receiving person's devices only. Our servers pass on sealed envelopes they cannot open: we never see a file's contents, its name, its type, or what a search found. We see the size of the encrypted data (rounded up to fixed steps), who sent it to whom, and when. An encrypted file waiting on our servers is deleted 24 hours after it is first downloaded, or after 7 days if nobody downloads it.

Device keys. Each device you sign in on makes its own encryption keys. The private key never leaves the device. We store each device's public keys, its name (for example "Safari on iPhone"), its type and when it was last seen, so that other devices can encrypt files for it.

What our servers can read. To deliver a request and tell people about it, our servers store these in readable form: the words of each request and its optional reason; who asked whom, and whether and when it was answered; and your teams, their names, members and invites. The names of the folders your computer lets each teammate ask about are end-to-end encrypted, like files: your computer encrypts each teammate's list for their devices only, so our servers cannot read the names or see who a folder is shared with. A request can no longer be answered after 7 days; once it is closed and past those 7 days we delete its words and reason, and keep only the record that it happened (who asked whom, and when) until the sender's account or the team is deleted. If you block someone, we keep a record of the block so their requests and files do not reach you.

Your account. You sign in with your email address and a one-time code we email you, with your phone number and a code we send to it, with Sign in with Apple, or with a passkey; in a browser you can also use Google. Phone numbers and Sign in with Apple are described below. A passkey is made and kept by your device or your password manager (such as the iCloud Keychain or Google Password Manager), which unlocks it with Face ID, a fingerprint or your device's passcode on the device itself: we never receive your face, your fingerprint or the passkey's private key. We keep the passkey's public key and id, a label such as "iPhone · Safari", whether it is synced across your devices, and when it was made and last used, until you remove the passkey or delete your account. People in your teams see your name and your profile photo if you add one, and some teams also show members' email addresses to each other. If you invite someone by email, we send them the invitation and keep only a hash of their address, not the address itself.

Sign in with Apple. If you choose Sign in with Apple, Apple sends us an identifier for your Apple account that is unique to us, your email address or, if you choose Hide My Email, a private relay address that forwards to you (we use it as your account's email), and, the first time only, the name you chose to share. Apple may leave the email out on later sign-ins, so we keep the identifier to recognise you. We also keep, encrypted, a token Apple gives us, used only to ask Apple to revoke Truffle's access when you delete your account. If you stop using your Apple ID with Truffle or delete it, Apple tells us, and that Apple ID no longer signs in to your account (you can still sign in with your email).

Your phone number and contacts. You can sign in to Truffle with your phone number. We send it a six-digit code, usually by text message, and keep the number on your account, with when you last proved it, so that you can sign in with it. The code is sent for us by Prelude or by Amazon Web Services (Section 6); they receive the number, and Prelude also receives the network address and browser of the request, to stop fraud. On a phone, "Find friends already on Truffle" reads your contacts only after you tap "Check my contacts" and allow it. Your phone turns each number in your contacts into a scrambled code and sends only those codes, never names or the numbers themselves. Our server compares them with the codes of people who chose to be findable, keeps none of them, and tells you only which of your contacts are on Truffle and the name each one uses. A scrambled code can be worked back to its number by trying every possible number, which is why we do not keep them. "Let people who have your number find you" is off unless you turn it on, and it needs a number you proved with a code. While it is on, people who have your number in their contacts can see that you are on Truffle and your name, nothing else, and we keep a scrambled code of your number to compare with; we delete it when you turn the switch off or delete your account. When you text an invite to someone in your contacts, your phone's own Messages app sends it, and the contacts you pick are not sent to us.

Links anyone can open. You can send a file as a link to someone who does not use Truffle. The file is encrypted on your device before it is uploaded, and the key is in the part of the link after "#", which browsers never send to any server, so we cannot open the files. We store the encrypted files, how many there are, their padded sizes, when the link was made and how much has been downloaded. A link expires after 7 days, and you can turn it off at any time; either way its files are deleted. The link page uses no trackers and nothing from other companies. Anyone can report a link: we keep the report's reason, and the reporter's IP address only as a short hash for one hour, to stop repeated reports.

Notifications. If you turn on notifications, we store the address that your browser's or phone's push service (Apple, Google or your browser maker) gives us. A notification carries only generic words and an id, never the words of a request, a file name, or a person's or computer's name.

Usage data. Our servers record a small set of events about how Truffle is used: for example that you signed up, connected a computer, sent or answered a request, accepted an invite, or said a file was the wrong one, and, once a day, that a device of yours was on. They hold only fixed categories and counts, never what was asked or sent, and they are kept as Section 7 describes. We also count visits to Truffle's web pages and clicks on its download buttons, keeping only the page, the kind of computer, the country the visit came from, the ad or website that led there, whether the download was available, whether it was the first from that address that day, whether it looks like a robot, a test run or our own team, and a scrambled key that lets us leave out our own team's visits, never the IP address. Truffle's apps and its browser app contain no advertising, analytics or crash-reporting software from other companies; the one exception is the advertising tag that truffle.pageduo.ai can load after you choose "Allow", described below. The computer app checks our servers for updates, sending its version, system and processor type and, on a test copy or a copy signed in to a test account or one of our team's, a label saying so. We count those checks by version, and also keep the update channel and whether it looks like a test run or our own team. These events and the daily counts below also note the country the request came from, and nothing more precise, never the IP address. Update checks and the app's first launch carry the same key. We also keep a short record with that key, naming no account, when one of our own accounts uses an address or when an address is busy in a day: six or more browsers or copies of the app, or two or more accounts that are not ours. Requests you make while signed in to Truffle count towards this, so such a record can show that your address was busy that day. The key changes every day. It is made with a random secret that we delete after three days; after that the key cannot be traced to any address. Separately, the firewall log described in Section 1 is not part of these records.

Ads that brought you to Truffle. If you arrive at truffle.pageduo.ai from an ad, the link carries the ad's click identifier (a code the ad's company, such as Google or Meta, adds to it), and we keep it with your account when you sign up. We then tell Google or Meta, from our servers, when an account that came from one of their ads reaches certain steps: the account was made, the computer app was opened for the first time, it finished its first look through your folders, the first search, the first request sent to someone, a return on a later day or in the second week, and an invite sent. Each report carries only the click identifier, the step, when it happened, a fixed value we give each step and a scrambled code made from your account's id; if you chose "Allow", it also carries a scrambled (SHA-256) code of your email address, which they can match to an account you have with them. The value for the first opening of the computer app is higher on a Mac with Apple silicon, so it tells them that kind of computer. It never carries your files, their names or what is in them, what you searched or asked, the names of your devices, your IP address, or anything from the iPhone, iPad or Android app. In the countries Section 5 lists where we ask first, and wherever we cannot tell where you are, nothing is reported unless you choose "Allow" on truffle.pageduo.ai. Everywhere else it is reported unless you choose "No thanks" under "Ad choices" at the bottom of truffle.pageduo.ai, or your browser sends Global Privacy Control. Our server keeps your choice in that browser, in a small cookie that a link cannot set, and it joins your account when you sign up or sign in there; Global Privacy Control counts as "No thanks" whenever your browser sends it as you sign up or sign in. Only if you choose "Allow" on truffle.pageduo.ai does that page also load the advertising tag of the one company whose ad you came from (the Google tag, the Meta Pixel, or Microsoft's, TikTok's, Reddit's, LinkedIn's, X's or Pinterest's tag); no other company's tag loads, and none loads if you did not come from an ad. It runs in a hidden frame on a separate pageduo.ai address that holds nothing else, never inside Truffle's apps or its browser app, and its cookies stay on that address: Truffle's pages and the PageDuo app cannot read them, and it cannot read theirs (the PageDuo app has its own Google Ads tag, described in Section 5, separate from this one). It tells that company that you saw the page and whether you downloaded the app, for which kind of computer, or started it in your browser. Each download or start carries a code that lets the company count it only once; the page view carries one only for Meta, Reddit and Pinterest, so for the other companies a reload can count as a second view. The tag gets the ad's click identifier and, if the link has them, the campaign's short source, medium and name, never the rest of the link, and it is never given your email address or anything else that identifies you. Each company uses what it receives under its own privacy policy. To stop these reports for your account at any time, write to support@pageduo.ai, or sign out, choose "No thanks" under "Ad choices" and sign in again in that browser. We keep a record of which steps were reported for your account and delete it with your account. The same applies, with the same choices, to ads on Microsoft Bing, TikTok, Reddit, LinkedIn, X and Pinterest: we keep their click identifier the same way and tell only the company whose ad you came from (Pinterest only after "Allow", because it needs the scrambled email). One of the steps reported is the first time, on the day you signed up or the next, that a search of your own files led you to open or use a result. In the iPhone app we ask Apple once, on its first start, whether an Apple Search Ads ad led to the download (Apple's AdServices), and in the Android app we read once the campaign tags Google Play kept from the store link; we keep that campaign with your account to count which ads work and to start the app on the matching first step, and we send it to no one. Neither uses an advertising identifier or follows you across other companies' apps.

Daily use counts. Once a day, the computer and phone apps, and Truffle in a browser, send counts of how they were used the day before. The computer app sends how many searches, how many ended with a file opened, played, sent or shared, how many questions were asked and how many got an answer, how the panel was opened, how many times the app crashed, and how far setup got (including whether its first look through your files has finished), with the app's version and processor type. The first time the computer app is opened, before anyone signs in, it also says once that it was installed, with its version, processor type, the kind of computer, whether it is a new install or an update, a label if it is a test copy or one of our team's, and a random number made for that copy of the app, which is never linked to your account. The phone apps and a browser send how many searches of your own files, how many ended with a file opened, saved or shared, how many requests were sent to other people, how many times something went wrong in the app, and how far setup got (signed in, notifications allowed and, on a phone, photos allowed). The phone apps also send how many photo and video searches were made on the phone and how many ended with one opened or shared, how many files were sent from the share sheet, how many times Truffle was opened from a widget and, on an iPhone, how many files and private links were added to a message from Truffle's Messages drawer, with the app's version and whether it is an iPhone or an Android phone. They never send what was searched, asked or found, or who anything went to. If a device was off or Truffle was not opened, the days it missed are sent the next time it runs, up to 7 days back. These counts are kept as Section 7 describes. You can turn this off in Settings, under This computer on a computer, This phone on a phone or This browser in a browser; turning it off also erases any counts not yet sent.

Optional sharing to improve search. What Truffle learns from how you use it on your own devices stays on them. Apart from the daily use counts above, two things leave your device only if you turn them on. "Help make search better for everyone" (off unless you turn it on) sends at most once a week a short report of 12 numbers, with random noise added on your device first; it contains no file, word or name, and we keep only a weekly total of all reports. Accounts in our pilot can also choose "Donate this search", which sends exactly what the sheet shows: the words you typed and, for each result, its position, kind, file extension and what you did with it, never a file name, folder or picture. A donation is kept with your account until you delete it or the account. To hold each account to the yearly limit on these reports, we also keep the days your account sent one, under a code that is not your account id.

Reports you send. If you report a problem or ask a question, we keep what you write and an email address to reply to, with where you sent it from (which app or page) and the facts the form lists: the app's version, your system, your computer's speed tier, the update channel and the names of recent errors. You can remove any of them before you send. A problem report from the computer app also carries the app's log, with file names, paths, what you asked, tokens and email addresses taken out. The form shows you every line of it before you send, and you can leave it out with one tap. If you choose, a report also carries a screenshot, which can show whatever was on the screen. Your files are never part of a report. We use reports only to answer you and fix problems, and you can ask us to delete one at support@pageduo.ai. The IP address is not kept with a report; to stop abuse we keep a short hash of it for up to a day.

When you sign out of a computer. What Truffle has learned on a computer from how you use it (which files you chose, what you sent and to whom, the names you taught it, the words you searched for) stays on that computer for your account, encrypted with a key kept in the computer's secure key store. If the computer has no secure key store, or you refused it, the key is kept in a file that only your user account on that computer can read, which protects it less. When you sign out it stays there, locked: Truffle does not read it or add to it, and another account signing in on that computer does not get it. Signing back in with the same account unlocks it. It is erased if you choose "Also erase what it learned on this computer" when you sign out, or "Forget what Truffle has learned" in Settings; if you delete your account from that computer; if you remove that computer from another of your devices (when it next connects); or if it goes unused on that computer for 90 days. If you delete your account somewhere else, it stays locked on that computer until those 90 days pass. Truffle does this erasing itself, so it happens when Truffle is running on that computer; if you uninstall Truffle, it stays there, locked, until you delete Truffle's folder on that computer. On a phone, it works the same way: it stays on that phone for your account, encrypted with a key kept in the phone's own secure key store (the iPhone Keychain or the Android Keystore), and it is erased if you choose "Also erase what it learned on this phone" when you sign out, or "Forget what Truffle has learned"; if you delete your account from that phone; if you remove that phone from another of your devices; or if it goes unused there for 90 days while you use Truffle on that phone. Deleting the app deletes it. In a browser, it stays in that browser for your account, together with which folders you shared there, and comes back only when the same account signs in there again; the browser's search index and its device key are erased when you sign out, so those folders are read again. The key is kept in that same browser, so this keeps other accounts out but not someone who uses that browser: on a browser other people use, choose "Also erase what it learned in this browser" when you sign out. It is also erased by "Forget what Truffle has learned", by deleting your account in that browser, by removing that browser from another of your devices, after 90 days unused, or by clearing the site's data in that browser. The search index is different: it is not encrypted, it stays on the computer when you sign out, and whoever signs in next on that computer searches the same folders. To remove a folder from it, stop sharing that folder.

Faces in your photos (People). On a Mac where it is offered, People is off until you agree on that Mac. If you agree, Truffle makes a face template, a mathematical faceprint, of each face it can measure in the photos and videos it reads there, and groups the ones that look alike so you can find people by the names you give them. Templates, groups and names are made and kept only on that Mac, encrypted with a key in its own keychain. We never receive them; they are never sold, shared, used for advertising or used to train any model, and they are never copied to your other devices or to backups. Only your own searches on that Mac use them: nobody else can, not your teammates and not your other devices. Truffle never guesses age, gender or ethnicity from a face. Templates are deleted when you tap Erase all, when you sign out, when the photo is gone, when you forget that person, or when the person hasn't come up for 12 months; a face never grouped with another is deleted within 180 days. If you delete the app without tapping Erase all first, the encrypted data stays until you reinstall Truffle or delete the folder ~/Library/Application Support/PageDuo Teammate/people. Your photos may include people who have not agreed to this, and you choose whether to turn it on. We receive nothing about People.

Deleting your Truffle data. In Truffle, open Settings, choose Delete my account and type your email to confirm, or follow these steps. Because Truffle and PageDuo share one account, this deletes your PageDuo account too. It deletes your devices and their keys, the requests you sent, encrypted files and links waiting on our servers, and anything you donated, as Section 7 describes. Files on your own computers are not touched. If you are the only owner of a team that has other members, make someone else the owner first.

Age. Truffle is a tool for work and is not directed at children. The age limit in Section 9 applies to it.