How miaminos handles information.

Effective date and scope

Effective September 10, 2026.

This notice describes the information practices for the miaminos public website, free membership, account access, calculator worksheet email, contact form, missing-topic suggestions, and first-party analytics. The private vendor questionnaire has a separate notice tailored to that workflow.

Read the vendor-questionnaire privacy notice

The website operator is miaminos. The accountable privacy role is the Miaminos Privacy Lead. Written access, correction, deletion, and privacy questions can be sent to hello@miaminos.com or submitted through the contact form.

This notice addresses visitors and members in Canada and the United States. Applicable privacy rights depend on the law and the information or activity involved, not only where a visitor lives.

Website delivery and traffic

Cloudflare provides the website infrastructure.

Cloudflare provides DNS, content delivery, security controls, server execution, and database infrastructure. Like other web infrastructure providers, Cloudflare processes ordinary network and request information, which can include IP addresses, routing data, security signals, requested paths, and technical logs. This processing is used to deliver the site, resist abuse, investigate errors, and protect the service.

On public production pages, miaminos uses Cloudflare Web Analytics to understand aggregate visits, page views, referral hosts, approximate countries, browser and device categories, URL paths, and page-performance measurements. Cloudflare describes this browser measurement as cookie-free and says it does not track individual visitors across websites. The Web Analytics beacon is not loaded on private administration, vendor-questionnaire, local, or test pages.

Cloudflare currently makes Web Analytics history available to miaminos for six months. It documents that unsampled beacon data is retained for seven days and then aggregated for longer-term reporting. Provider-controlled network, security, and account records follow Cloudflare's terms and retention practices.

First-party product activity

Daily counters, not raw event histories.

Miaminos stores the following aggregate product measurements in Cloudflare D1:

• Calendar date and test-or-production environment
• An approved event name, such as a calculator result or PDF download
• A fixed category, such as guided/forward or search/results found
• A daily aggregate count

The table has no fields for IP address, browser string, cookie, visitor or session identifier, member email, referrer, raw URL, calculator entry, or search phrase. Aggregate events are not joined to membership records.

Daily counters are retained for a rolling 24 months. Before deletion, the same anonymous totals are rolled into monthly summaries retained for five years and annual summaries retained for ten years. Those summaries contain reporting totals only and cannot restore individual activity.

If a search returns no result, a visitor may deliberately submit a general topic phrase for private editorial review. Miaminos stores that phrase, the search surface, a submission count, editorial status, and internal notes. It is not connected to an email address, membership, cookie, visitor profile, or raw network address. Open suggestions are deleted 180 days after the latest submission. Published and dismissed suggestions are deleted after 90 days, unless the 180-day limit is reached sooner. Associated review-audit records are deleted with the suggestion.

Membership and account access

Email is the account identifier.

Free membership is used to provide future Vendor Intelligence access. Miaminos collects an email address, verification date, the recorded age-of-majority declaration version and date, and any optional update categories selected. It does not request a name or birth date.

Before verification, D1 temporarily stores the submitted email address, a one-way token hash, and request and expiry times. Pending registration links expire after one hour; expired records are removed during subsequent account activity or daily cleanup.

The membership record is stored in Cloudflare D1. A corresponding contact and topic-preference record is synchronized with Resend for requested service emails and optional updates. Membership remains active until the member deletes it; miaminos has not adopted an automatic inactive-member deletion period. Deleting a membership removes the active D1 member, token, and session records and requests deletion of the corresponding Resend contact.

Verification and sign-in links are single-use. D1 stores one-way token hashes rather than the raw link token. A secure, HTTP-only cookie and a one-way session-token hash keep the account signed in for up to 30 days. New links replace older pending links. Used, failed-delivery, and expired authentication records are removed during account activity and by daily cleanup.

Members can review their email address and update optional topics, sign out, or permanently delete their membership from the account page. Membership access remains separate from optional email updates. Necessary verification, security, and account-access notices do not subscribe members to newsletters or ongoing Vendor Intelligence updates.

A newsletter unsubscribe link can turn off all optional updates after confirmation without signing in; it does not delete the membership. D1 keeps a one-way link-token hash, its member association, expiry, and synchronization result for up to 180 days. These records are removed during daily cleanup after expiry, or when the membership is deleted. If synchronization is unfinished, a pending opt-out flag stays with the membership to prevent optional email delivery. It is cleared after synchronization, a successful authorized preference update, or membership deletion; it does not extend the link’s expiry or retain the expired token record. Unsubscribe pages are excluded from browser analytics.

For optional newsletters, D1 keeps the reviewed message, recipient list, administrator approval, and delivery result for up to 180 days. Deleting a membership removes its address from queue receipts. Delivery records do not store the personal unsubscribe link. Periodic provider delivery checks can continue for up to 28 days after a campaign attempt. We retain the receipt status, check time, automatic or manual check source, and minimal scheduling and error counters, not the retrieved message contents or open/click activity. An opaque delivery reference helps match an uncertain attempt to its provider receipt without resending it. A known bounce, complaint, or provider suppression adds a separate newsletter delivery hold, with its reason and date, to the membership record. That hold remains while the membership exists; changing optional preferences does not clear it. Deleting the membership removes it. Turning off a topic is saved locally before provider synchronization; unfinished synchronization blocks optional sending until resolved.

Requested email and contact

Resend delivers; Google Workspace receives.

