PLARO Privacy Policy

• Account information: name, email, password hash, language, nationality, timezone, email verification status, social-login identifiers, profile information, and the sign-up consent record (when the Terms were accepted and which version, when adulthood was confirmed, and for sign-ups from Canada the contract language chosen).
• Service content: projects and their meeting schedules, organization information, file metadata, uploaded files, support inquiries, and sharing or collaboration data.
• Recording and transcription data: audio files, meeting-session information, participants and speech segments, transcripts, translations, titles, and timestamps.
• Your clients' information: the names and email addresses of client contacts you enter to send requirements and acceptance confirmations, extra-work quotes and meeting invitations, and the clients' answers (Section 5).
• Billing information: plan, subscription status, order and subscription identifiers, amount, currency, payment and refund timestamps, and billing metadata. PLARO does not directly store full card numbers.
• Billing profile: when requesting a receipt or payment record, you may enter a legal name, country, business or tax identifier, billing email, and address (optional). A buyer who appears to live in Canada (who chose a contract language at sign-up, or whose payment, connection or billing country is Canada) must enter where they live (country, province, street, city, postal code) before their first payment, because the contract copy has to show the consumer’s address (sections 54.6 and 214.2 of Québec’s Consumer Protection Act); that address appears in the payment confirmation e-mail (the contract copy). The billing profile is stored encrypted. Identifiers are checked only for format and are not verified as a business by any government or tax authority.
• Security and operations data: IP-based access data, browser and OS, cookie and local-storage identifiers, push subscription data, usage logs, error logs, risk scores, hashed anti-abuse signals, and access records of signed-in use (the screen opened or action taken, the project, meeting or recording numbers it concerned, date and time, IP address).
• Google Calendar connection data: if you connect Google Calendar, we process the connected Google account email, access tokens, and the identifiers and links of the meetings PLARO adds (Section 7).
• Developer AI connection data: the developer’s email address and name you enter (the name is optional; both stored encrypted) with a non-reversible value (HMAC-SHA-256) used to look the address up, the name of the connected tool, the requirement versions it received, the developer’s sign-in (the code mailed to them — as a hash only, for 10 minutes; sign-in tokens — as hashes only, for at most 30 days from signing in), and an access record of each sign-in step and call (connection, date and time, IP address, the function called, the result). We never receive what the developer types or their conversation with the tool.
• Collection methods: information you enter or upload when you sign up and use the service; the name, email, and account identifier passed on by your social login provider (Google or Microsoft); and access and usage records generated automatically while you use the service.
• Required information: your name and email address are needed to create an account and provide the service, so you cannot sign up without them. Everything else is optional; leaving it out only turns off the related feature.

• Contract performance (Article 15(1)(4) of Korea’s Personal Information Protection Act; no consent needed): user identification, login, service features, synchronization, collaboration permissions, subscription, billing, refunds (including the contract copy sent to consumers in Canada), and support — account information, service content and billing information (including the billing profile).
• Processing on your instructions: sending requirements and acceptance confirmation requests (with any extra-work quote), answer copies, meeting invitations and their cancellation notices to client contacts, keeping their records so they cannot be altered, and letting you make quotes, change agreements and acceptance records (Section 5).
• Features you start (contract performance, Article 15(1)(4) of the same Act): recording, transcription, speaker separation and translation; AI summaries, drafts and checks; social login; the Google Calendar connection; and the developer AI connection — the related information in Section 2 is processed when you use the feature. We ask for separate consent only for web push notifications (your browser’s permission) and for recording meeting guests.
• Legitimate interests and legal obligations (Article 15(1)(6) and (2) of the same Act; no consent needed): security monitoring, error analysis, abuse prevention, service improvement (using only usage and error logs, never your content), accounting, tax, dispute handling, and legal requests — security and operations data, billing information and records kept by law.
• Region check (legitimate interests and legal obligations): we look up the country of your IP address so that sign-up and payment are accepted only in our service countries and access is blocked in regions the AI services PLARO relies on do not support. The lookup uses a database on our own server (DB-IP); your IP address is not sent anywhere else, and the result is not stored.
• Users in Canada: in Québec, providing your information for the purposes stated in this Policy is consent to those purposes (section 8.3 of Québec’s private-sector privacy Act); any other use without consent happens only where that Act allows it, such as fraud prevention or security (section 12). Elsewhere in Canada, the uses listed above under legitimate interests rest on implied consent within what you can reasonably expect, and we use information without consent only where Canadian law allows it.
• Automated decisions: refusing sign-up or payment based on the country of your IP address, and blocking sign-up or free benefits based on automated sign-up and abuse signals, are decided without a person. When this happens we tell you on screen or by email. On request we explain the information used, the main reasons and the principal factors and parameters, let you correct that information and submit your observations, and have the privacy officer review the decision. The region check finds only your country; it does not locate you more precisely or build a profile. AI feature results are not used to make decisions about you.

