Version 6
Privacy Policy
In short
- We collect what V3 needs to run the guild: your Discord ID and name, your computer's name, your game characters, and the guild data your addon saves, such as income, deposits, gifts and group activity.
- Guild data uploads automatically for guild and guide members; full-access members choose. Run logs upload only if you turn that on.
- Every member can see each member's name, points, gold given, rank, dues owed and credit score. Officers see more, such as daily income. The owner sees everything.
- Some data goes to Discord, to GitHub, and to the AI assistants the owner uses to fix problems. We never sell data and show no ads.
- Most data is kept while the guild service runs. Ask at [email protected] for a copy or for deletion.
- New in version 5: when Micro Managers or Guild Forge hits a Lua error, Micro Managers sends a short report about it by itself: the error message and where in our code it happened. Errors of other addons are not sent.
Effective date: November 16, 2026
This policy explains what personal data V3 collects, why, where it goes, who can see it, how long we keep it and what you can ask for. "V3" means V3 Companion for Windows and Mac, the service at https://app.micromanagersguild.com, the Micro Managers and Guild Forge addons and the V3 pack for Polestar. CNK Studios, operated by Cristopher Betances ("we") runs V3 and decides what happens to the data. Contact: [email protected].
1. What we collect, and from where
When you sign in
- With Discord: your Discord user ID, your display name in the guild's Discord server (or your Discord name), and your roles in that server. We ask Discord for "identify" and for "read your member info" (Discord's permission for server membership); we use the second only for the guild's own server. Sign-in does not give us your email address or your messages. We keep a Discord sign-in token so that we can check your roles again when your devices connect, at most every 15 minutes. When your roles no longer allow access, your devices are signed out, usually at the next check and at most within three days. If you try to sign in and are not a member, the display name and role IDs of that attempt are kept until the next attempt.
- With an invitation: the invitation code (stored only as a one-way hash) and, if the owner chose one, the guild member it is for.
- Your computer: its name as the operating system reports it (the "device name", which often contains a first name), when it signed in, when it was last seen, and the versions of V3 Companion and the addons it runs.
- Your agreement: which versions of these documents you agreed to, when, and from which device.
Guild data (Micro Managers)
When guild sync is on, V3 Companion uploads what Micro Managers saved in the game. For guild members and guide members this sync is part of membership and is always on; full-access members choose it with a switch. It holds:
- your characters' names, realm, class and level;
- your income by day and character, gold you spent at trainers, items you crafted, and auction sales by item;
- guild bank deposits, and the guild bank Money Log and item log as you saw them, which name the characters who made each deposit;
- gifts and trades with guild characters, with the items and the gold in them (gold between the two members of an open loan counts as that loan's, not as a donation);
- boss kills, quests and fights done in a group with guild characters, with the names of those characters;
- how the game ran (frame rate, latency, addon memory);
- once a day, your own character's lifetime gold statistics (gold acquired, most gold held, gold per day);
- requests, wishes and claims you make in the addon, including loan requests, loan offers and gold you confirm you received for a loan;
- while you want a guild legendary: your character's race, sex and the items it wears where a character model shows them (not the neck, rings or trinkets). The podium uses only the latest report of each character; earlier reports stay with your other uploads. Face and hair are not sent;
- bug reports you type in the game: your text, your character, level, class and zone, the game and addon versions and the addon's status. When the game blocks one of Micro Managers' actions, the addon saves such a report by itself (without text of yours), naming the blocked function, the game code that made the call, whether you were in combat and which game windows were open. When Micro Managers or Guild Forge hits a Lua error, Micro Managers also saves a report by itself (without text of yours): the error message, where in the code it happened, and whether the character was in the guild. Only errors that run through our addons' code are kept; errors of other addons, and the values of the game's variables at the error, are not sent. A report from a character outside the guild waits in the addon's saved data until a guild character logs in. At most three such reports are sent in a game session. A report about a Polestar guide step also carries the guide, step and quest, and your position on the map; you can also mark a spot yourself.
If you are an officer, your game also sends the guild roster (names, levels, classes, ranks, time offline), the guild event log (who joined, left, was invited, promoted or removed, and by whom), auction prices, and the lifetime gold statistics of guild characters near you. These cover guild members who may not use V3 themselves.
Micro Managers does not send chat or bag contents. It reads the game's loot and system messages only to count crafted items and guild joins. It does not send your position, except in a guide bug report as described above. Guild Forge profession data stays in the game.
Run logs (Polestar Recorder and the old V3 recorder)
Run logs are off until you turn on "Automatically upload my saved V3 run logs" (Windows) or "Automatically upload my saved V3 recordings" (Mac). The switch is offered to guide and full-access members. While it is on:
- Polestar Recorder. V3 Companion installs Polestar's recorder addon (Polestar_Recorder, from Polestar's official GitHub releases) and turns recording on in the way Polestar documents; the addon says so once in the game's chat. Typing
/psrec offin the game stops recording, and V3 Companion never turns it back on;/psrec onstarts it again. V3 Companion uploads the recorder's saved file (Polestar_Recorder.lua), one for every game account in the game folder you chose. It holds a random ID for the game account folder and one for each character (not their names); for each session your character's race, class, faction, sex, level, game language, region and game version, and the versions of Polestar, the recorder and the guide packs you use; your map positions and movement (including flights, boats, deaths, combat, being away and resting); the quests you were offered, accepted, progressed, handed in or abandoned, with quest text in which the game's use of your name is replaced; dialogue options you chose; creatures you killed or saw, loot, gathering, trainers, vendors and flight points; level, experience, reputation and skill changes; the size of your group (not who is in it); and the guide steps you went through. In Forever's new places it also records more about the world around you (creatures, map points, dungeon floors and bosses). It does not record character, realm or account names, other players' names, chat, whispers, guild, friends, mail, auction or trade data, or anything you type, except the notes you write with/psrec markand the labels you give/psrec trail. We use it to compare how fast the V3 routes are with Polestar's own. - The old V3 recorder. V3 no longer ships it, so it records nothing new, but its saved files can still be in your game folder. V3 Companion uploads them too: they hold the characters' names, class and level, the guide steps and quests you did, timings, idle time, combat events and their results, money changes, deaths, and map positions. A Windows problem report can also include your run log once, if you tick that box.
Run logs go only to our service, where each is stored with the device that sent it, so we know which member it came from. V3 Companion sends nothing to Polestar's makers. If you install Polestar's own app yourself, that app can share recordings with Polestar's makers under its own terms.
Problem reports
- Reports you write (Windows): your text, plus the app's versions, your access level, which switches are on, your Windows version and the status the app showed.
- Automatic error reports (Windows): when the app hits an unexpected error, it sends the error message and technical details, with the same app information, at most once a day for each kind of error. Your Windows user name and profile folder are replaced before sending. Paths inside the game folder, which can include your game account's folder name, are sent as they are.
- The Discord bug channel: if the guild uses one, the service reads the posts in it: the author's Discord ID and name, the text, and up to six images. Anyone who posts there is included, whether or not they use V3. The service marks each post it stored with a ✅ reaction.
Other people who do not use V3
The guild records in-game information about every character in the guild, whether or not its player uses V3: the guild roster and event log (name, level, class, rank, time offline, joins and leaves), and, for the dues check, the lifetime gold statistics that officers' games read from guild characters nearby. This is a condition of joining the Micro Managers guild, and the guild says so in its in-game information. Readings of a character that is not tied to a member using V3 are seen only by officers and the owner and are deleted after 90 days (section 5). Officers' readings of a V3 member's characters are also compared with the income that member's game reports, to find reports that are too low; only officers (never about their own characters) and the owner see the comparison, it is an estimate, and it charges nothing by itself.
Other data is also about people who never installed V3: characters named in the guild bank Money Log (including guild members who give gold without V3, whose names and totals are shown to every member as guest donations), characters named as group or trade partners, authors of posts in the Discord bug channel, and people who tried to sign in without the guild's roles.
What we do not collect
We do not ask for your real name, email address, payment details, precise location or contacts, and we do not collect chat. Your device name and Discord name may contain your real name. The service does not keep a log of every web request; it logs errors, and records every request that fails on the server's side with the page that was asked for. To limit repeated sign-in attempts, it keeps your internet (IP) address for at least 15 minutes, until the next sign-in attempt removes it. The web proxy in front of the service does not keep a log of requests either. The service's error log is kept on the server and rotated: it holds at most about 30 MB, and older lines are deleted as new ones arrive.
2. Why we use it
- To sign you in and decide what you may install (your Discord roles).
- To install and update your addons.
- To run the guild's economy: dues, reward points, credit scores, loyalty, gift credit, legendary awards and the guild fund. Officers' gold readings help find members who owe dues without using V3, and income reports that are too low.
- To find and fix problems, and to improve the V3 pack from run logs.
- To protect the service and the guild against misuse.
We do not sell personal data, show ads, or use it for anything else.
3. Who can see it
- You: your own uploads and what came of them (V3 Companion, Micro Managers, My activity).
- Every member of the guild: each member's name, total points, gold given, rank, dues owed and credit score (members who left are still listed); every member's approved characters and realm; guild requests, contributions, needs and goals with the characters and gold in them; the guild bank balance last seen and who opened the bank; guest donors' names and totals; and, once switched on, loyalty totals, legendary rankings and awards; the loan board (who asks to borrow, the amount, interest, days, what it is for and their credit score); with the race, sex and worn items of the first three in a legendary's order (from their main, or their latest report). Every member also receives the guild activity list. It includes events such as bank deposits by character name and amount, characters approved for a member, changes to a member's points under new rules, and the unused dues credit of a member who left the guild becoming guild gold, with that member's name. It no longer includes Discord accounts (IDs or names), devices, their access levels or sign-outs and the reasons, automatic registrations (which name the device), or the owner's changes to a member; those are on the owner's pages only. Such entries sent before this change may remain in saved data on members' computers.
- The two members of a loan: who lends, its due date and every payment of it. The gold itself, like any gold between members, also shows in the guild's contribution list, marked as loan gold.
- Officers: in addition, loans past due and pledges waiting for gold for more than two days (borrower, lender, amount and dates), each member's daily income and dues for the last 31 days, the dues check list of guild characters without V3 (with their lifetime gold readings and time offline), the income check of other members' characters (lifetime gold readings beside the income reported for them), depositor names the service could not match, and the evidence lines of help claims they review. Officers receive these in V3 Companion and Micro Managers, so a copy is kept in the saved data on their computers.
- The owner: everything listed in this policy, on the owner's pages of the service. Run logs are seen only by the owner and the owner's run-log review (see "AI assistants").
- Discord: Discord handles your sign-in and role checks, and hosts the bug channel the service reads. If the owner sets up an alert channel, the service posts guild bank alerts there, which can name a depositing character and the amount.
- GitHub: V3 Companion downloads Polestar directly from GitHub, so GitHub sees your internet address. No V3 sign-in is sent to GitHub.
- AI assistants: the owner uses AI coding assistants (Anthropic's Claude and OpenAI's Codex), running on the owner's computers, to read problem reports, error reports, bug channel posts and run logs and to find and fix problems. They work with the owner's access to the service, so they can reach the service's data while they do this, including guild data they read while working. The providers (Anthropic and OpenAI) process what the assistants read in order to run them, and may keep it for a limited time under their own terms, for example for safety and abuse checks. The owner has turned off the use of this data for training the providers' models.
- Others: only if the law requires it, or to protect someone's safety.
4. Where it is stored, and how it is protected
The service and its database run on a server managed by the owner, hosted by Hostinger in California, United States. Backups are kept on that server and copied to the owner's computer. The owner's computers also keep working copies of some run logs and reports for review.
- All traffic between V3 Companion and the service uses HTTPS.
- Your device's sign-in is stored on the service as a one-way hash. During a Discord sign-in from the Mac app it is kept in full until the app collects it, or until the next sign-in removes it if the app never does. On your computer it is protected by Windows (for your Windows user only) or kept in the Mac Keychain.
- The Discord sign-in tokens the service keeps are encrypted in its database with a key kept in a separate file on the server, not in the database. The server's backups hold both the database and that key file. The rest of the database and the backups are not encrypted separately.
- The owner's pages need the owner's sign-in.
No system is perfectly secure. If a breach puts your data at risk, we will tell affected members through the guild's Discord and by any other contact we have, as the law requires.
5. How long we keep it
- Run logs: at most 90 days on the service, and at most the newest 20 for each device: an older one is deleted when the same device uploads a new one. The copies the owner's run-log review keeps on the owner's computer are also deleted after 90 days.
- Officers' gold readings of a guild character that is not tied to a member using V3: 90 days. Of a member's character: 90 days too, except readings taken before the member's first income report or up to 3 days after it, which back dues use; those stay like the guild's books.
- Guild roster: a character's line goes 90 days after it left the guild, unless it is a character of a member using V3.
- Guild event log: 180 days. The earliest join line of a character still in the guild, or of a member using V3, stays while they are: it sets the first 14 days' dues rate.
- Sign-in attempts (with your internet address): at least 15 minutes, until the next attempt removes them. Discord sign-in sessions: at least 10 minutes, until the next sign-in removes them.
- Detailed income steps: about 35 days; they are removed when your income is next reviewed. The daily income totals behind your dues are kept.
- Everything else (members, devices, characters, uploads and their raw copies, the guild's books, readings, problem reports, Discord bug posts, agreement records): for as long as the guild service runs, because the guild's books depend on it. Leaving the guild, losing your Discord role or having a device signed out does not delete it.
- Backups: seven nightly archives on the server and seven copies on the owner's computer, which rotate within about a week, and the five newest archives made before each update of the service, which rotate only when new ones are made and can be older. Deleted data can stay in these until they rotate out. A restore of the service also sets aside the data it replaces; the owner deletes that copy once the restore is confirmed.
6. Your choices and requests
- Turn uploads off: full-access members can turn guild uploads on or off (after a change from guild or guide access it stays on until you turn it off), and run log uploads are off until you turn them on, on V3 Companion's home page.
/psrec offin the game stops the Polestar Recorder whatever the switch says. You can also pause V3 Companion, or quit it. - A copy: V3 Companion shows your uploads under My activity. For a full copy of what we hold about you, write to [email protected].
- Correction: tell an officer or write to us.
- If you are in the guild but do not use V3: write to [email protected] with your character's name, and we delete the roster line, gold readings and event-log lines about it. Guild bank log lines that name your character stay, because the guild's books depend on them, and so does your character's name and total in the guest donations every member sees. While the character stays in the guild, the next roster an officer's game sends lists it again.
- Deletion: write to [email protected] and say which member and Discord account you are. We confirm it is you, remove your guild role in Discord, then erase your data within 30 days: your devices are signed out, and your run logs, raw uploads, characters, income steps and gold readings, group and trade evidence, Discord link, problem reports, bug channel posts kept by the service, and officers' readings about your characters are deleted. To keep the guild's books correct, your points, dues totals, credit, loyalty and help records, gifts, contributions and awards stay under the name "Removed member"; text you wrote in them stays unless you ask us to remove it. The guild bank logs keep the depositor's and reader's character names as the game showed them to officers, linked to that record. Mentions of your characters in other members' records (for example as a group or trade partner), in the service's own problem logs and alerts, and in the owner's notes are removed only if you ask and we can find them. Posts in Discord itself stay until you or a moderator delete them there. Backups and working copies are not changed; they hold the data until they rotate out (section 5).
7. Children
You must be at least 13 to use V3. Members aged 13 to 17 may use V3 with a parent's or guardian's permission. V3 is not directed at children under 13, and we do not knowingly collect their data. If we learn that an account belongs to a child under 13, we remove its guild role in Discord, sign out its devices and erase its data as section 6 describes. Parents or guardians can ask us at [email protected] to see or delete their child's data.
8. Changes
When we change this policy, we raise its version number at the top of this page. From V3 Companion 1.1.27, the app then asks you to agree again before it signs in or uploads anything more. Older versions of the app do not ask; please update.
9. Contact
CNK Studios, operated by Cristopher Betances, New York, United States. Email: [email protected]
Questions or requests: [email protected]