Privacy Policy

Last updated November 9, 2026

PlugNApps LLC, a Washington limited liability company, runs PlugNApps: this website, the shared PlugNApps login at account.plugnapps.com that you use to sign in to PlugNPortal and PlugNKiosk, Sign in with Microsoft and Google, the referral program, and our support. This policy explains what we collect for those, how we use it, who receives it and how we protect it.

How this fits with each app's policy

This policy covers your login and everything that goes with it across our apps. Each app's own policy covers the information that app handles for the businesses that use it:

PlugNPortal's Privacy Policy covers guest WiFi sign-ins, UniFi networks and portal content.
PlugNKiosk's Privacy Policy covers visitors, the people they visit, signed agreements and text messages.

Your login

Who you are: your name, your email address and when you confirmed it.
How you sign in: a hash of your password, never the password itself; your authenticator app's sign-in code secret, stored encrypted; your recovery codes, stored only as hashes; and, if you add them, your passkeys. A passkey gives us only a public key and its ID, the name you give it, and when it was added and last used.
Where you use it: which of our apps your login is used with, and your role on each business or office you belong to.
Keeping it safe: short-lived counts of recent sign-in attempts, by email address and network address, so nobody can keep guessing passwords or codes. One-time links and codes, such as a password reset link or the code that passes you to an app after you sign in, are stored only as hashes and stop working once they're used or expire.
Support and technical data: messages you send us, and server logs that can include IP addresses and browser type.

When you sign in to one of our apps, the login gives that app your login's ID, your name and email address, whether your email address is confirmed, how and when you signed in (with a password, a code, a passkey, or Microsoft or Google), and the IDs of any Microsoft or Google accounts linked to your login. PlugNKiosk uses those IDs to check your organization's groups when you sign in with Microsoft or Google, as described below.

Sign in with Microsoft or Google

Signing in with your work Microsoft or Google account is optional, unless your organization makes you use it. A login that was created by signing in with Microsoft or Google has no password of its own: your organization manages how you sign in. A PlugNKiosk account can also require it for the people who get their role from its directory. It's for organizations: Microsoft sign-in accepts work and school accounts only, not personal Microsoft accounts or guests, and Google sign-in accepts Google Workspace accounts only, not personal Gmail accounts.

What we ask for: only the basic sign-in permissions that say who you are. The PlugNApps sign-in app can't read your mail, files, calendar or directory.
What we receive: from Microsoft, your organization's tenant ID, your user ID there, your name and your sign-in address; from Google, your Google user ID, your Workspace domain, your name and your email address. Google also sends your profile picture link and language, which we don't keep. Your Microsoft or Google password never reaches us, and your organization's own rules, including its second step, apply when you sign in there.
What we keep: which provider it is, those IDs, your Workspace domain, the email address the provider gave when it was linked, and when it was linked and last used. We recognize you by the provider's IDs, never by your email address alone.
Linking: if you already have a login with the same email address, we don't link the two until you've also signed in to that login with its password or a passkey, in the same browser, within ten minutes. You can also link or unlink Microsoft or Google from your login's Security page. A new login can only be made this way for an organization that has connected its directory to one of our apps and given dashboard roles to its groups there.

Directory sync in PlugNKiosk

A PlugNKiosk account can connect its organization's Microsoft 365 or Google Workspace directory. Only an administrator of that organization can approve it, and the access is read-only:

Microsoft 365, through Microsoft Graph: the names of the organization's groups, so the account can pick them; the members of the groups the account picks, with their name, email address and directory ID; and the organization's verified domains. The person connecting signs in to Microsoft once, so we can confirm which organization it is.
Google Workspace, through the Google Admin SDK: the names and email addresses of the organization's groups, so the account can pick them; the members of the groups the account picks; and, if the administrator allows it, the organization's verified domains. To fill in members' details, each sync reads the Workspace's user list (each user's name, primary email address, ID and whether they're suspended); we keep only the people in the picked groups. We also keep the email address of the Google administrator who approved the connection, and their Google authorization, stored encrypted.

We also keep which of the account's people connected the directory, and when. We use this information only to provide these features:

To fill the account's People list. The kiosk shows these people's names so visitors can pick who they're visiting, and when a visitor picks someone, we email them an arrival notice (delivered through Microsoft 365) and include their name in the account's own Teams or Slack arrival alerts, if it has turned those on.
To give dashboard roles to the people in the groups the account maps to them, and to check those groups when someone signs in with Microsoft or Google.
To let the organization's people create a PlugNApps login by signing in with Microsoft or Google: we pass the organization's Microsoft tenant ID, or its Workspace's email domains, to the PlugNApps login.
To prove the organization owns its email domains.

We don't sell this information, we don't use it for advertising, and we don't use information from Google Workspace APIs to develop, improve or train generalized AI or machine-learning models. We don't send the names or email addresses we get from a directory to Anthropic.

An account's owner can disconnect the directory at any time. That deletes the saved connection, including the Google authorization, and ends the roles its groups gave. People who were already synced stay on the account's People list as ordinary entries until the account removes them or closes; someone taken out of a picked group is taken off the kiosk at the next sync, but stays in the account's records because past visits point to them. Removing our access in your Microsoft or Google settings stops further syncs, but doesn't delete what was already synced. To have this information deleted, the account can remove those people, close its account, or email us.

