Privacy Policy
1. Overview
whatismysize.com ("we", "us", "our") provides free tools that check the size of your photo, signature or other file against what an application form asks for and fix it, and tools that show the size of your screen. This Privacy Policy explains how we collect, use, and protect your information when you use our website.
In short: your files are processed in your browser and never uploaded. We keep anonymous counts of visits and tool use, with no cookies and no third-party analytics.
The lawful basis for our processing under the EU General Data Protection Regulation (GDPR) is our legitimate interests (Article 6(1)(f)) in understanding how the site is used and improving the accuracy and usefulness of our tools. We believe the processing described here has a minimal privacy impact given that it is anonymous, first-party, stores no IP address or user agent in our analytics database, and is not shared with any third party for advertising, profiling, or cross-site tracking.
2. Information We Collect
Your Files
The photo, signature, thumbprint or other image you choose is read and changed only in your browser, on your device. It is never uploaded: no part of your file is sent to our servers or to anyone else. In detail:
- Your browser opens and checks the file. The fixed copy is made in your device's memory and offered to you as a download from there. Closing or reloading the page discards both.
- We never receive the file, its name, what it shows, or the information stored inside it (such as camera details or location). We never receive its width and height in pixels.
- A file that already meets the requirement may be handed back exactly as you gave it, with whatever is stored inside it. We do not promise to remove any information from a file.
- The numbers you type into the custom resize tool are used on your device and are not sent
as such: analytics only hear the word
custom. The size of the file we make is sent, though (the size of the result, below), so a file made to a KB limit you typed will show up as a size within that limit.
The only things about a file that reach us are the anonymous counts listed under tool_use, no_answer and ui_open below: which requirement
you picked, what kind of item it is for, whether the file was fixed, a coarse size bucket for
the file you chose, the size of the result, and which check failed.
Screen and Ruler Tools
The screen size, resolution, viewport, ruler and PPI tools read facts your browser already
shows to every website: your screen's size in pixels, its pixel ratio, your window size, its
orientation and its colour depth. They do their sums on your device. These readouts, the
ruler and your calibration are never sent to us. The only device detail in
our analytics is a coarse device class (mobile, tablet or desktop), worked out from your window's width.
The ruler remembers your calibration, one number (CSS pixels per millimetre), in your
browser's localStorage under wms_ppmm, so you do not have to repeat it on the
same screen; calibrate again after a zoom change or on another screen. It stays on your
device and is never sent to us. The Reset button removes it, and so does clearing site data.
Anonymous Usage Data (First-Party Analytics)
To understand how the site is used and which tools work, we collect a small amount of anonymous usage data on our own servers — not through Google Analytics or any third-party analytics service. When you browse a page or use a tool, your browser sends us an event made of:
- A random session ID and a random anonymous user ID, both described in section 3, and an event version number
- Your device class (
mobile/tablet/desktop), derived from your browser window's width — not your model, OS, or user agent - Added by our server when it receives the event: the time, and a coarse language/region tag
like
en-USorde-DE, taken from your browser'sAccept-Languagerequest header. We never store the full header, never store your IP address, and never look up your precise location
The kinds of event, and what each one carries besides the above:
page_view— when a page loads: the page path (for example/resize-image), the page category (home,toolorother) and, if you came from another website, that site's host name (never the full address)page_engaged— once per page view, when you leave the page or switch to another tab or app: the path and category, how many seconds you stayed (capped at one hour) and how far down you scrolled (0 to 100 percent)tool_use— when the file fixer gives you a file that meets the requirement (or your file already did): the tool namefile-fixer, the requirement (spec_id: a public id such as a form's page name, orcustom), the kind of item the requirement is for (photo,signature,thumbprint,documentorcustom), the outcome (fixedoralready_ok), a coarse size bucket for the file you chose (in_bucket:<100KB,100KB-1MB,1-3MB,3-10MBor>10MB) and the size of the result in KB to 0.1 KB (out_kb). When your file already met the requirement and was returned unchanged, that last figure is your own file's sizeno_answer— when the file fixer cannot read your file or cannot meet the requirement: the tool name, the reason, the requirement and the kind of item as above, and the check that failed (kb_min,kb_max,dimensions,formatordecode) — never anything about the file itself.cannot_meet_specis the only reason this site sends today; our server still acceptsout_of_rangeandno_matchfrom earlier versions, together with a free-forminput(see Earlier Versions of This Site below)ui_open— when you open an answer in a question list (the text of that question, which is fixed text on the page) or choose or drop a file into a tool (file_picked, labelled with the requirement orcustom, never the file's name), together with the page path and categoryoutbound_click— when you click a link that leads to another website, such as an official notice: the destination's host name and path (never the query string), a label for the kind of link (for exampleofficial_guidefor an official notice, orexternalfor any other), the link's text (up to 100 characters) and the page you clicked from. We record nothing about what you do on the other site
We do not store your IP address, we do not store your user
agent, we do not track you across sites, and we do not set any third-party cookies. The events are received by an API we
operate at api.whatismysize.com and stored in a Postgres database, and they are used
only to operate and improve this site. If Do Not Track is on, or you have opted out (section 9),
your browser sends none of them.
Nothing you type into a box on this site is sent in an event.
Earlier Versions of This Site
Earlier versions of this site offered size charts and converters for shoes, bras, clothing
and underwear. They sent further anonymous event types, which this version does not send: feedback (thumbs up or down on a result, with the size you usually wear, the
size you bought and a reason, when you gave them), brand_request (a brand you
asked us to add), personal_action (saving or sharing sizes), cta_click (clicking a link from one page of that site to another: a short name
for the placement, the two page paths, the category and brand of the page you clicked from,
and the link's text), fit_report_submitted (that you sent a bra fit report) and section_view (which parts of a long page you scrolled to). Their tool_use and no_answer events could also carry the measurements
and sizes you had typed into a converter, and the text of a brand search that found nothing
(the no_match and out_of_range reasons).
Those events are still in our database under the same random IDs and are kept for the period in section 7, like every other event. Our server still accepts these older event types, so a browser that is still running an old copy of the site may keep sending them until it reloads.
The bra fit reports of the earlier site are kept in a separate table. Each one holds the brand, the band and cup you tried, whether you kept or returned the bra, optionally your bust and underbust measurements, your random user ID, and a one-way hash of your IP address: your address combined with a random value that lived only in the server's memory and changed each time the server restarted, used only to spot repeated submissions. We no longer collect these reports and no page or server route of this site reads them any more, but we have not deleted them. They are covered by this policy, and you can ask us to delete yours (section 9).
The earlier site also saved your preferences, measurements and saved sizes in your browser's localStorage. This version does not read or use them, but they stay on your device until you clear site data for whatismysize.com.
3. Cookies & Local Storage
We do not use cookies — not for analytics, not for tracking, not for advertising. This site does not set any cookies on your device, and Google Analytics is not loaded at all.
This version of the site keeps the entries below in your browser's storage. Storage is not a cookie and is never sent to a server by itself. Of these entries, only the two random IDs leave your device, inside the events described in section 2.
wms_sid(sessionStorage) — a random anonymous ID for the current browser tab. It is not shared with other tabs and expires when you close the tab. It is sent with each event.wms_uid(localStorage) — a random anonymous user ID and the time it was created, so the same browser is recognized across visits for analytics purposes only. It contains no personal data and rotates automatically at least every 13 months. The ID is sent with each event, to our own analytics server and nowhere else; the time it was created is not sent.wms_analytics_opt_out(localStorage) — the wordtrueif you opted out of analytics (section 9). It is never sent to us.wms_ppmm(localStorage) — your ruler calibration, one number. It stays on your device and is never sent to us.sveltekit:scrollandsveltekit:snapshot(sessionStorage) — written by SvelteKit, the framework this site is built with, when you leave or hide a page, so that your browser's Back button can put you back where you were. They hold your scroll position for each page in this tab's history, and nothing else. They never leave your device and expire when you close the tab.
If your browser blocks storage, the IDs are kept only in memory and are gone when you close or reload the page.
4. Information We Collect via Forms
The contact form is submitted to Formspree (formspree.io), a third-party
form processor, so that we receive an email notification when you write in. What you send —
your message, the reason you choose and, if you add them, your name and email — goes from
your browser straight to Formspree, not through our API, and is stored by Formspree on our
behalf. We use it to answer you and to correct what you report. See Formspree's Privacy Policy. The form cannot take files, and you should never send a photo or document to us.
Nothing else on this site collects text you type: the custom size boxes and the ruler's controls work on your device and are not sent anywhere.
5. Third-Party Services
Our site uses or links to the following third-party services:
- Formspree: Delivers the messages sent through the contact form, as described in section 4, under its own privacy policy.
- Render: Hosts this website's pages and runs our analytics server (
api.whatismysize.com, in Oregon, United States). To deliver a page or receive an event, Render necessarily handles the IP address and request details of the connection; our analytics database does not store them. - Supabase: Runs the Postgres database that stores the anonymous events described in section 2.
- Official notices: Form pages link to the official notice each requirement comes from, on the website of the authority that publishes it. We record only that you clicked and where the link leads (section 2). Those websites have their own privacy policies.
The typefaces of this site, Bricolage Grotesque and Figtree, are served from whatismysize.com itself, so reading a page makes no request to a font service.
Our first-party analytics server is operated by us, on Render's hosting, and the events it receives are stored in a Supabase database. We run no advertising and have no affiliate links, so no advertising or affiliate company receives data from this site.
6. Data Sharing
We do not sell your information and we do not share it with third parties for advertising, profiling or cross-site tracking. The only third parties involved are the services in section 5: Render relays the anonymous events and Supabase stores them, and Formspree delivers contact-form messages. Your files are never shared with anyone, because they never reach us.
7. Data Retention
We retain anonymous analytics events (the data described in section 2, including the events
of earlier versions of this site) for a rolling window of 24 months from
the date each event is recorded, after which the row is deleted from our database. The
anonymous user identifier in your browser (wms_uid) rotates at least every 13 months, so a visitor who returns after that window will look like a new
visitor to our analytics. The session ID (wms_sid) disappears when you close
the tab.
Data stored in your browser (the two IDs, wms_analytics_opt_out and wms_ppmm) stays on your device until you clear it. We have no control over
local browser storage.
We have not set a deletion date for the bra fit reports of the earlier site (section 2). You can ask us to delete yours at any time (section 9).
Form submissions sent to Formspree (see section 4) are retained according to Formspree's own retention practices, described in their privacy policy.
8. International Data Transfers
Our analytics server runs on Render in the United States, and the events are stored with Supabase. When you submit the contact form, data travels to Formspree, also based in the United States. This means personal data originating in the EU, UK, or other regions may be transferred to and processed in the United States or other countries.
These transfers are made under the Standard Contractual Clauses approved by the European Commission, which our service providers include in their data processing agreements. You can request more information about these safeguards via the contact form.
9. Your Rights
If you are located in the EU, the UK, or another jurisdiction with comparable data protection law, you have the following rights in relation to the anonymous data we hold about your sessions:
- Right of access (Art. 15 GDPR) — request a copy of the data associated with your current anonymous user identifier.
- Right to rectification (Art. 16) — request correction of inaccurate data.
- Right to erasure (Art. 17) — request deletion of the data associated with your anonymous user identifier.
- Right to restriction (Art. 18) and portability (Art. 20) — request that we limit processing or provide the data in a structured machine-readable format.
- Right to object (Art. 21) — opt out of our analytics at any time using the controls below.
- Right to lodge a complaint with a supervisory authority — for example, your national data protection authority in the EU, or the Information Commissioner's Office (ICO) in the UK.
To exercise any of these rights, please include your anonymous user ID when you contact us. It is the uid value inside your browser's wms_uid localStorage entry (in your browser's developer tools, open Application,
then Local Storage, then whatismysize.com). It is the only identifier that lets us locate the
data associated with your browser; we cannot find data from an ID that has been cleared.
Opt out of analytics
Use the button below to turn off our first-party analytics on this device. We also automatically honor your browser's Do Not Track setting when it is enabled.
Checking your setting…
Your choice is stored in your browser's localStorage under wms_analytics_opt_out. Clearing site data will reset it.
Turning analytics off stops this browser from sending events. It does not delete the IDs already stored in your browser, or events we have already received: to remove the IDs, clear site data for whatismysize.com, and to have earlier events deleted, contact us as described above.
10. California Residents (CCPA/CPRA)
If you are a California resident, you have rights under the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA). The categories of personal information we collect are described in section 2: random identifiers (the session and anonymous user IDs), your activity on this site (pages, clicks, scrolling and time on a page), and coarse device and language information.
We do not ask for sensitive personal information, and your files never reach us. We do not sell or share your personal information with third parties for advertising purposes or for cross-context behavioral targeting.
You have the right to know what we collect, to request deletion, and to correct inaccurate information. To exercise these rights, use the opt-out button in section 9 or contact us.
11. Children's Privacy
Our site is a general-audience tool that may be used by people of any age. We do not require accounts, we do not allow comments or public user-generated content, and we collect only the anonymous, first-party data described in section 2, plus whatever you choose to write in the contact form.
In line with the UK Age Appropriate Design Code (Children's Code), any data we happen to receive from a visitor under 18 is treated with the same high privacy standards as data from any other visitor: anonymous, no profiling, no advertising, no sharing with third parties. We do not use age or any other signal to target children specifically.
Consistent with the US Children's Online Privacy Protection Act (COPPA), we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, please contact us and we will delete the associated data from our analytics store.
12. Data Breach Notification
In the event of a personal data breach that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority within 72 hours of becoming aware of the breach, in accordance with Article 33 of the GDPR. Where the breach is likely to result in a high risk, we will also take reasonable steps to communicate the breach to affected users through this website.
13. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be posted on this page with an updated "Last updated" date. We encourage you to review this page periodically.
14. Contact
If you have questions about this Privacy Policy or wish to exercise any of the rights described in sections 9 and 10, please contact us.