• PLARO does not provide your personal information to third parties, except for paid checkout (below) and to the extent that you yourself share, invite or connect an external service (for example Google Calendar, or a developer’s AI tool connected through the developer AI connection), or that a law specifically provides for it. Material you have stored is provided without your consent only under a court order to produce it or a warrant issued by a judge (Article 27 of Korea’s Cloud Computing Act).
• Payments (provision to a third party): paid plans are sold by Creem (Armitage Labs OÜ, Estonia, support@creem.io) in its own name as merchant of record. You enter card and other payment details directly in Creem’s checkout. When you start a checkout, PLARO sends Creem your account email, your user, checkout-request and payment-consent record numbers, and the plan and billing period (for a team, the team name and number of seats); Creem uses them for the sale, payment, receipts, tax, refunds and fraud prevention. The basis is Article 17(4) of Korea’s Personal Information Protection Act (provision reasonably related to the original purpose). PLARO decides by these criteria, which our privacy officer checks: the purchase is one you asked for (related purpose); the checkout screen and the Billing and Refund Policy name Creem as the seller before you pay (foreseeable); only what the purchase needs is sent (no undue harm); and it is sent only over encrypted connections (HTTPS, TLS) (security). The transfer to Estonia relies on Korea’s decision recognising the EU and EEA as equivalent (Article 28-8(1)(5), since 16 September 2025). Creem keeps contract data for 3.5 years after the contract ends and accounting records for 7 years (Creem’s privacy notice). Nothing is sent if you do not check out, but paid plans are then unavailable.
• Developer AI connection: if you enter a developer’s email address, PLARO mails that address the setup steps and the sign-in codes and, on your instruction, gives the tool signed in with such a code (the AI coding tool the developer chooses, for example Claude Code or Codex) only that project’s requirements, change history and open questions. Meeting and chat transcripts, amounts, and client names and contacts are not sent, although a name you write into a requirement’s text goes with it. The developer, the tool and its AI company (usually in the United States) are not processors PLARO has entrusted, and if they are outside Korea the information leaves Korea. What happens next follows that company’s terms and the developer’s account settings (such as whether data may be used for AI training). If you write other people’s information into requirements, having a basis to share it is your responsibility (Terms, Section 3). You can revoke a connection at any time, and the developer can ask our privacy officer (hyunjaeyoo@plaro.kr) to delete their address.
• No sale: PLARO does not sell personal information or share it for targeted advertising. Nevada residents may send a request not to sell their information to hyunjaeyoo@plaro.kr; we respond within 60 days.

Users (PMs) can send their clients' contacts requests to confirm requirements or acceptance results (with an extra-work quote) and meeting invitations through PLARO. PLARO processes the client contact's information as the user's service provider, on the user's instructions, and the user must have a basis for entering it and contacting them (such as a contract or business relationship with the client).

