Vulcan/ Docs/ Privacy Policy

Privacy Policy

Last updated: October 14, 2026

Vulcan is a Discord bot, dashboard and set of tools for running token-gated communities, operated by Premint, Inc. ("we," "us," or "our"). This Privacy Policy explains what personal information we collect through Vulcan (the "Service"), how we use and share it, and the choices you have. It is part of the Terms of Use.

Two kinds of people use Vulcan. A Member is someone who verifies with, or has a role managed by, Vulcan in a Discord server. A Server Owner is someone who adds Vulcan to a server or administers it. Most of this policy applies to both; where it doesn't, it says so.

The short version

  • You sign in with Discord. When you click Verify in a server, Vulcan checks every wallet linked to your Vulcan account against that server's rules and gives you the roles you qualify for. Vulcan keeps re-checking, and removes a role when you stop qualifying.
  • By clicking Verify you direct Vulcan to share information about your wallets and holdings with that server and its administrators. You can disconnect from a server from your account page.
  • Wallet addresses and what they hold are public blockchain data. We can't make them private or delete them from a blockchain.
  • We do not sell your personal information, and we do not use advertising or analytics trackers on the Service.

1. Information we collect

From Discord. When you sign in, Discord gives us your Discord user ID, username, display name and avatar, your email address if you share it, and the list of servers you are in. We store the access and refresh tokens Discord issues so we can keep you signed in and check which servers you administer when you open the dashboard. Role changes are made by the Vulcan bot, not with your token.

In servers where Vulcan is installed, the bot reads messages in channels it can see so that it can respond to commands. We store message content only where a feature keeps it: support tickets, messages a community highlights, and posts the bot itself makes. We also keep each member's roles, join date, boost status and membership-screening status. If you are in a server where Vulcan is installed but have never used it, we still receive and keep your Discord ID, username, avatar and roles in that server from Discord, so the server's administrators can see their member list and so Vulcan can manage roles there.

Wallets. The wallet addresses you link to your Vulcan account. If you have already linked wallets in another service we operate, such as PREMINT, Vulcan may import them. Vulcan also looks up wallets that other wallets have delegated to (for example through delegate.cash) and ENS names. Wallet addresses are public blockchain data.

Holdings. What your linked wallets hold on public blockchains, such as tokens, quantities and token traits, which we read from the blockchain and from data providers.

Server and verification records. Which servers you are connected to, your roles in them, when you joined or left, and a history of verification activity: the roles added or removed, the tokens that qualified, and the wallets involved. If you appear in a server's member directory, enter a giveaway, open a support ticket, or use onboarding or captcha, we keep what those features need, such as your entry, your ticket and the result.

Accounts you link. If you link an X (Twitter) account, we receive your handle, ID and display name and store the access and refresh tokens. If a server uses avatar verification, we compare your profile picture with the images of NFTs you hold.

Billing (Server Owners). Payments are handled by Stripe, which collects your payment details and billing address directly. We receive your email address, a Stripe customer ID, the plan and payment status. We never see your full card number.

Technical information. IP address, browser and device details (user agent), the page you came from, session identifiers, and logs of requests to the Service. When a wallet is linked or unlinked we record the time, the wallet, your Discord ID, and your IP address, user agent, referrer and session, to investigate fraud and abuse. We configure error monitoring not to collect IP addresses, cookies or account details by default; an error report may still contain data involved in the failing request, such as an email address.

Communications. What you send us when you contact support or answer a survey, your email preferences, and whether you have opted out of our emails.

Cookies. We set a session cookie and a security (CSRF) cookie. We do not use advertising cookies or third-party analytics. Pages that embed a video from YouTube, Loom or Vimeo may let those services set their own cookies. Emails we send may record whether they were opened.

2. How we use it

Purpose Examples Legal basis (EU/UK)
Provide the Service Sign you in, check your wallets against rules, grant and remove roles, run giveaways and tickets, bill Server Owners Contract
Keep it secure Detect fraud, duplicate or stolen wallets, abuse and attacks; investigate wallet link history Legitimate interests
Improve it Fix bugs, measure reliability, build features, use de-identified or aggregated data Legitimate interests
Communicate Service and billing messages, security notices, changes to our terms, support replies Contract; legitimate interests
Marketing Product news, only where you have not opted out or where the law requires your consent Consent or legitimate interests
Comply with the law Respond to lawful requests, enforce our terms, keep records Legal obligation; legitimate interests

3. How we share it

With the servers you verify in, at your direction. When you click Verify in a server you direct Vulcan to share information about your wallets and holdings with that server. The server's administrators, and the moderators and staff they authorize, can then see the wallets that qualified for that server's rules, the holdings and roles that go with them, and your verification history there. They see it in the dashboard, through bot commands, in exports and the API where the server's plan includes them, and in messages the server chooses to post. A server may use this information to run its community, including to grant and manage roles, moderate, support members, and run giveaways and distributions to members. Disconnecting from a server stops further checks and sharing with it. If a server connects Vulcan's ticket feature to its own Zendesk account, your support ticket is sent there.

PREMINT. Premint, Inc. also operates PREMINT (premint.xyz). Wallets linked to your Vulcan account are shared with PREMINT when you use PREMINT with the same Discord account, and wallets you proved on PREMINT are imported into Vulcan.

Apps you authorize. If you use Login with Vulcan to sign in to another application, we send that application the wallets you select on the consent screen. The application's own policy governs what it does with them.

Custom Webhooks. If a server uses a Custom Webhook rule, Vulcan sends that server's endpoint the wallets needed to evaluate the rule, which can include other wallets linked to your Vulcan account, when you click Verify, use the status command, or during scheduled re-checks. The endpoint belongs to the server owner or a party the owner chooses.

