R RenderComp
← RenderComp

Privacy Policy

Last updated: 2026-11-08 · Operated by Trimora Inc.

1. Controller

RenderComp is operated by Trimora Inc. (Trimora株式会社), represented by Hiromi Ishino. For privacy inquiries, use the support page at rendercomp.com/support or email [email protected].

2. Data We Collect

  • Purchase data: Email address, payment information (processed by Stripe — we do not store card numbers), purchase amount and date.
  • Email you give us outside a purchase: If you enter your email address to watch the free masterclass, to join the RenderComp update list, to receive the free 50-template ZIP, or to join the RenderComp Academy early list, we store that address on our own Cloudflare D1 database. We use it to send you the confirmation email and news about the product. We do not sell it or share it with anyone outside the processors listed in section 4. You can unsubscribe with the one-click link in any of those emails, by replying to them, or by contacting us at the address in section 1.
  • License data: License keys and download tokens issued for your purchase, stored in Cloudflare D1.
  • Delivery records: When a valid download link for your order is used — exchanging the link after payment, opening the download page, or downloading the template ZIP — we record one entry on our own Cloudflare Worker, stored in Cloudflare D1. Each entry contains your order ID, which of those three steps it was, the date and time, the IP address of the connection, your browser's user-agent string (the first 512 characters), the approximate location and network that Cloudflare derives from that IP address (country, region, city, postal code, network number (ASN) and the network operator's name), and, for the ZIP download, the amount of data sent. Requests that do not match a valid order are not recorded. Delivery records do not contain the visit identifier described below.
    Why: to prevent fraudulent use of purchases and to show that a purchased product was delivered if a card payment is disputed (for example, a chargeback claiming the purchase was not made or not received). This is our legitimate interest (GDPR Article 6(1)(f)).
    How long: deleted automatically 18 months after the purchase date. Card networks allow a cardholder to dispute a payment for up to 540 days, and 18 months covers that period.
    Who receives them: no one in the normal course. If a payment for your order is disputed, or if we investigate suspected fraud on it, we include the delivery records for that order in the evidence we submit to Stripe, which passes it to the card network and the card issuer. We do not sell them or use them for marketing.
  • Usage analytics: Aggregated, anonymized page view data via Cloudflare Web Analytics (no cookies, no cross-site tracking).
  • First-party visit data: A random identifier for your visit, the page events it produced (for example, opening the download page), the path of the page each event happened on (for example /blog/ — the path only, never the query string or the full address), the hostname of the site that sent you here, and any campaign or referral tag that was in the link you clicked. This is recorded on our own Cloudflare Worker. It does not contain your name, your email address, or your IP address. If you buy, the visit identifier is stored with your order so that we can see which pages led to the purchase. See section 7 for exactly what is stored in your browser and how to remove it.

3. How We Use Your Data

  • To fulfill your purchase (contract performance): providing the download link and license key, issuing receipts.
  • To communicate about product updates relevant to your purchase (legitimate interest).
  • To send the confirmation email and product news to people who entered their email address for the free masterclass, the update list, the free 50-template ZIP, or the Academy early list (consent — withdrawn with the one-click unsubscribe link or by replying).
  • To prevent fraudulent use of purchases and to respond to card payment disputes, using delivery records (legitimate interest — see section 2).
  • To comply with legal obligations (tax records, etc.).