• Information processed: the client contact's name, email address, and preferred language and time zone, as entered by the user. Users can edit or delete saved contacts at any time.
• Requirements confirmation: when the confirmation page was opened, the client's answer (confirmed as is, or changes requested) with any comment and per-item notes, when they answered, how they were verified, and a pseudonymized (hashed) IP address and browser type. When a link was shared by hand, a 6-digit code is emailed to the client before they can answer. If the client presses the PLARO button on the page, the time is recorded.
• Acceptance confirmation: each requirement's result (met, or not met with the reason) and the date it was checked are sent, and the client's answer is kept the same way as a requirements confirmation.
• Extra-work quotes, change agreements and acceptance records: they contain the recipient you enter (client company, contact name and email), your business details (the billing profile), the amounts, and, in agreements and acceptance records, who confirmed, when, how they were verified and what they wrote. Quotes are saved in the project; the documents are made in your browser (print or Excel), and PLARO records only that a document was taken out.
• Record fingerprints: so that confirmation records cannot be altered later, a SHA-256 fingerprint of each requirements version and each client answer is computed and linked to the previous one. The original content cannot be recovered from a fingerprint, and fingerprints are deleted with the project.
• Emails to clients: (1) the requirements or acceptance confirmation request (and its code, with the amount when an extra-work quote goes with it), (2) a copy of their own answer after they reply (what they answered and when), (3) meeting invitations (date and time, video meeting link, calendar file), and (4) a cancellation notice when an invited meeting is cancelled (with a calendar file). They are sent only when the user presses send (the answer copy once, when the client answers; the cancellation notice once, when the user cancels a meeting they sent an invitation for), and replies go to the sending user. They are sent through Amazon Web Services (Amazon SES), listed in the table in Section 6, and the delivery log keeps the recipient address masked.
• Retention and deletion: a client's answer is kept as a confirmation record that cannot be edited later. When the user deletes the project, the client information and confirmation records are deleted after the 30-day trash period; when the user deletes their account, they (quotes and record fingerprints included) are deleted without delay. The account deletion screen reminds the user to take out any documents they want to keep first. A deleted contact's name remains only in the records of requests already sent.
• Client rights: clients may ask the user who contacted them, or PLARO at the contact email in this Policy, to access, correct, or delete their information; PLARO handles such requests together with that user.
• Your clients’ voices in recordings: recordings and transcripts may contain your clients’ voices and what they say. PLARO processes them only on your instructions to provide the service to you (including AI analysis), never for its own purposes or to train AI. In PLARO video meetings, speakers are told apart by who was talking at the time. When speaker separation is turned on for a recording (in person or from another app’s meeting), AssemblyAI creates voice features (treated as biometric data by some laws) to tell the speakers apart within that recording, uses them only for that, and does not keep them after returning the transcript. PLARO does not receive them and does not identify anyone by voice. Biometric retention and destruction: these voice features are made for each recording and permanently destroyed by AssemblyAI when it returns that recording’s transcript, when their purpose is complete. The time you confirmed consent when turning speaker separation on, and the version of that wording, are kept with the recording and deleted with it. Telling your clients about this processing, and obtaining any consent the law requires (such as written consent before speaker separation), is your responsibility (for example, section 11 and IPP 3A of New Zealand’s Privacy Act 2020). Clients who join a meeting as guests are recorded only after the join screen tells them about the recording, transcription and this Policy and they agree.
• Conversations with your clients: if you upload a messenger conversation with a client (such as a KakaoTalk chat export) or a transcript from a meeting or recording app, the client names, times and words in it are processed the same way. Only the words are sent to AI, not names or times; who said something and when is looked up in the original to label the evidence in results. So that the next upload of the same chat is compared from where the last one ended, we keep a non-reversible value (HMAC-SHA-256) made from the chat's name or its participants. An iPhone zip file is opened in your browser and only the chat text is uploaded; photos and videos are not sent to PLARO.

