Privacy policy

2.1. Your account

• email address;
• password — stored only as a cryptographic hash, never in clear text;
• name;
• phone number (if you provide it);
• city (if you provide it, to fill in requests faster); for the same purpose, your date of birth, if you save it in your profile or type it in your first request (it is then saved in your profile to fill in the next ones; you can change or delete it in “Edit profile”).

If you sign in with “Continue with Google” or “Continue with Apple”, we receive your provider account identifier and, when supplied, your email address and name to create, find or link your Maps account. We do not receive your Google or Apple password. Apple may provide a private relay address instead of your real email. We store Apple authorizations encrypted so that we can revoke access when you delete your account; if Apple cannot revoke access at that moment, the account is retained so that you can retry deletion.

2.1.a. Data obtained when you sign in with Google

On the website and in the iOS and Android apps, “Continue with Google” requests only the openid, email and profile permissions. We read your Google account identifier, email address, whether Google has verified it and your name, when available. We do not access Gmail, Google Drive, your contacts or calendars; we do not receive your password or import your Google profile photo.

We use your Google identifier to recognise you, create or find your Cannasys Maps account and link it when appropriate. Your email and name become part of your profile and are used for the features you request: managing your account, sending service emails and completing requests or reviews. You can edit your name in your profile. Cannasys Connect membership discovery uses a hash of your email, as explained in section 5.2. We do not sell this data or use it for personalised advertising or to train artificial intelligence models.

We store your Google identifier linked to your account and your profile data in the Service database while your account exists. The identity token is used to verify sign-in; we do not store Google access or refresh tokens. Communications are encrypted over HTTPS and access to data is restricted through session and role controls. Storage and providers are described in sections 5 and 8.

Your Google identifier is not published or sent to clubs. Profile data may be processed by our hosting and email providers to deliver the Service and by authorised staff for support and security. A club receives the name and email you include when you send it a request; the visible author name on a review is public. Other recipients and disclosures to authorities are detailed in section 5.

You can delete your account from Profile → Settings → Delete account in the app, from your personal area on the website or request deletion at info@cannasys.co. Once deletion completes, your Google account link and profile are deleted. Requests already sent and published reviews may retain their data as described in section 4; you can also request their erasure as explained in section 7. Removing Cannasys Maps access in your Google account settings does not by itself delete your Maps account.

2.2. Membership requests to clubs

• name, phone and email address (by default, your account email; you can give another one you would rather the club wrote to);
• date of birth — we process it solely and exclusively to check that you meet the minimum age: 18, or the club's own minimum if higher (e.g. 21) and, only if you tick the pre-registration box, to disclose it to the club (section 2.12). We do not use it for any other purpose or to build profiles;
• the message or comment attached to your request.

Requests can only be sent from a registered account. The data in your request is disclosed to the club you choose, so that it can contact you and assess the request under its own statutes. From that point on, that club is the controller of that data on its own account. Remember: membership is decided by each club. If the club is connected to Cannasys, you can also ask to pre-register (section 2.12). If you are already a member of other clubs linked in “My clubs”, you can tick the optional box “Show the club which other clubs I'm already a member of” (unticked by default): only then do we add the names of those clubs to the request, and only the club you send it to can see them.

2.3. Favourites

The list of clubs you save to favourites (the “account — club” relationship and the date you added it). The club does not know who saved it: it only sees how many people have it in their favourites, in total. Each saved club has a “Club notifications” switch, turned on by default when you save it (unless you have reported an invitation from that club); you can turn it off at any time. We store its state and the date you last turned it on or off. While it is on, the club — if it can send invitations — sees a pseudonymous entry (“User · saved on …”, with the day you saved the club, without your name, email or phone) to which it can send a single short invitation (section 2.15). Your name and date of birth only reach the club if you reply to that invitation. If you turn it off or remove the club from your favourites, the club no longer sees that entry and can no longer send you invitations.

2.4. Reviews

• the author's display name (fixed at the moment the review is published);
• the text of the review and the rating.

