- Terms and Conditions
- Who we are
Terms and Conditions
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 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 24 hours before the event starts.
First, the transferor (seller) sends the following information for both themselves and the transferee (buyer):
- Name on payment method
- Email address
- Furry name
- Telegram name
- We then refund the ticket and create a voucher that lets the transferee get a new ticket.
- We wait until the transferor confirms that they have received payment.
- We then give the transferee access to the voucher we created.
- The transferee can then exchange that voucher for a ticket.
To prevent scalping, only one ticket may be transferred by transferor.
Who we are
Our website address is: http://otterdance.club.
What personal data we collect and why we collect it
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 exact same way as if the visitor has visited the other website.
We sometimes 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 our use of Google Maps). 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. This makes any assurances we could offer regarding your privacy are pretty moot. 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 for DJ files. Possibly other web services.
What automated decision making and/or profiling we do with user data
Industry regulatory disclosure requirements