To provide the service, PLARO entrusts the processing of personal information to the companies below. Amazon Web Services Korea LLC is a Korean company and processes it on servers in the Republic of Korea (Seoul); all the others are located outside the Republic of Korea. Information is sent over encrypted connections (HTTPS, TLS) when you use the relevant feature. This is entrustment and storage needed to perform our contract with you, disclosed in this Policy under Article 26 and Article 28-8(1)(3) of the Personal Information Protection Act. Information sent to Creem (Estonia), the seller, is a provision to a third party, not entrusted processing, and is described in Section 4.

• Retention: uploaded files and recordings are stored in R2 until you delete them. AI, transcription and delivery providers keep data after processing only for the period their policies set and then delete it: OpenAI up to 30 days for abuse monitoring (speech-to-text requests are not kept), Anthropic deletes within 30 days, and AssemblyAI deletes uploaded audio within 48 hours while PLARO has the transcript deleted as soon as it fetches it. Content flagged for policy violations may be kept longer by the provider. We require deletion without delay when the contract ends.
• If you do not want your information transferred abroad, you can stop using the relevant features (AI, recording transcription, paid purchases) or ask to delete your account; those features will then be unavailable. AI is used only for work you start; no background automation sends your data to AI.
• Web push notifications pass through the push service chosen by your browser (Google, Mozilla, Apple, and others), and their content is encrypted. When you sign in with Google or Microsoft, that company passes your name, email, and account identifier to PLARO, and the sign-in itself follows that company's policy. You can remove PLARO's access to your Microsoft account at https://account.live.com/consent/Manage.
• We use the AI and transcription providers only on terms under which they do not use the information PLARO sends to train their AI models (the OpenAI API, the Anthropic API, and AssemblyAI with its model improvement program turned off).
• PLARO itself does not use your content, recordings or transcripts to train AI, and will not start doing so for information it already holds without your express consent.
• If you live outside Korea: your account and service information is stored on PLARO’s servers in the Republic of Korea, uploaded files and recordings in Cloudflare R2’s Asia-Pacific region, and it is processed by the companies above and Creem (Section 4) in the United States and Estonia, so it leaves your country (for example Canada and Québec, Australia, New Zealand, Singapore or the United States). There, courts, law enforcement and national security authorities may access it under their laws. PLARO’s written agreements with these companies (data processing or data sharing agreements) set out security measures, limits on retention and notice of a breach without undue delay. Each company publishes a list of the sub-processors it uses and their countries, and gives notice when the list changes.
• If a company or the data transferred changes, we update this Policy and let you know.

Connecting Google Calendar is optional. If you connect it, PLARO receives only the information below and uses it only for the purposes below.