PlugNApps' use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The referral program

If you take part in the referral program, we keep your referral code, the businesses that signed up with it, and the commissions and payouts that come from them. Before your first payout we also collect a W-9: your legal name, business name, address, tax classification and taxpayer identification number, and your payout method and its details. Everything sensitive in these is stored encrypted. We keep the version of the program terms you agreed to, and when and from which network address you agreed to them and signed the W-9.

Support

When you email our support address or use the help chat in an app's dashboard, we keep the messages, who sent them and what they're about. PlugNSupport, our support assistant, uses Anthropic's Claude to read each new message, sort it, and suggest or send a reply; its replies say they came from the assistant, and a person on our team takes over if you reply that it didn't help. With each help chat message, the assistant also gets a summary of your account's setup and status, such as the business or office name, your email address and role, billing and setup state, location and device names, and counts such as recent sign-ins or visits. It never gets passwords or keys.

Staff access to your account. PlugNApps staff open a customer's account only with the approval of the account's owner or, for a business in a company, one of the company's Super Admins, asked for by email or in the app. An approval lasts no more than 24 hours, the owner or one of those Super Admins can end it sooner, and every request, answer and visit is recorded with who made it.

How we use it

To sign you in to our apps and keep your login secure.
To keep your organization's People list and dashboard roles in step with its directory, when it has connected one.
To run the referral program, pay commissions and meet our tax reporting obligations.
To send account emails, such as confirming your address, password resets, security notices, approval requests and payout notices, and to answer you when you contact us.
To keep the service secure, limit abuse, fix problems and restore from backup.
To meet legal obligations.

We don't sell personal information, use it for advertising, or run advertising or analytics scripts.

Who receives it

We share information only as the service needs, over encrypted connections to these providers' systems:

Vultr: hosts our servers, in Seattle, Washington, United States.
Cloudflare: provides our domain name service, and carries traffic to the PlugNKiosk app at plugnkiosk.app.
Microsoft: delivers our emails and hosts our support mailbox through Microsoft 365. If you use Sign in with Microsoft, or connect a Microsoft 365 directory, Microsoft handles that sign-in or connection.
Google: if you use Sign in with Google, or connect a Google Workspace directory, Google handles that sign-in or connection.
Anthropic: its Claude model reads support messages and help chats, with the account summary described above, for PlugNSupport.
Stripe and its Link service: sell and collect payment for our apps' subscriptions, and handle sales tax, receipts and billing support. Card details go to Stripe directly and never reach our servers.
Payout services: when you claim a referral payout, the payment is sent by the method you chose, Zelle, Venmo, Cash App or bank transfer, using the details you gave us.
The IRS: referral commissions are reported where the law requires, as the referral terms explain.

The apps you sign in to receive who you are, as described above, and a business or office you belong to can see that you're on its team and your role there. We may also disclose information when the law requires it, to protect people or the service, or as part of a sale or transfer of the business.

How long we keep it

Your login is kept while you use it. When a business you belong to is closed, or you're taken off its team, a login you also use for another app or for the referral program stays, with its password, codes and passkeys; any other login is deleted with it. Deleting a login also deletes its passkeys, recovery codes and Microsoft or Google sign-ins. Referral commission and payout records are tax records, so they're kept even when a login or business is deleted. Closed support cases are deleted a year after they're closed, and help chats that didn't become a case after 90 days; support emails also remain in our Microsoft 365 support mailbox. Directory information is kept as described under Directory sync above. Backups clear within 30 days.

How we protect it

Our sites and the login use encrypted HTTPS connections.
Passwords, recovery codes and one-time links and codes are stored only as hashes, so we can't read them.
Authenticator secrets, W-9 and payout details, and Google directory authorizations are encrypted when stored.
Every login must set up an authenticator app for two-step sign-in, unless it signs in with Microsoft or Google, where your organization's own rules apply.
Backups are encrypted, and server access is limited to our administrator.

No system is completely secure, so we can't guarantee absolute security.

Cookies

The login at account.plugnapps.com uses a cookie to keep you signed in and protect your forms. This website sets no cookies of its own. We don't use advertising or tracking cookies.

Your choices and rights

You can change your password, authenticator app and passkeys, and link or unlink Microsoft or Google, from your login's Security page. You, or your organization's administrator, can also remove PlugNApps' access in your Microsoft or Google account settings; that stops further sign-ins and syncs, and information we already have is kept and deleted as described above. Depending on where you live, you may have the right to access, correct or delete your personal information. Email us to make a request, including to delete your login. If your information came to us through a business or office that uses our apps, we may refer your request to it.

Children

PlugNApps is for businesses and isn't directed to children. We don't knowingly collect children's information for our own purposes.

Where information is processed

We're based in the United States, and our servers are hosted by Vultr in Seattle, Washington, United States. Cloudflare, Microsoft, Google, Anthropic and Stripe may process information in the United States and other countries when they provide their part of the service, as described above.

Changes

We'll post any changes on this page with a new version label, and tell customers by email about significant ones.

Version 2026-11-09 (updated 9 Nov 2026: the provider is now PlugNApps LLC). Questions or requests: support@PlugNApps.com