Put simply, all sales are final. Refunds are available only in the following circumstances:
- You’ve bought a ticket for an event that was cancelled.
- You’re unable to attend an event for which you bought a ticket. In this case refund requests must be submitted by midnight (Amsterdam time) 24 hours before the event. The refund will be for 75% of the original amount paid.
Contact JackNewhorse on Telegram with the name used to purchase the ticket. Specify how many tickets you bought, and which should be refunded.
Event tickets may be transferred to another person by emailing firstname.lastname@example.org at least 48 hours before the event starts. Include the following information for both the transferor and transferee:
- Name on ID
- Email address
- Furry name
- Telegram name
To prevent scalping, only one ticket may be transferred by transferor. Payment is solely handled between the two parties, with no involvement by Otterdam.
Who we are
This website’s address is https://store.otterdance.club. It’s the e-commerce site for Otterdam and Otterdance.
Primary contact is Tom Geller (aka “Jack Newhorse”), JackNewhorse on Telegram. Otterdance and Otterdam are registered business names of Tom Geller Productions (KvK 66951453).
personal data we collect
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Any information you send via a contact form on this site will be sent to the site’s administrator. That’s, uh, kind of the point.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the same way as if the visitor has visited the other website.
We use Jetpack (a product of Automattic) for analytics.
Who we share your data with
If you visit the site without signing into it, we will not intentionally share any data. But regardless of whether you sign in, WordPress and its supporting pieces (such as plugins) might send information to third-party providers, such as Google (for use of Google Maps, for example). To the best of our knowledge, nobody can personally identify you via these data without taking extreme measures.
If you create an account, we may share your information within the organisation, but will not share it with any outside organisations.
How long we retain your data
For users that register on our website, we store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information. We have no plans to destroy such information after a specific period of time, but reserve the right to do so.
What rights you have over your data
If you have an account on this site, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Nowhere except as described above.
How we protect your data
This site is hosted on third-party servers, using a shared hosting space. As a result, any assurances we could offer regarding your privacy are pretty moot, as we can’t control the behaviour of these third parties. Having said that: Our own backups are stored on a hard drive in a locked apartment.
What data breach procedures we have in place
None beyond complaining a lot. But we’ll do our best to ameliorate any effects.
What third parties we receive data from
Google, e.g. for Google Maps. Mixcloud, Soundcloud, and DailyMotion for DJ files. Possibly other web services.
What automated decision making and/or profiling we do with user data
Industry regulatory disclosure requirements