Privacy Policy
Effective date: November 5, 2026
This policy explains how Ternary Developments Inc. ("Ternary", "we", "us") handles personal data. Ternary is a platform that businesses use to run their Discord communities: signup pages, Discord roles, a member list, paid memberships, polls, saved posts, support tickets, a Claude connector and a developer API.
It covers three groups of people:
- Businesses that use Ternary, and the team members they invite to their dashboard.
- Members: people who sign up to, buy from or take part in a community run by a business on Ternary.
- Visitors to ternarydev.com.
1. Our two roles
For members, the business is in charge. Each business decides what its signup pages ask for, which features it turns on, and what it does with its members' data. The business is the "controller" of that data (under the CCPA, the "business"). Ternary processes it on the business's behalf, as its "processor" (under the CCPA, its "service provider"), and only to provide the platform to that business.
If you are a member, the business's own privacy notice applies to you, and the business is the right place to send questions and requests. If you contact us, we will pass your request to the business and help it respond. Each business's data is kept separate, and one business cannot see another's members.
For businesses and visitors, Ternary is in charge. We are the controller of the data about business accounts, team members, billing and our website.
| Whose data | Who decides how it is used | Who to contact |
|---|---|---|
| Members of a community | The business that runs it (Ternary is its processor) | The business, first |
| Business accounts and their team members | Ternary | Ternary |
| Visitors to ternarydev.com | Ternary | Ternary |
2. What we collect
About members (on behalf of the business)
What we hold depends on what the business asks for and which features it turns on.
- Signup details: your name and email address, the answers to any extra questions the business adds to its signup form, and the code we email you to check your address.
- Your acceptance of the terms: when you accepted, which version of the terms, the IP address you accepted from, and whether you accepted ad cookies.
- Discord account: when you link Discord, Discord shares your account ID, username, display name, avatar, email address and the list of servers you are in. Of this, only your ID, username, display name and avatar are kept. Your Discord email address is only compared with the email address you signed up with, and is not stored.
- Server membership: whether you are in the business's Discord server, the roles Ternary gives you, and, if the business turns on member tracking, your current Discord username and server nickname, and whether you have left.
- Activity counts: if the business turns on activity tracking, how many messages you post in each channel and thread of its server, by day, and when you last posted. This never includes what your messages say.
- Saved posts: if the business picks channels to save, the posts in those channels, including their text, thread replies, edits, deletions, and copies of image, text and PDF attachments up to 8 MB. Nothing is saved from channels the business has not picked.
- Poll votes: your answers to polls the business posts through Ternary.
- Support tickets: the tickets you open and the messages in their Discord threads. If the business connects Slack, tickets are also sent to the business's Slack workspace.
- Purchases: if you buy a paid membership, the plan, its price and currency, when you bought it, your subscriptions, Stripe's references to your customer record and subscription, and, if checkout asks for them, your billing address and phone number. Your card details go straight to Stripe. Neither Ternary nor the business ever sees or stores them.
- How you arrived: the page you landed on, the referring site, any campaign tags in the link, and the signup steps you complete. This is recorded whether or not you accept cookies.
- With your consent only: ad click identifiers (such as Google's gclid, Meta's fbclid and TikTok's ttclid), ad-network cookies, and your IP address and browser details kept with the record of how you arrived.
About businesses and their team members
- Account details: name, email address, password (stored only as a one-way hash), role, and the business's name, branding and settings.
- Connections: the Discord servers you connect, your Stripe account ID, your Slack webhook, your pixel IDs, and the API keys and Claude connector tokens you create (stored only as one-way hashes).
- Billing: your Ternary plan, invoices and payment status. Your card is saved with Stripe, not with us.
- Usage and audit logs: sign-ins, and a log of each developer API and Claude connector call (which tool or endpoint was used and when, but not what was asked).
- Messages to us: support requests and other emails.
About website visitors
- Contact and demo forms: the details you enter, such as your name, email address, phone number and message.
- Technical data: like any website, ternarydev.com receives your IP address, browser details and the pages you request.
We do not ask for sensitive data, such as health information or government ID numbers, and we ask businesses not to collect it through Ternary.
3. Where the data comes from
- From you, when you fill in a signup, checkout or contact form, or use the dashboard.
- From Discord, when you link your Discord account (Discord OAuth), and through the business's Ternary bot, which reads the business's server: its member list, nicknames, message counts, poll votes, ticket threads and the posts of the channels the business picks.
- From Stripe, about payments, subscriptions, refunds and disputes, and the billing details checkout collects.
- From the business, when it adds or imports member records, including from earlier versions of Ternary.
- From your browser, through the cookies and storage described in our Cookie Notice, and the link you arrived by.
- From Cloudflare, which passes on the visitor's IP address when a business serves its pages from its own domain.
4. Why we use it
Member data is used only to provide the platform to the business, as the business sets it up. The business is responsible for having a legal basis for each use:
- to create your membership, check your email address and give you access to the business's Discord server and roles;
- to take payment for and manage a paid membership;
- to keep the business's member list up to date, show its team who is active, and export its members;
- to run its polls, saved posts and support tickets;
- to email you about your signup or membership, on the business's behalf;
- to show the business which pages and campaigns bring new members, and, with your consent, to let its ad pixels measure its ads;
- to keep the platform secure, prevent abuse (for example, rate limits on signup codes), and fix problems.
Data about businesses and visitors is used by Ternary, on these legal bases where the GDPR or UK GDPR applies:
| Purpose | Legal basis |
|---|---|
| Providing your account, the platform and support | Performance of our contract with you |
| Billing, invoices, tax and accounting | Contract, and our legal obligations |
| Security, fraud and abuse prevention, audit logs | Our legitimate interest in keeping Ternary safe |
| Improving Ternary, using feature usage and error data | Our legitimate interest in a better product |
| Answering contact and demo requests, and product updates to business customers | Our legitimate interest in running our business (you can opt out of updates at any time) |
| Any optional analytics or ad cookies on ternarydev.com | Your consent |
| Responding to lawful requests from authorities | Our legal obligations |
We do not use member data for our own marketing, we do not sell personal data, and we do not use any of it to train AI models.
5. Cookies and ad pixels
Ternary's signup and checkout pages show a cookie banner, with equal Accept and Decline buttons. You can sign up whichever you choose.
- Some cookies are always set because the pages need them: to keep you signed in and to keep your signup in progress. A first-party cookie that remembers how you first arrived (
tny_touch) is also set whichever you choose. - The business's Meta, Google and TikTok pixels load only after you accept. They send data from your browser straight to those companies, under their own privacy policies. Ternary does not send member data to ad networks from its servers, and none of your Discord data is sent to them.
- If you decline later, the ad click identifiers, ad-network cookies, IP address and browser details kept with the record of how you arrived are removed at once.
Our Cookie Notice lists each cookie and how to change your choice.
6. Who we share it with
The business. A member's data is available to the business that runs the community, and to the team members it gives access.
Our subprocessors. We use these providers to run Ternary. Each may only use the data to provide its service to us, under a contract with data protection terms.
| Provider | What it does for Ternary |
|---|---|
| Railway | Hosts our servers and their logs |
| MongoDB Atlas (MongoDB, Inc.) | Hosts our database |
| Stripe | Processes Ternary's own billing, and the member payments each business takes on its own Stripe account through Stripe Connect |
| SendGrid (Twilio Inc.) | Sends emails, such as signup codes, welcome emails and account emails |
| Cloudflare | Serves businesses' custom domains, and protects the platform against attacks |
| Discord | The platform the communities run on: our bot gives roles and reads the business's server through Discord |
| DigitalOcean Spaces (DigitalOcean, LLC) | Stores files, such as saved-post attachments and branding images, and our encrypted backups |
| Webflow | Hosts ternarydev.com and its forms |
Discord and Stripe also handle data under their own privacy policies, as independent companies, when you use their services directly. We will update this list, and tell businesses in advance, before we add or replace a subprocessor.
Services a business connects. When a business connects a service, we send it the data that service needs, on the business's instructions. Once there, the data is under that service's terms and the business's control:
- Slack, if the business forwards support tickets to its Slack workspace;
- Claude (Anthropic), if the business connects the Claude connector. Only the business's owners and admins can connect it, and it can only read members, poll votes and saved posts;
- the business's own systems, through the developer API;
- Meta, Google and TikTok, through pixels in your browser, only after you accept cookies;
- other tools a business connects, such as an email marketing or online course tool.
Others, only when needed. We may share data if the law requires it, to protect the rights, safety or property of Ternary, our users or others, or as part of a merger, acquisition or sale of our business, in which case this policy will continue to protect it.
7. International transfers
Ternary is based in the United States, and our providers store and process data in the United States and other countries where they operate. When we transfer personal data from the European Economic Area, the UK or Switzerland, we protect it with the European Commission's Standard Contractual Clauses (with the UK and Swiss addenda), or with the provider's certification under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions, where it has one.
8. How long we keep it
| Data | How long |
|---|---|
| A signup started but never verified | Deleted 30 days after it was started |
| The record of how a visitor arrived, if they never verify their email address | Deleted 90 days after they arrived. The signup steps they completed are kept until the business deletes them or closes its account |
| Ad click identifiers, ad-network cookies, IP address and browser kept with that record (only with consent) | Removed at once if consent is withdrawn, and in any case 180 days after the email address is verified |
| A verified member's record: signup details, acceptance of the terms, Discord details, how they arrived, signup steps, purchases | Until the business deletes the member or closes its account |
| Activity counts | Deleted 400 days after the day they count |
| Saved posts and their attachments | Until the business asks us to delete them or closes its account. A post deleted in Discord within 7 days of being posted loses its text and attachments at the next daily check. If the business stops saving a channel, posts already saved are kept |
| Poll votes and support tickets | Until the business asks us to delete them or closes its account |
| Developer API and Claude connector logs | 90 days |
| Claude connector access | Access tokens last 1 hour and refresh tokens 30 days. A revoked connection stops at once |
| Sign-in sessions | Up to 7 days without activity |
| Business account data | While the account is open, then deleted after the 30-day export window that follows closure |
| Ternary's own billing and tax records | As long as tax and accounting law requires |
| Contact and demo requests | As long as we need them to answer and follow up |
| Encrypted backups | Deleted after 30 days |
When a business closes its account, we delete its members' data at the end of the 30-day export window, except what the law requires us to keep. Deleted data leaves our backups within the backup period above.
Data held by Discord, Stripe or a service the business connects is kept under that company's own policy.
9. Your rights
Depending on where you live, you may have the right to:
- know what personal data is held about you, and get a copy of it in a portable format;
- correct it;
- delete it;
- restrict or object to how it is used, including at any time for direct marketing;
- withdraw consent you have given, such as for ad cookies, without affecting what was done before;
- complain to your data protection authority.
Members: please send requests to the business that runs your community. It decides what happens to your data, and we help it respond. If you write to us, we will pass your request on.
Businesses, team members and visitors: email us at support@ternarydev.com. We will need to confirm your identity first, and we will answer within one month (in California, within 45 days). We may extend that when the law allows, and will tell you if we do.
California residents
This section applies to the data Ternary controls, and describes the data we process for businesses. In the past 12 months we have collected:
- identifiers, such as name, email address, Discord ID, IP address and account IDs;
- customer records, such as billing address and phone number;
- commercial information, such as plans bought and subscriptions;
- internet activity, such as pages visited, referring sites, campaign tags, signup steps and, with consent, ad identifiers;
- account login details (email address and password), used only to sign you in;
- for members of communities that turn the features on, the content of messages in channels a business saves, and message counts.
We collect it from the sources in section 3, use it for the purposes in section 4, share it with the categories of recipients in section 6, and keep it for the periods in section 8.
We do not sell personal information. Ternary does not "share" it for cross-context behavioral advertising either. When a business adds ad pixels, those pixels run only after a visitor accepts ad cookies, and the business is responsible for them. You can decline them in the cookie banner. We do not use sensitive personal information to infer anything about you. You have the rights to know, delete and correct, to opt out of selling and sharing, and to limit the use of sensitive personal information, and we will not treat you differently for using them. You may use an authorized agent, who must show your written permission.
10. Security
We protect data with:
- encryption in transit (HTTPS) everywhere, and encryption at rest by our hosting and database providers;
- separate data for each business, checked on every request, so one business cannot read another's data;
- passwords, API keys and Claude connector tokens stored only as one-way hashes;
- roles for team members (owner, admin and read-only), and a read-only Claude connector that cannot change any data;
- card details handled only by Stripe;
- encrypted backups;
- logs of developer API and Claude connector use;
- limiting staff access to what each person needs.
No system is completely secure. If a breach affects your personal data, we will tell the affected business, or you, as the law requires.
11. Children
Ternary is not for children under 13, and Discord does not allow them. We do not knowingly collect data from children under 13, or under the age of digital consent where they live. If you think a child has given us data, contact us or the business, and it will be deleted.
12. Changes to this policy
We will post any change on this page and update the effective date. If a change is material, we will tell businesses by email or in the dashboard before it takes effect.
13. Contact
Ternary Developments Inc.
support@ternarydev.com
