Occasionly Privacy Policy

Who we are and our role

Occasionly provides a reminder tool to online stores (“merchants”). Occasionly is operated by Adam Nagy (ABN 94 644 080 792), trading as Occasionly. When a customer saves an occasion using a store's Occasionly widget, the store decides to send them reminders and Occasionly sends those emails on the store's behalf. This policy covers the customers who use a widget, the merchants who use Occasionly, and people who visit or contact us through our website.

What we collect from customers

When a customer saves an occasion, we collect their name and email address and the names, dates and types of the occasions they choose to save. We also record whether they have unsubscribed, and whether an email to them has bounced or been reported as spam, so that we stop sending. We use this information only to send a confirmation email and reminder emails on behalf of that store. The store whose widget was used can see the name, email address and occasions saved with it, and whether the customer has unsubscribed.

What we collect from merchants and enquirers

When a store signs up we collect its login email address, store name, branding, sender and reply-to details, settings and plan. Payments for paid plans are handled by Stripe, and we do not store card numbers. If someone sends an enquiry through our website, we collect the name and email address they enter so that we can reply.

Email tracking and revenue reporting

Links in our reminder emails are tracked. When a link is clicked we record the click, the time and an anonymous token that identifies the reminder, so the store can see how its reminders perform. Clicks that look automated are filtered out. If a store adds the Occasionly tracking snippet to its website, then when a visitor arrives from a reminder link the snippet tells us about the visit, and keeps the anonymous token in the visitor's browser on the store's own website, in local storage or, if that is not available, in a cookie lasting up to 30 days. If that visitor places an order within 30 days, the snippet sends us the order's identifier, its subtotal, its currency and the token. It does not send the customer's name, email address, postal address or payment details, and nothing is sent for visitors who did not arrive from a reminder link. We use this only to show the store estimated sales. These figures are estimates and do not show that a reminder caused a sale.

Website analytics

Our public website pages (such as the home page, FAQ, documentation, sign-up and sign-in pages) use Google Analytics to count visits and see which pages are used. It sets cookies in the visitor's browser, named _ga and _ga_ followed by an ID, and sends Google the page address, the visitor's browser and device details and an approximate location worked out from their IP address. It is not used in the merchant dashboard or in the widget, so it does not see customers who use a widget or merchants who are signed in to their dashboard. We do not use it to identify individual visitors.

How we use it

We use collected data only to send confirmation and reminder emails, to provide merchants with click and estimated revenue reporting in their dashboard, to reply to enquiries, to understand how our website is used, and to keep the service secure and prevent abuse. We do not sell personal data, and we do not share or transfer it to anyone for marketing or advertising purposes.

Cookies and similar storage

Merchants are signed in to their dashboard using cookies. The sign-up page remembers the plan you picked in your browser, and the dashboard remembers the currency you choose to view revenue in, both on your own device only. The widget itself sets no cookies or browser storage. The private page where a customer changes or removes their saved dates sets no cookies or browser storage either, and loads nothing from third parties except the store's own logo. If a store uses our signup popup, a small script served from our website runs on the store's pages and asks our website for the store's popup settings when a page loads. After a visitor closes the popup or uses it, the script saves a short note in the visitor's browser on the store's own website, in local storage or, if that is blocked, in session storage, so that the popup does not keep appearing. It sets no cookies, and the note holds only the time the popup was closed and whether it was used, with no personal information. We also count how often the popup is shown, opened and used, without any visitor identifier. Our public website pages use Google Analytics, which sets the cookies described under website analytics above. Logos supplied by stores are loaded from the address the store provides. Like most services, our hosting provider's logs record technical details of requests, such as IP address and browser type.

Who processes it

We use service providers to run Occasionly: Supabase (database), Vercel (hosting), Resend (sending email), Stripe (merchant payments) and Google (analytics on our public website pages). They process data only to provide those services to us.

If a store connects its own email platform, we send that platform the customer's email address and, when the customer saves dates and when each reminder is due, the details the store needs to send the email: the customer's first name, the store's name, the name of the person the date is for, the kind and date of the occasion, a link to the store, and the customer's private link for changing or removing their saved dates. That platform handles the data under its own terms and privacy policy, and we do not control it. An unsubscribe made inside that platform is not passed back to Occasionly, so the store is responsible for honouring it. The private link is also in each email we send ourselves, but whether a store's own emails show it is up to the store.

Where it is stored

Our database is hosted in Seoul, South Korea, our servers run in Seoul, South Korea, and our email provider processes email in Tokyo, Japan, so personal information is stored and processed outside Australia. Our providers may also process it in other countries as part of operating their services.

Keeping and deleting data

Customer occasion data is kept for as long as the merchant's account is active. Cancelling a paid plan moves the account to the free Starter plan and does not delete data. A store can delete a customer at any time from its dashboard, which removes that customer's name, email address, saved occasions and unsubscribe record from our database. A customer can also change or remove their saved dates themselves. Every confirmation and reminder email we send has a link near the bottom, “You can change or remove your saved dates here”, which opens a private page for that customer and that store without signing in. Removing a date there deletes it from our database. Removing all of a customer's dates keeps their name and email address on file with its unsubscribe record. Emails already sent may remain in our email provider's records for a limited period. A customer can unsubscribe at any time using the link at the bottom of every email we send. To have personal information corrected or deleted, including having your details deleted entirely, or to have a store's account and all its customer records deleted, contact hello@occasionly.app. Customers may also ask the store directly.

Changes

We may update this policy. The date at the top shows when it was last changed.

Contact

For data requests or privacy questions, contact hello@occasionly.app