Calculator arithmetic runs in the browser. When someone requests a downloadable or emailed PDF, the entered calculation values are sent to Cloudflare to generate the worksheet. Miaminos does not save those values or the generated worksheet in D1. A share link contains entered values in its browser-only URL fragment; anyone with that link can read them.

If someone requests an emailed calculation worksheet, the recipient email address and generated attachment are sent to Resend for that one delivery. They are not stored in the miaminos database and do not create a membership or optional subscription.

Contact-form names, email addresses, optional organizations, regions, topics, related URLs, and messages are sent through Resend to the appropriate Google Workspace role inbox. Miaminos uses them to review and respond to the message. The website does not copy those contact fields into D1. Each submission receives a matter reference. D1 keeps only the latest reference number for each contact category so numbers are not reused; these counters contain no sender details or message contents.

When miaminos assists with a formal membership access, correction, or deletion request, its private administration register stores a matter ID, request type, masked address, secret-keyed email lookup value, requested preference state when applicable, workflow dates, administrator, and synchronization result. It does not store the contact-message body or raw verification link. The exact email must be entered again for a sensitive action, and the registered address must first confirm a single-use link. Completed register records expire after 24 months; unused verification records expire after 24 hours. Associated privacy-case audit entries are removed when the request record is deleted. Deleting a membership does not by itself delete a separate privacy case, mailbox conversation, delivery log, or provider recovery copy; their own retention schedules still apply.

Resend documents 30-day retention for sent-email data on its standard service. Contact conversations retained in Google Workspace follow the miaminos mailbox schedule: general, technical, and testing matters are deleted six months after resolution; correction, source, copyright/removal, and privacy conversations are deleted after 12 months, with a minimal non-sensitive decision record retained for up to 24 months; and vendor or commercial correspondence is deleted 24 months after the last interaction. A documented legal hold or active dispute pauses deletion only for affected records.

A matter is resolved when miaminos has sent its final substantive response or recorded its final decision and no further action is pending. Reopening it cancels the previous deletion date; a new period starts when it is resolved again. An unanswered message is not automatically resolved. Mailbox deletion is checked through a monthly review, rather than occurring at the exact instant a retention period ends.

Abuse prevention and safeguards

Short-lived controls protect public forms.

Membership requests, account sign-in requests, calculator emails, contact submissions, and missing-topic suggestions use rate limits to reduce automated abuse. Before storage, the submitted email or requesting network value is transformed into a secret-keyed pseudonymous identifier. These one-hour counters are kept separately from membership, analytics, and suggestion content and are removed during later protected activity and by daily cleanup.

Safeguards include encrypted connections, secure HTTP-only session cookies, one-way authentication-token storage, role-restricted administration, masked member views, separate test and production databases, and restricted service credentials. No system can guarantee absolute security.

Miaminos does not sell or rent personal information. Information is disclosed to Cloudflare, Resend, and Google only as needed to provide, secure, and administer the described services, or when disclosure is required by applicable law.

Cross-border processing

Service providers operate internationally.

Cloudflare, Resend, and Google operate infrastructure in more than one country. Resend states that its primary processing occurs in the United States. Information handled by these providers may be processed outside the province, state, or country where a visitor lives and may be subject to lawful access in those jurisdictions.

Miaminos reviews provider roles and limits the information sent to each service. Their own terms, privacy notices, security controls, subprocessors, and lawful-retention obligations also apply to provider-controlled records.

Your choices and requests

Access, correct, delete, or raise a concern.

A person may make a written request to learn whether miaminos holds personal information about them, ask for access, challenge its accuracy, request a correction, or request deletion where applicable. Miaminos may request limited information needed to confirm identity and locate the record. It will not request a government identity document by default.

For membership records, the safest verification is control of the registered email address. If a request comes from another address, miaminos will normally send a confirmation to the registered address before disclosing or deleting the record. If that address is no longer accessible, miaminos will consider a proportionate alternative without collecting more information than needed.

We respond within the time required by applicable law. Where PIPEDA applies, we provide a substantive response to an access request within 30 calendar days of receipt, unless a permitted extension applies. We explain any extension and applicable complaint rights. We also explain an inability to locate information or a lawful refusal.

These request channels are available to people in both Canada and the United States. PIPEDA is a Canadian law; United States federal or state privacy laws may also apply. Rights, exceptions, and response deadlines vary. If applicable law gives you a right to appeal a request decision, reply to that decision or contact hello@miaminos.com to request a review. We will explain the applicable appeal process and deadline.

Send privacy complaints to the Miaminos Privacy Lead so the concern can be investigated. You may also contact the regulator with authority over your concern; contacting miaminos does not limit that option.

Canada: Contact the applicable federal or provincial privacy regulator. The Office of the Privacy Commissioner of Canada ↗ provides guidance on reporting a privacy concern.

United States: Contact your state attorney general ↗ or the state privacy regulator with authority over your concern. You can also report potentially unfair or deceptive business practices to the Federal Trade Commission ↗. The FTC uses reports for enforcement but does not resolve individual complaints.

Changes to this notice

Material changes are recorded.

Miaminos will update the effective or review date when this notice changes. If a material change affects how membership information is used, miaminos will provide an appropriate notice and obtain additional consent where required. A privacy-policy update does not automatically subscribe a member to optional email topics.

Accountable privacy role

Miaminos Privacy Lead

Send a written access, correction, deletion, complaint, or other privacy request. Do not include medical records or unnecessary sensitive information.

Email hello@miaminos.com or use the contact form.

Effective: September 10, 2026