Privacy Policy

1. Who this covers

This policy explains how MONAD INDUSTRIES SOFTWARE CORP. ("we") handles personal information in frontkiosk. It covers three groups of people:

• Customers: the offices that create a frontkiosk account, and their staff who use the dashboard.
• Visitors and hosts: people who sign in at a customer's kiosk, and the staff members they visit.
• Website visitors: people who browse frontkiosk.net.

For visitor and host data, the customer decides what is collected and why. We process that data on the customer's behalf and follow their instructions. If you signed in at an office, that office is your first contact for questions about your visit; you can also contact us.

2. What we collect

Customer accounts

• Business name, the account owner's name and email, and a password. Passwords are stored only as a salted scrypt hash.
• If you sign in with Google or Microsoft: your verified email and the account ID that provider gives us.
• The answers to the optional setup questions (such as type of workplace, team size and how visitors sign in today).
• Location settings: location name, time zone, address, logo and colours, policy/NDA text, photo and badge settings, the webhook URL you enter, and email settings, including your own SMTP server details if you choose to send emails through it.
• Hosts you add: name, title, email, phone and alert preferences.
• Billing records: plan, number of locations, amounts, status and Stripe's customer and subscription IDs. For deal-platform codes: the code, platform, tier and when it was redeemed.

Visitors (set by each office)

• Name, and if the office's kiosk asks for them: company, email, phone, visit type and reason for the visit.
• Who they are visiting (the host).
• Sign-in and sign-out times, how they signed out (kiosk, badge QR code or staff), and the kiosk language used.
• If the location uses a visitor policy or NDA: that it was accepted, its title, a fingerprint (hash) of the policy text, and the visitor's drawn signature image if a signature is required.
• A photo, only if the location turns on visitor photos.
• Random badge and sign-out codes so the visitor can sign out by scanning their badge.

Messages we send for customers

• Host email alerts: when a visitor signs in, the host gets an email with the visitor's name, company, reason and time. It can include the visitor's photo if the office turns that on.
• Visitor policy copy: if the office turns it on, a visitor who gave an email and signed a policy gets a copy by email.
• Webhook alerts: if the office enters a webhook URL (for example a Slack or Teams address), frontkiosk sends the visitor's name, company, email, phone, visit type, reason, host name and email, and times to that URL when visitors sign in or out. The office controls that destination.
• We keep a log of these messages (recipient, subject, delivery status) so the office can check alerts were delivered. It keeps the most recent 500 entries per office.

Website visitors

• We run our own simple analytics, stored in our database in two tables, page_views and site_events (for example "visited the demo" or "signed up for the newsletter"). For each public page view we record the page, the referring site (without its query string), campaign tags in the link (utm values or a ref code), the browser and operating system family (such as "Safari/iOS"), the country if our hosting provides it, whether it looks like a bot, and a keyed hash of the IP address instead of the IP itself.
• We do not use Google Analytics, advertising pixels or third-party tracking scripts. Some pages load fonts from Google Fonts, which means your browser asks Google for the font files.
• If you subscribe to our newsletter, we keep your email, the answers you choose to give, the page you signed up on, the consent text you agreed to, and a hashed IP. You can unsubscribe with one click in any issue. Signups made through our hosted form on Kit are handled by Kit.

3. Cookies

• vk_session: keeps you logged in to the dashboard. It expires after 12 hours.
• fk_onb: remembers your answers to the setup questions before you have an account (30 days).
• fk_ref: set only when you arrive from a link with a referral or campaign code, so we know which link brought you (30 days).

We don't use advertising cookies.

4. How we use information

• To run the service: sign visitors in and out, alert hosts, print badges, show who is on site, make evacuation lists and exports.
• To manage accounts, billing, deal-platform codes and support.
• To send service emails (welcome, password reset, account setup, billing) and, only if you subscribed, the newsletter.
• To keep frontkiosk secure, for example rate limits on sign-in attempts and code redemptions.
• To understand which pages and links bring people to frontkiosk.net, using the analytics described above.

frontkiosk never sells personal data. We don't rent it, share it with advertisers or use visitor data for our own marketing.

5. Service providers we use

Provider	What it does for frontkiosk	Data it handles
Render	Hosts the frontkiosk application (United States, Oregon region)	All traffic to frontkiosk.net passes through it
Neon	Hosts our Postgres database on AWS in the United States (us-west-2, Oregon)	Account, location, host and visitor data, including photos and signatures, plus analytics
Stripe	Processes payments, subscriptions and the billing portal	Payment details you enter at Stripe Checkout, your email and billing details
Resend	Sends emails (host alerts, visitor policy copies, account and billing emails, newsletter)	Recipient addresses and email content

If an office sets up its own SMTP server in frontkiosk, that office's alert emails are sent through its own email provider instead. If you sign in with Google or Microsoft, that provider confirms your identity. We share information with authorities only when the law requires it.

Our providers are in the United States, so your information is stored and processed there and may be accessible to authorities under US law.

6. How long we keep data

• Visitor records, photos and signatures are kept for as long as the office's account exists. frontkiosk does not have an automatic deletion setting today. An office can ask us to delete older visitor records, or a specific visitor's record, by emailing us.
• The alert log keeps the last 500 entries per office, and billing history keeps the last 100 entries per office. Older entries are deleted automatically.
• Login sessions expire after 12 hours. Password reset and setup links expire after 60 minutes.
• When an account is closed, we delete its data within 30 days. Our database provider keeps a short restore history (about 6 hours), after which deleted data is gone from it too. We keep billing records as long as tax law requires.

7. Security

Connections to frontkiosk use HTTPS. Passwords are hashed. Each office's data is separated in the database, and kiosk links, badge codes and API keys are random and hard to guess (API keys are stored only as a hash). No system is perfectly secure; if a breach affects your personal information, we will tell affected customers and the authorities as the law requires.

frontkiosk is a general-purpose visitor sign-in tool. It is not certified under HIPAA or any other security or privacy certification, so don't use it to collect health information.

8. Your choices and rights

• You can ask to access, correct or delete your personal information, or ask what we hold about you, by emailing frontkioskeur@gmail.com. We reply within 30 days.
• Visitors: we may need to check with the office whose kiosk you used before we change or delete their records.
• Customers can export their visitor log as CSV from the dashboard at any time.
• If you are not happy with our answer, you can contact the Office of the Privacy Commissioner of Canada, or the privacy authority where you live.

9. Children

frontkiosk is a business service and is not meant for children to create accounts. Schools that use the kiosk decide what to collect from visitors and are responsible for the notices their visitors need.

10. Changes

If we change this policy in a way that matters, we will update the date at the top and tell account owners by email.

Contact