• What we receive: the connected Google account email and the identifiers and links of the meetings PLARO adds. PLARO does not read the other events in your calendar.
• How we use it: PLARO adds to your Google Calendar only the project meetings you choose to put there, and when such a meeting is changed or cancelled, it updates or removes the copy it added. It updates or deletes only events that PLARO created. The account email is used to show which account is connected.
• No AI use: information received from Google Calendar is never sent to PLARO's AI features or to any AI provider. No information received through Google APIs is used to create, train, or improve any AI or machine learning model, including generalized or foundational models.
• Sharing and access: information received from Google Calendar is not sold or used for advertising, and is not transferred to anyone except as needed to provide the features above, for security, or to comply with law. People do not read it unless you agree, or it is needed for security or to comply with law.
• Storage and deletion: the account email and access tokens are stored encrypted. When you disconnect, PLARO asks Google to revoke its access and deletes the connection and sync records (meetings already added stay in your Google Calendar). You can also remove access at any time in your Google Account settings (https://myaccount.google.com/permissions).

PLARO's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs, including Google Calendar, will adhere to the Google User Data Policy, including the Limited Use requirements.

• Account and general service data enter the deletion process without undue delay when the user deletes them or closes the account. Encrypted database backups keep it for up to 30 days before it is removed from them too. Material created in a team space (projects, recordings and the like) and the team’s activity log are, however, the team’s work records: they are not deleted but stay with the team, and the material passes to the team owner.
• Recording audio files and transcripts are retained until the user deletes them, subject to the cumulative storage allowance of the selected plan.
• Signup risk signals, deleted social-account hashes, and free-benefit or refund-abuse prevention logs may be retained for up to 180 days for security and operations.
• Sign-in records (date and time, IP address, browser) are kept for 180 days and e-mail delivery logs (recipient address, type, subject, time sent, and whether the mail was delivered or bounced — with the address masked for mail to people who are not users and for users who have closed their account) for 90 days, and are then deleted. An address that bounced permanently is kept for 1 year as an irreversible value (HMAC-SHA-256) and in masked form, so that we do not mail it again.
• Developer AI connection access records (connection, date and time, IP address, sign-in step or function called, result) are kept for 1 year (Article 8 of Korea’s Standards for Securing the Safety of Personal Information), even after the connection, the project or the account is deleted. The developer’s email address and name are deleted 1 year after the connection is revoked (or after it stopped for 90 days without use), and at once when the project or the account that made the connection is deleted.
• Access records of PLARO staff viewing or handling your information (staff member, date and time, IP address, the user concerned, what was done) are kept for 1 year (Article 8 of Korea’s Standards for Securing the Safety of Personal Information), even after the account is closed.
• Access records of signed-in use (account number, date and time, IP address, the screen opened or action taken and the project, meeting or recording numbers it concerned, sign-ins, failed sign-ins and sign-outs) are kept for 1 year (Article 8 of Korea’s Standards for Securing the Safety of Personal Information). Search terms are not kept. They remain for this period after the account is closed, and are included when you ask for your information.
• AI request records (without the request or the answer: the feature, model, provider, result, time taken, token counts, cost, who pays, user number, team number, date and time) are kept for 1 year to check cost and quality. When you close your account, your user number is removed from them.
• Records of how we handled a request about your information (access, export, correction, deletion, restriction) — e-mail, user number, country, type, date received, deadline, date handled, outcome and any reason for refusal, and who handled it — are kept for 5 years from the date handled, to show it was handled in time, even after you close your account. The data file made for an access or export request is deleted within a day after its download link ends (7 days after it is made).
• As required by law, the following records are kept separately from other information for the stated periods and then destroyed: records of contracts and withdrawals, 5 years; records of payment and supply, 5 years; records of consumer complaints and disputes, 3 years; records of labeling and advertising, 6 months (all under the Act on Consumer Protection in Electronic Commerce); tax books and supporting documents, 5 years (Framework Act on National Taxes); sign-in records, 3 months (Protection of Communications Secrets Act — PLARO keeps them 180 days as above). The items kept are the e-mail address, order and subscription identifiers, plan and amount, the times of payments, refunds and withdrawals and how they were handled, complaint records, and sign-in times and IP addresses.
• Destruction: information whose retention period has ended or whose purpose has been achieved is destroyed without delay. Electronic files are deleted so that they cannot be recovered, and paper documents are shredded or incinerated.

• PLARO uses cookies and browser storage to keep you signed in, for security (preventing automated sign-ups and abuse), and to remember your language and display settings. We do not use cookies for advertising or behavioral tracking.
• You can refuse or delete cookies in your browser settings. If you refuse essential cookies, some features such as signing in will not work.
• No tracking: PLARO runs no third-party advertising, analytics or social-media trackers, and its own server logs are used only to run and secure the service. On the sign-up screen, Cloudflare Turnstile receives connection signals such as your IP address to tell bots apart; Cloudflare states it uses them only to detect bots and improve that detection, not to identify, profile or target anyone, and it uses them for that improvement as a controller in its own right (https://www.cloudflare.com/turnstile-privacy-policy/). We do not let any other company collect personal information about your online activities over time and across different websites through PLARO. Because PLARO does not do such collection itself, it does not respond differently to browser Do Not Track signals.

• PLARO applies reasonable security measures such as access controls, authentication, encryption or hashing, audit logs, backups, vulnerability patching, rate limits, and CAPTCHA. Every sign-in also asks, after the password or Google or Microsoft, for a one-time code we mail you (an authenticator code for admins), and we keep tamper-evident access records of signed-in use (Articles 6 and 8 of Korea’s Standards for Securing the Safety of Personal Information).
• If a security incident is confirmed and legal notice is required, PLARO will notify affected users and authorities as required and reasonably work to mitigate harm.
• If a breach affects information we hold for you, including your clients’ information, we tell you without undue delay. Where the law requires, we also notify the regulator and the people affected (for example, the people affected in Korea within 72 hours of our learning of it, Singapore’s PDPC within 3 calendar days of assessing a breach as notifiable, California residents within 30 days, and in New Zealand, Canada and Québec as soon as practicable). We keep a record of every incident.

• Users may request access, correction, deletion, restriction, withdrawal of consent, account closure, and push-notification opt-out to the extent provided by law.
• You may also exercise these rights through a legal representative or an authorized agent; in that case we may ask for proof of the authorization.
• Requests may be sent to the contact email in this Policy. Some requests may be limited because of identity verification or legal retention obligations.
• Response time: requests from people in Korea to access, correct, delete or restrict their information are handled and answered within 10 days of receipt. For people elsewhere we meet their country’s legal deadline — 20 working days in New Zealand; 30 days in Canada and Québec (in Québec, no answer within 30 days counts as a refusal); in Singapore as soon as reasonably possible, and if we cannot within 30 days we tell you in writing when we will. When we extend a deadline in Canada, we also tell you that you may complain to the Privacy Commissioner.
• Users in Singapore: an access request also tells you how the information has been or may have been used or disclosed in the past year, and when we correct it we also send the correction to anyone we disclosed it to in that year. Users in New Zealand: if we need more time, we tell you within 20 working days how long, why, and that you may complain to the Privacy Commissioner; if we refuse a correction, we attach your statement of the correction sought to the information.
• Portability: you may ask to receive the information you gave us in a structured, commonly used format (JSON or CSV), or to have it sent to a body the law allows.
• Review and correction: you can review and change account details such as your name, email and language yourself in Account settings.
• Users in Québec: if we refuse a request we tell you the provision relied on and your remedies, and you may apply to the Commission d’accès à l’information within 30 days of the refusal. Where the law provides, you may also require links about you to be de-indexed.
• Appeals: if we decline a request, we tell you why. You may appeal by writing to hyunjaeyoo@plaro.kr with "Appeal" in the subject; we answer within 60 days with our reasons. If we deny an appeal, US residents may contact their state attorney general.

• Contact email: hyunjaeyoo@plaro.kr

Only adults may sign up for PLARO (19 or older in Korea; elsewhere, the age of majority where you live), and we ask you to confirm this when you sign up. We do not collect your date of birth or identity documents for this. If we learn that information about a minor, in particular a child under 14, has been collected, we close the account and destroy the information without delay.

Please send complaints about how we handle personal information to hyunjaeyoo@plaro.kr first. We acknowledge them within 7 days and reply in writing within 30 days. If you are not satisfied with our answer, you can contact the organizations below.

• Personal Information Dispute Mediation Committee: +82-1833-6972, www.kopico.go.kr
• Personal Information Infringement Report Center (KISA): 118 within Korea, privacy.kisa.or.kr
• Korean National Police Agency: 182 within Korea, ecrm.police.go.kr
• Australia: Office of the Australian Information Commissioner, www.oaic.gov.au, +61 2 9942 4099
• New Zealand: Office of the Privacy Commissioner, www.privacy.org.nz, 0800 803 909
• Canada: Office of the Privacy Commissioner of Canada, www.priv.gc.ca
• Québec: Commission d’accès à l’information du Québec, www.cai.gouv.qc.ca
• Singapore: Personal Data Protection Commission, www.pdpc.gov.sg
• United States: your state attorney general

If we change this Policy, we announce it in the service or by email at least 7 days before it takes effect (30 days for changes unfavorable to you). Earlier versions are available on request. Previous version effective: October 11, 2026. Changed on October 20, 2026: we added uploading messenger conversations with clients and transcripts from meeting and recording apps (Section 5). The only new thing kept is a non-reversible value (HMAC-SHA-256) that recognises the same chat. The same day we added or corrected the developer AI connection (Sections 2, 3, 4 and 8 — newly collected: the developer’s email address and name, hashes of the sign-in codes and tokens, and access records), the address asked of buyers who appear to live in Canada before their first payment (Sections 2 and 3 — it goes into the contract copy), the separate legal bases (Section 3), when stored material may be provided (Section 4), voice features in speaker separation with the time consent was confirmed and their destruction rule (Section 5), the correction that information sent to the seller Creem is a provision to a third party (Sections 4 and 6), the correction of the contracting party for web relay and e-mail delivery to Amazon Web Services Korea LLC (Section 6), each provider’s retention, the storage location and what the provider agreements set out (Section 6), the items kept, the periods for sign-in and e-mail records (with delivery results and bounced addresses), staff access records, access records of signed-in use, AI request records and records of handling privacy requests (Section 8), the sign-in code (Section 10 — newly collected: access records of signed-in use), Korea’s breach-notice deadline (Section 10), and response deadlines by country and the rights of users in Québec (Section 11), and removed the Supreme Prosecutors’ Office from the list of bodies (its Act was repealed). Changed on October 11, 2026: we corrected where uploaded files and recordings are stored — in Cloudflare R2’s Asia-Pacific region, not in Korea (Section 6) — and replaced web traffic delivery with domain name service in what Cloudflare does (web connections are relayed by Amazon Web Services’ server in Seoul). No new information is collected. Changed on October 10, 2026: we added acceptance confirmation requests, extra-work quotes, change agreements and acceptance records, and the fingerprints of confirmation records (Sections 2, 3 and 5). What is newly kept: a quote's amounts and recipient, and the records' fingerprints (SHA-256 — values from which the original content cannot be recovered). Changed on October 9, 2026: to meet the laws of our service countries, we added the privacy officer’s other roles and how we are run (Section 1), required information (Section 2), the consent basis for users in Canada and automated decisions (Section 3), no sale (Section 4), your clients’ voices in recordings (Section 5), no AI training by PLARO and transfers seen from your country (Section 6), no tracking (Section 9), breach notices (Section 10), response times, portability, self-service correction and appeals (Section 11), and the complaint process and regulators by country (Section 13). We collect nothing new. Changed on October 8, 2026: region checks added to the purposes (Section 3 — sign-up and payment are accepted only in our service countries, and access from regions the AI services PLARO relies on do not support is blocked; the country of your IP address is looked up only on our own server). On the same day, Google (Gemini API) was removed from the companies entrusted with processing, and Anthropic, which handles requests when OpenAI cannot respond, was added (Section 6). On the same day, the minimum age for sign-up was raised from 14 to the age of majority (Section 12). Changed on October 7, 2026: the list of service content we collect now matches the features we offer (items were only removed; nothing new is collected). The description of AI processing now matches the current features as well (AI is used only for work you start). On the same day, the Google Calendar connection stopped receiving your busy time ranges (booking links were removed), meeting cancellation notices were added to the emails sent to clients, and the provider that sends client emails was corrected to Amazon Web Services (Amazon SES). Changed on October 5, 2026: Amazon Web Services (service email delivery, the server that relays web connections) added to the companies entrusted with processing, and service email moved from Google (Gmail) to Amazon SES.