CloseItUp
DoorDash, Uber Eats & Grubhub payout reports → QuickBooks Online (or Xero) journal. Files stay in your browser.
Converter Pricing Terms Privacy Refunds

Privacy Policy

Last updated: 17 November 2026 (Asia/Taipei). This is a draft for Creem account review. Replace the highlighted placeholders before you submit the store for live payments. This is not legal advice.

This policy describes how Zhou Weifu (“we”, “us”) handles information when you use CloseItUp at closeitup.com.

1. Payout files stay in your browser

Your DoorDash, Uber Eats or Grubhub payout or financial-report CSVs are processed locally in your web browser. The file is not uploaded to our servers. We do not receive, store, or have access to the contents of that file — including store names, order identifiers, or amounts.

If you pay to unlock a specific upload, the browser sends only a SHA-256 hash (of the file text, or for several files a hash of their sorted per-file hashes) and the file name(s), so we can bind a $9 unlock to that upload. A hash cannot be reversed into the original report. Conversion and download still happen on your device.

2. Information we collect

Depending on how you use the Service, we may process:

  • An email address you choose to enter at checkout, so Creem can send a receipt.
  • Payment and billing details, processed by Creem as merchant of record. We do not store full payment-card numbers. Creem’s processing is described in Creem’s own privacy documentation.
  • Unlock tokens, license keys, checkout and customer identifiers, and subscription status, stored so we can honor a purchase and handle refunds.
  • Basic server logs (for example IP address, time, and URL) from our hosting provider, used to operate and secure the site.
  • Information you send to [email protected] if you contact support.

The free monthly allowance is remembered in your browser (local storage). We do not use that local flag to identify you across devices.

3. How we use information

We use the information above to provide the converter, process payments, issue and validate unlocks, prevent abuse, respond to support requests, comply with law, and improve the Service. We do not sell your personal information.

4. Processors and international transfers

Payments, tax collection, and payouts are handled by Creem. The website and billing worker may be hosted on Cloudflare. These providers may process data outside your country. If you pay, Creem is also an independent controller or processor for payment data under its terms.

5. Retention

Unlock records are kept for as long as needed to provide access and handle refunds, disputes, or legal obligations, then deleted or anonymized. Browser local storage can be cleared by you at any time. Support emails are kept only as long as needed to resolve your request.

6. Your choices

You can use the free preview without paying and without creating an account. You may request access, correction, or deletion of personal information we hold by emailing [email protected]. You can also cancel a subscription in the Creem Customer Portal.

7. Cookies

The Service uses local storage for unlock tokens and the monthly free-download flag. We do not currently use advertising cookies. Our host or payment provider may set cookies that are strictly necessary for checkout or security.

8. Children

The Service is intended for business users and is not directed at children under 16 (or the age of digital consent in your country).

9. Changes and contact

We may update this policy. The “Last updated” date will change when we do. Privacy questions: [email protected].

Pricing Terms of Service Privacy Policy Refund Policy

Support: [email protected]. Operator: Zhou Weifu. Website: closeitup.com.

CloseItUp is not affiliated with DoorDash or Intuit. It is not tax, accounting, or legal advice — especially around marketplace-facilitator sales tax and tip treatment, which vary by jurisdiction. You are responsible for reviewing every journal entry before you import it into QuickBooks. Column mapping is based on official published field names and must be confirmed against a real merchant CSV before you rely on it.