Servers decide how they handle what they receive. Each server is responsible for its own use of the information it receives. Each server is a separate controller of what it receives. Our Terms require Server Owners to use it only to run their community and not to sell it or use it to harass or target members, but we do not control what a server does and this policy does not govern it. Ask the server about its practices.

Public by nature. Your roles are visible to people in the server. Wallet addresses, and the tokens they hold and trade, are public on the blockchain, and sales feeds show the buyer's and seller's wallet addresses or ENS names in Discord and, if the server connects an X account, on X.

Service providers. We use providers to run the Service, who may process your information only on our instructions: hosting and storage (Render, Amazon Web Services and Cloudflare), payments (Stripe), email delivery (Cloudflare), error monitoring (Sentry), blockchain and marketplace data (Alchemy, OpenSea, Etherscan, delegate.cash and ENS), which receive wallet addresses to look up what they hold, X (when you link an X account or a server connects one), and content delivery networks and image hosts that serve pages and NFT images, which receive your IP address. Discord itself receives the information you give it when you use Vulcan in Discord.

Affiliates and advisors. With Premint, Inc.'s affiliates where needed to run the Service, and with our lawyers, accountants and similar advisors.

Business transfers. If we are involved in a merger, acquisition, financing, reorganization, bankruptcy or sale of assets, your information may be shared with the other parties and transferred as part of it.

Legal reasons. We do not volunteer your personal information to government authorities, but we may disclose it where required by law or to protect rights, safety and property, including to prevent fraud and abuse.

Automated decisions. Roles are granted and removed automatically from blockchain data and your server's rules, and giveaway entries can be automatically disqualified. A server administrator can override these. If you think a decision is wrong, contact the server or us.

We do not sell your personal information for money, and we do not share it for cross-context behavioral advertising.

4. Your choices and rights

  • Disconnect from a server on your account page in the dashboard. Vulcan stops checking you for that server and stops sharing with it.
  • Remove a wallet on your account page. You lose roles that depended on it. We keep the removal in our security log, a short cooldown before the address can be attached to another account, and the address in past verification records until you ask us to delete them (see section 5).
  • Revoke Vulcan's access to your Discord account at any time in Discord's Authorized Apps settings. You can also unlink an X account.
  • Opt out of email by turning off feature updates and server-configuration emails on your account page, or by using the link in the email. We will still send service, billing and security messages.
  • Ask us to access, correct, delete or export your personal information, to restrict or object to how we use it, or, where we rely on consent, to withdraw it, by emailing [email protected]. We may ask for information to confirm it is you. An authorized agent may make a request for you if they can show authority. We respond within the time the law allows, usually 30 days in the EU and UK and 45 days in US states. If we deny a request, you may appeal by replying to our decision. We will not treat you differently for using your rights.
  • Limits. We cannot delete data from a blockchain. We may keep information we are required to keep, or need to resolve disputes, enforce our terms and protect against fraud, and servers keep their own copies of information they already received. If you are not satisfied with our response, you may complain to your data protection authority.

We do not sell or share personal information, so an opt-out preference signal such as Global Privacy Control does not change how we use it. We do not respond to "Do Not Track" signals.

5. How long we keep it

We keep personal information until you, or the server it relates to, ask us to delete it, or until we no longer need it for the purposes above. To ask, email [email protected]. A few things work differently:

  • Wallet removal records. When you remove a wallet, we keep the removal in our security log. The address cannot be attached to another account for 24 hours.
  • Billing records. We keep them as long as tax and accounting law requires.
  • Logs and error reports. We keep them for a limited time that depends on the settings of our hosting and monitoring providers, typically up to 90 days.

Information that you have already shared with a server, and public blockchain data, are not deleted by us from those places.

6. Security

We use technical, organizational and physical safeguards to protect personal information. No system is completely secure, and we cannot guarantee the security of your information. Never share your seed phrase or private keys with anyone, including anyone claiming to be Vulcan. Vulcan's website will never ask you to connect your wallet or sign a message, and we will never ask for your keys or ask you to send assets to us or to anyone else. One optional verification method asks you to send a small amount from your wallet back to the same wallet; nothing leaves it.

7. Children

Vulcan is not directed to children and you must be at least 18 to use it. We do not knowingly collect personal information from anyone under 18. If you believe a child has given us personal information, contact us and we will delete it.

8. International transfers

We are based in the United States and process information there. If you are in the European Economic Area, the United Kingdom or Switzerland, we transfer your information to the United States and other countries, and rely on standard contractual clauses approved by the European Commission and the UK government. Contact us for more information.

9. Region-specific information

EEA, UK and Switzerland. Premint, Inc. is the controller of the information we collect through Vulcan. Our legal bases are in section 2. You have the rights listed in section 4 and the right to complain to your supervisory authority.

California and other US states. In the last 12 months we collected the following categories of personal information, from you, from Discord, and from public blockchains and data providers: identifiers (Discord ID, username, email, wallet addresses, IP address), commercial information (holdings, subscription and payment status), internet activity (usage and logs), and inferences (the roles you qualify for). We disclosed them for the business purposes in section 3. We do not sell or share personal information as those terms are defined by the California Consumer Privacy Act, and we do not collect sensitive personal information as defined by it. You may use the rights in section 4. The sources, purposes, recipients and retention period for each category are described in sections 1, 2, 3 and 5.

10. Links to other services

Vulcan links to services we don't control, including Discord, marketplaces and block explorers. Their privacy policies govern what they collect.

11. Changes

We may change this policy as the Service changes. We will post the new version here and update the date above, and for a material change we will also notify you in the dashboard, in Discord or by email.

12. Contact

Premint, Inc., 249 S Highway 101 #220, Solana Beach, CA 92075. Email: [email protected].