Reviews are public: anyone visiting the Service can read them, and search engines can index them. Bear this in mind before writing something that identifies you. When writing a review you can choose to publish it anonymously (and change this later in “My reviews”): then your name is shown neither on the Service nor in the club's panel, only “Anonymous member”; the name stays stored with the review and only our moderation team can see it. You can add an optional profile photo: an approved photo is public and can appear beside your non-anonymous reviews. Anonymous reviews never show your photo. You can replace or remove it in your profile; we delete the previous photo and delete your photos when you delete your account.

2.5. Data of club representatives (B2B)

• club data: name, description, phone, website, email address, address, amenities;
• documents provided for the “Documents verified” check: the association's statutes and its entry in the relevant register of associations;
• when claiming your club (linking an existing listing): first and last name, stated role and, if you wish to provide it, a supporting document;
• when applying to add a new club: name, email address and contact phone of the applicant.
• the content the club publishes in the Service (listing texts and photos, events, notices to members and invitations), the account of the team member who submits it and the history of its review before publication (section 2.16).

2.6. Support

• the subject and text of your enquiry;
• attached files (if any);
• the reference to the request your enquiry relates to.

2.7. Notifications

• your notification inbox inside the Service (subject, text, read status);
• the browser push subscription data (endpoint and technical encryption keys) — only if you enable push notifications.

2.8. Search history

If you have an account, your search history is stored in our database. If you browse as a guest, it is stored only on your device (localStorage) and is not sent to our servers. The text of an individual search may be transmitted to the assistant's technology provider in order to interpret it, only in the cases described in section 5; your history does not leave the Service.

2.9. AI assistant

The text of the messages you write to the assistant and the conversation identifier. We process it only to generate the reply; the message is transmitted to the assistant's technology provider (section 5). Avoid writing personal data in the chat that is not needed.

2.10. Technical data

• IP address and HTTP request data — recorded in the server logs and in the systems that protect against abuse (request rate limiting);
• cookies and browser storage — see the Cookie policy.

2.11. Cannasys Maps mobile app

The Cannasys Maps app for iOS and Android shows the same directory as the website and is published by the same controller (section 1). You do not need an account to browse the catalogue, the map or club pages. The app contains no advertising, includes no analytics or tracking tools of its own, and does not let you buy or pay for anything. If you use the app, we process:

