SIZE IT UPPARTY
Menu

Contact Size It Up Party

Use this page to ask a general question, report a measurement or source problem, raise a copyright or permission concern, or make a privacy request. The public contact address is support@sizeitupparty.com.

Size It Up Party does not use a public contact form in V1. Email lets you keep a copy of the message and include the context needed for review. Please choose the guidance below that best matches your request. Clear, specific information usually makes it easier to investigate and respond.

Do not send passwords, verification codes, payment-card details, government identification, medical records, or other sensitive information that is not necessary for your request. We will never ask for your Google password. If a request concerns an account, provide only the public leaderboard name and the Google email address when reasonably needed to locate the record.

General help

For a general gameplay or website question, include the page you were using, what you expected to happen, what happened instead, and the browser or device type if the issue appears technical. A short sequence of steps is more useful than a message that only says the game did not work.

Before writing, you may find the answer on the How to Play page. Moving the target changes its position, while scaling the target changes the estimate. Camera zoom helps the comparison fit the screen but does not change the score. Daily contains five shared rounds for a UTC date, and Unlimited provides separate practice without changing the Daily result.

If the page failed to load, try the visible retry action and check the connection first. If a refresh still fails, tell us whether the problem affects Daily, Unlimited, How to Play, or another page. Please do not include internal browser logs unless requested; a plain-language description and visible error message are enough for the first report.

Suggested subject: General support

Report a measurement correction

Real-world measurements can vary by model, specimen, configuration, dimension, and measuring method. A correction report should compare like with like. For example, an aircraft’s length and wingspan are both valid measurements, but one cannot directly correct the other. A building’s roof height may differ from its architectural height, and an animal species may have a range rather than one universal value.

Include the following:

A direct manufacturer specification, institutional record, maintained database entry, or clearly identified reference is usually more useful than an unsourced snippet. If the page contains several values, identify the exact table, section, model, or specimen that supports the correction.

We may keep the current value, add or improve a qualifier, replace the source, publish a corrected puzzle version, or withdraw the puzzle. A different valid number does not necessarily mean the current record is wrong; it may describe another definition. The review focuses on matching definitions and presenting the comparison clearly.

Suggested subject: Measurement correction: [object or puzzle]

Report a source problem

Use a source report when the linked page is unavailable, the citation no longer supports the displayed value, the referenced document has been superseded, or the qualifier does not make the source’s definition clear.

Include the puzzle, existing source if available, and a replacement source or archived official reference when possible. Do not copy and paste a long article, manual, or database record into the email. A link, document title, page number, and short explanation are normally enough.

A cited source does not sponsor or endorse Size It Up Party. The source supports the factual measurement, while the game’s wording, selection, scoring, and visual presentation are independent. If a source cannot be repaired or replaced with suitable evidence, the related puzzle may be withdrawn.

Suggested subject: Source issue: [object or puzzle]

Report a copyright, attribution, or permission concern

If you believe material on the site infringes your rights, uses an incorrect attribution, exceeds a license, or should be removed, provide enough information to identify the material and understand the concern.

Include:

We may ask for limited additional information reasonably necessary to review authority, ownership, license terms, or the specific use. Do not send unrelated sensitive documents. A credible concern may result in temporary withdrawal while the material is reviewed, followed by correction, replacement, removal, restoration, or an explanatory response.

For permission to reuse original Size It Up Party material, describe the exact material, intended audience, distribution channel, commercial or non-commercial context, and any planned modifications. Permission is not granted unless it is confirmed in writing. We cannot grant rights in third-party material owned by someone else.

Suggested subjects: Copyright concern, Attribution, or Permission request

Make a privacy request

You can play without an account. If you choose Google sign-in, Size It Up Party stores an internal user ID, Google identity details described in the Privacy Policy, session records, and eligible Daily leaderboard results. Most unfinished game progress and preferences remain in your browser and can be cleared through the game or browser settings. A support message itself contains the email address, name, content, and other details you choose to provide.

Depending on where you live and which laws apply, you may have rights to ask about information we control, request access or correction, request deletion, restrict or object to certain processing, or appeal a decision. Not every right applies to every situation, and an exception may allow or require some information to be retained.

State that the message is a privacy request and describe what you want us to review. We may need enough information to confirm that you are connected to the relevant message or record. We will not ask for unrelated identification merely because you submitted a request. If your request concerns browser-stored game data, clearing that data on the relevant browser may be the fastest available action because it normally remains on your device.

Suggested subject: Privacy request

Report a security concern

If you believe you found a security issue, avoid accessing data that is not yours, disrupting the service, or publicly sharing details that would create immediate risk. Describe the affected page or feature, the steps needed to observe the issue, the potential impact, and whether the concern can be reproduced without accessing another person’s information.

Do not send active malicious files, passwords, access tokens, or data obtained from other people. We do not offer a public bug-bounty program or promise a reward. A responsible report helps us evaluate the issue and choose an appropriate response.

Suggested subject: Security concern

What happens after you write

Your message is used to understand and respond to the request, investigate a correction or rights concern, protect the service, and maintain a reasonable record. Messages are generally kept for no more than 12 months unless a longer period is needed for an active request, dispute, security matter, permission record, or applicable obligation.

We do not publish your email address or message merely because you contacted us. A correction may result in a changed puzzle, qualifier, or source without publicly identifying the reporter. If you want a particular public credit, ask first; do not assume that a source correction automatically creates attribution.

The public email may use service providers for email delivery and forwarding. They process limited information needed to deliver the message. The destination mailbox and other operational account details are not public contact information and are not displayed on the site.

We do not promise an exact response time. Some questions can be answered quickly, while source comparisons, permission checks, security review, and rights-related messages may require more investigation. Sending repeated copies of the same message usually does not speed up that work.

Writing a useful report

A concise report can follow this structure:

  1. Page or puzzle: identify where the issue appears.
  2. Issue: explain what seems wrong or what you need.
  3. Expected result: describe the correction, answer, or action requested.
  4. Evidence: provide a reliable link or relevant definition when applicable.
  5. Reply details: include a working email address and any necessary context.

Keep each request focused. If one email contains unrelated gameplay, copyright, privacy, and security issues, use clear headings so each concern can be routed and reviewed correctly.

Frequently asked questions

Can I send a screenshot?

You may include a screenshot when it helps identify the visible issue, but remove unrelated personal information first. A source correction should also include a reliable source link and matching measurement definition. The current Contact page does not provide a website upload form.

Should I send my Daily score?

Only if it helps explain a scoring or result problem. For an ordinary measurement correction, the puzzle name, dimension, displayed value, and source are more useful than the total score.

Can support change my completed Daily result?

Support does not manually edit a local completed result. If a puzzle is invalid, it may be corrected or withdrawn for future play. Incompatible puzzle or rule versions are not merged into an old result.

Can I request a new object?

Yes. Include the object name, useful comparison dimension, and a reliable measurement source. A suggestion is not a promise of publication; it still needs source, puzzle-quality, and visual-asset review.

Is there another official support account?

The public support channel for V1 is support@sizeitupparty.com. Do not send passwords or verification codes to anyone claiming that they are required to resolve a game question.

Email support

Send your message to support@sizeitupparty.com. Choose a descriptive subject and include only the information needed for the request.