Skip to content

Privacy

Draft for review. This is not a finished privacy policy.

PrintyCal (https://printycal.com) is published from Euless, Texas. The site lets you preview, print, and download calendars. There is no account yet.

What we store

A cookie named ml_uid gives the browser an id. A signed cookie named ml_access lists the calendars that browser has unlocked. The server keeps the same unlocks, plus a count of free prints, next to that id and a coarse IP address. That IP check is there so clearing cookies does not reset the four free prints. It can also affect another person on the same network.

The browser copy of the free-print count is only for the little “free left” label. The server count is the one that matters.

Turning on owner mode sets a separate signed cookie named ml_owner on that browser. It does not add a free-print count. Failed passphrase tries are counted by IP for 15 minutes so the passphrase cannot be guessed in a loop. The passphrase itself is not stored.

Payments

Paid downloads go through Square checkout. PrintyCal does not see your card number. Square hosts the payment page. Sales tax is a configured percentage, not calculated from your address. In demo mode, nothing is sent to Square and nothing is charged. A Square webhook, or a check of the order when you return, records that the payment completed. Stripe is only used if the site is switched back to it.

Ads

Pages reserve space for advertising. If an AdSense client id is configured, Google may set its own cookies. Ads are not part of the print view or the JPEG.

The advertise form

The advertise form stores the name, email, business, product, placement, and budget you send, so PrintyCal can reply. It does not send that note as email by itself.

Contact

Privacy questions can go through the advertise form. The note is stored for a reply. It is not emailed automatically.