• your account: email address and, if you add them, your name, phone number and city (the same as on the website, section 2.1). If you are signed in, have entered your city and do not share your location, the app uses that city to show you its clubs first in the catalogue and on the map;
• your membership requests: the form data (name, phone, email, date of birth and comments) and your confirmation that you meet the minimum age (18, or the club's own minimum if higher); the server rejects the request if the date of birth does not belong to an adult or is below the club's minimum age. The club you choose receives them (section 2.2). If the club is connected to Cannasys, the form also includes the optional pre-registration box (section 2.12), and in “My clubs” you can see whether your pre-registration is pending verification at the club;
• the messages you exchange with the club about your request. If you block a club’s chat, we stop sending you notifications about that chat;
• your reviews, your favourite clubs and your support requests, including content reports (“Report”), just as on the website (sections 2.3, 2.4 and 2.6);
• your event sign-ups (“My events”), the notices from clubs whose card you have linked, the invitations you receive and the “Club notifications” switch of each favourite, just as on the website (sections 2.3, 2.13, 2.14 and 2.15). In the app you can turn off a club's notifications (on its card and in your favourites), turn off the “Notices from my clubs”, “Invitations from clubs” and “My events” groups in Settings, and report a notice or an invitation;
• if your account belongs to a club (owner or manager), the “Requests” tab shows the membership requests your club receives — with the data each applicant sent — and their chat, and the app notifies you by push of new requests, messages, cancellations and unanswered-request reminders. This is the same data you see in the club panel on the website; nothing is bought or subscribed to in the app;
• push notifications, only if you turn them on: your device’s notification identifier, the platform (iOS or Android), the language of the notifications, the app version and whether you want the content shown on the lock screen. It is linked to your session and is deleted when you sign out, change your password, when the session expires, when you delete your account or when the system reports that the app is no longer installed. The text of each notification is kept in the sending queue for at most 7 days after delivery (30 days if it could not be delivered). By default, notifications do not show the club name or the message text;
• your approximate location, only if you have given the app location permission (we do not ask for it when the app opens: the “Near me” button does). On your device it is used to centre the map. In addition, rounded to about 1 km, it is sent to our server with each catalogue, map and events-list request, solely to order the clubs by your city and how close they are and, in the events list, to show only events of clubs within about 50 km, nearest first. We do not store it and we do not write it to the technical logs (it is replaced by a marker). You can withdraw the permission in your phone settings; without it, the order does not use your location and the events list shows events across Spain;
• the age confirmation shown on first launch, which is stored only on your device;
• technical access logs: our server records each request (method, requested address — without your approximate location —, result) with the originating network — not the full IP address: the last part is zeroed — and a technical pseudonym, without linking them to your account. The text you type in the catalogue search is used to show you results and, without linking it to your account, for aggregated search statistics;
• the messages you write to the AI assistant (paw button in “Clubs” and “Map”) and the history of that conversation: they are sent without linking them to your account, only to generate the answer, and are passed to the assistant's technology provider, which acts on our behalf (section 2.9 and section 5). The conversation is not stored on your device. Avoid writing personal data in the chat that is not needed;
• on Android, the map is provided by the Google Maps SDK, which collects technical data on its own (device model, errors, IP address and an SDK identifier) under Google’s privacy policy. On iOS the map is Apple Maps, built into the system.

Please note that applying to join a cannabis association may reveal sensitive information about you; that is why notifications do not show the club name on the lock screen unless you turn it on in Profile → Settings. We process app data for the same purposes, on the same legal bases and for the same periods as website data (sections 3 and 4).

You can delete your account from the app itself (Profile → Settings → Delete account) or from the website; the account is deleted on our server together with your devices’ notification identifiers. The app publisher’s details are in the Legal notice.

2.12. Pre-registration with clubs connected to Cannasys

Some clubs manage their members with Cannasys (cannasys.app), a system that QUASAR SMART TECHNOLOGIES, S.L. provides to those clubs as a processor: members' data is the responsibility of each club, and QUASAR only processes it on the club's instructions and does not use it for Cannasys Maps beyond what this policy describes.

When you send a request to one of those clubs you can tick “I want to pre-register with this club”. Only if you tick it and the club approves your request do we disclose to that club your first and last name, date of birth, email address and phone number, so it can prepare your record and recognise you when you visit; we do not send your messages, who recommended you or any other data. The legal basis is your consent (Art. 6(1)(a) GDPR): it is optional, does not affect your request and can be withdrawn at any time from the request or from “My clubs”, without affecting the lawfulness of earlier processing. If you withdraw before approval nothing is sent; if you withdraw afterwards, the pre-registration is deleted from the club's system.

From disclosure onwards the club is the controller of that data and will inform you how it processes it. The club, through Cannasys, emails you a personal QR code to identify yourself at its premises; the code contains no personal data (only a random identifier); you can also show it from your card in Cannasys Maps (“Show QR”), where we store it encrypted and only you can see it (section 5.2), and it stops working if the pre-registration expires, you withdraw it or the club rejects it. When the club checks your identity and age in person and decides to admit you, it sends you your membership card (in Apple or Google Wallet, or a new code by email) and the pre-registration code is no longer valid. Pre-registration does not make you a member. If you do not complete verification within 30 days of the visit date you gave (or of the approval, if you gave none or it had already passed), the club deletes the pre-registration.

To be able to prove your consent we keep a minimal record (your account, the club, the version of this text and the dates you gave or withdrew consent and the data was sent) while the pre-registration or link exists and for three years afterwards. You can exercise your rights as described in section 7 — with us or with the club — and complain to the Spanish Data Protection Agency (aepd.es).

2.13. Club events

Some clubs let you sign up for their events from their listing, on the website or in the app. If you sign up, we store your sign-up: the event, your account, its status (signed up, place held or cancelled), the dates and whether we have already sent you the reminder. In its panel the club sees your name (the one on your account or, if you have not provided one, the one on your request), the status of your sign-up and the date you signed up.

If you are a member of the club — you have its card linked in “My clubs” — you sign up directly. If you are not and the event is open to everyone, the sign-up goes together with a membership request to that club, with the same data as any other request (section 2.2), and your place is held until the club decides on it; if you already had an open request with that club, that one is used. We let you know if the event changes date or is cancelled, and we send you a reminder about 24 hours before. You can cancel your sign-up in “My events”; your request to the club, if any, stays open.

2.14. Notices from your clubs

Clubs connected to Cannasys can send short notices (a title, a text and, if they wish, a link to one of their events) to their members who have their card linked in “My clubs”. If you have a club's card linked, by default you receive its notices in your notification inbox and, if you have push notifications turned on, also as a notification; you also see them on that club's card, in “My clubs”. To know who a notice reaches we use the card link that already exists (section 5.2).

Notice notifications are on by default. You can turn them off for a particular club with the “Club notifications” switch on its card — you will still see its notices there — or all of them with the “Notices from my clubs” setting; we store that choice. If you report a notice (“Report”), we store the report (your account, the notice, the date and the reason, if you give one) so that our team can review it. The club only sees how many members each notice reaches: it does not know who has read it, who has turned notifications off or who has reported it.

2.15. Invitations from clubs

If you have “Club notifications” on for a club saved in your favourites (section 2.3; they are on by default), that club can send you a single invitation: a short text that we review before it is sent (section 2.16). It reaches your notification inbox, “Invitations” in your account and, if you have push notifications turned on, arrives as a notification. We store the invitation, its status and its dates. You can reply to it for 30 days from when it arrives; after that it expires and can no longer be answered.

If you reply, a request to that club is opened with the name (by default, the one on your account) and date of birth you write in the reply and with your message: this is the same data as in a request, without phone or email, and the conversation continues in “My requests”. Only then does the club learn who you are. As with any request, the date of birth is used to check the club's minimum age (section 2.2). If you decline it (“No, thanks”), the club is not told: for the club the invitation remains “sent” and, after 30 days, shows as “expired”. If you report it (“Report”), we store the report (your account, the invitation, the date and the reason, if you give one) so that our team can review it, that club can no longer send you invitations and its “Club notifications” are turned off in your favourites (also if you save it again, until you turn them on yourself); the club does not learn that you reported it either. You can turn off invitation notifications with the “Invitations from clubs” setting.

2.16. Automated review of content and profile photos

Before it goes live, everything a club wants to publish in the Service — the texts of its listing, its logo and gallery photos, the descriptions of its amenities, its events (text and cover image), its notices to members and the text of its invitations — goes through an automated review with artificial intelligence that checks it complies with the publishing rules: no prices, discounts or promotions, no invitations to consume and no product images, no references to minors, insults, third parties' personal data or spam. To do this we send that content (text and images) to the technology provider of the AI assistant, which acts on our behalf (section 5 and section 6.1). For club content review, we do not send data about users — neither about those who visit the listing nor about those who receive the notice or the invitation — nor the name or account of the person who publishes it. An optional profile photo is also sent as an image to OpenAI to check for sexual content, violence, minors, hate, third parties’ personal data, spam and product or consumption images. We remove image metadata before the review. We do not send the account name, email or identifier with the image and do not perform identity recognition. The image stays private until approval, and our team can resolve the review manually.

The outcome can be: it is published; it is rejected with a short reason, which the club sees and can correct; or it stays “Under review” if the automated review is not available at that moment: it is then not published until the system repeats the review or a member of our team resolves it. Our team can approve or reject any content manually, including content already rejected, and the club can ask us to review a rejection by writing to support. While a change is under review or has been rejected, the previous version stays published. We store the reviewed content, the decision, its reason and its date as the moderation history. The review decides which content is published; it does not decide whether someone can join a club.

2.17. Cannasys App demo requests

If you request a Cannasys App demo from the website (“Request a demo” form), we store your name, phone, email, the club, the member-count range, your preferred time, your message, the page you requested it from and the moment you gave your consent, and we send it by email to our sales team so that we can contact you about Cannasys App. The legal basis is your consent (art. 6.1.a GDPR), which you can withdraw at any time by writing to us; we keep the request for as long as it is needed to handle it or until you ask us to delete it. The Cannasys Maps app does not show this form.