4. Third-Party Processors

  • Stripe — payment processing and merchant of record (acts as an independent controller for payment data; Stripe's privacy policy applies). If a payment is disputed, we give Stripe the delivery records for that order as evidence, and Stripe passes them to the card network and the card issuer.
  • Cloudflare — website infrastructure and template download delivery. Cloudflare processes the IP address of every request in order to deliver the site, and provides the approximate location and network of the connection that we store in delivery records (section 2).
  • Resend — transactional email delivery (purchase confirmation, product updates) and our internal notification emails, including the notice we receive when a payment is disputed, which contains the delivery records for that order.

5. Data Retention

Purchase records are retained for 7 years as required by Japanese tax law. You may request deletion of any data not subject to legal retention via the support page at rendercomp.com/support or by email to [email protected].

Email addresses given outside a purchase (free masterclass, update list, free 50-template ZIP, Academy early list) are kept until you unsubscribe or ask us to remove them. After you unsubscribe, we keep a record of the unsubscribed address and the date so that we do not email you again.

First-party visit data (section 7) contains no name, email address, or IP address; if you buy, the visit identifier is stored with your order. This statement is about visit data only; it does not apply to delivery records, which do contain an IP address and are described in section 2.

Delivery records (section 2) are deleted automatically 18 months after the purchase date. If a payment is disputed, the delivery records for that order are also part of the evidence we submit to Stripe and of our internal notice of the dispute, and those copies are kept with the records of that dispute. Copies held by Stripe, the card network, and the card issuer are handled under their own policies.

6. Your Rights (GDPR)

If you are located in the EU/EEA, you have the right to access, rectify, erase, restrict processing of, and port your personal data. You also have the right to object to processing and to lodge a complaint with your national supervisory authority. To exercise these rights, contact us via the support page at rendercomp.com/support or by email to [email protected].

Where we rely on legitimate interest, including for delivery records, you may object at any time on grounds relating to your particular situation. We will then stop that processing unless we have compelling legitimate grounds for it, or need it to establish, exercise, or defend legal claims — for example, to respond to a dispute about your payment.

7. Cookies and Browser Storage

RenderComp does not use tracking cookies, advertising networks, or cross-site tracking of any kind. Cloudflare Web Analytics uses privacy-preserving, cookieless measurement. Stripe may set functional cookies during the checkout process.

We store four small entries in your browser's own storage. None is a cookie, none is ever sent to any other website, and all are readable only by rendercomp.com:

  • rc_visit in sessionStorage — a random 32-character identifier for the current visit, so that the pages you view can be counted as one visit instead of several. It is cleared as soon as you close the tab.
  • rc_ft in sessionStorage — where this visit arrived from: a category such as "organic-search", the referring site's domain such as "google.com", and the path of the first page you opened. It contains no personal data and is cleared as soon as you close the tab.
  • rc_rd in sessionStorage — on blog articles and the main product pages, which quarter-marks of the page (25/50/75/100%) you have already scrolled past, so that each is counted once. It is cleared as soon as you close the tab.
  • rendercomp-seminar-unlocked in localStorage — the single character 1, written after you enter your email address to watch the free masterclass. It records that the video is unlocked on this browser, so that you are not asked for your email again the next time you want to watch it. It contains no email address and no identifier. It has no expiry date and stays until you clear it.

Why we do this: so that several page views in the same visit are counted as one visit rather than several, and so that the masterclass video reopens without a second email entry. Where you arrived from is worked out on the first page of your visit and kept in rc_ft for the rest of that visit, so that it is not lost when you move between pages; it is sent to our own server with your visit identifier. On blog articles and the main product pages (home, templates, free) we also send how far down the page you scrolled (in quarters) and, when you leave, how many seconds the page was visible, rounded to 5 seconds, so that we can tell whether pages are actually read. Both are tied to the visit identifier only, never to your name or email, and none of this survives after you close the tab.

What we never put in them: your name, your email address, your IP address, or anything you type into the site. We do not use them to follow you across other websites, and we do not sell or share them. This applies to these browser storage entries and to the visit data they produce. It does not apply to delivery records: when a purchased template is delivered, our server records the IP address of the connection, as described in section 2.

How to remove them: closing the tab is enough to clear rc_visit, rc_ft and rc_rd. rendercomp-seminar-unlocked stays until you clear this site's data — in most browsers, site settings for rendercomp.com then "Delete data" or "Clear cookies and site data"; that removes both entries at once. If your browser blocks this storage, the site still works normally: you can browse, buy, and download exactly as before, and the masterclass will simply ask for your email each time.