Privacy policy

Last updated: 19 October 2026

This page describes how the service works today. It is a plain-language draft and should be reviewed by a qualified person before wide public launch.

Who we are

FaisPulse is operated by FaisTune Creation, Muscat, Oman ("we"). Contact: the contact details on faistune.com.

Two kinds of people

Participants join a session with a code or QR code. They do not sign up and we do not ask for an email, phone number or account.
Creators sign in with Google to create and run sessions.

What we collect from participants

• The answers you submit, and the optional nickname you type.
• A random identifier created in your browser (stored in your browser's local storage) so that your answers count once and can be changed while voting is open. It is not linked to your name, email or device.
• We do not store your IP address. To stop abuse we keep a one-way, keyed hash of it for a few minutes to count how many requests come from one network. That hash cannot be turned back into your address.

The person running a session can see the answers and nicknames from that session. Anyone who knows a session's join code can also see its live results on the presenter screen. Do not type personal or confidential information into an answer.

Optional per-network limit. A session owner can switch on a limit on how many different devices may answer from one network address. When it is on, a one-way hash of your network address and your random device ID are stored for that session only and deleted with it. Shared networks (a conference Wi-Fi, a mobile carrier) can look like one address, so the limit is off by default.

Audience questions and reactions. If the session owner switches them on, questions you type are stored with the session, together with your random device ID so that your upvotes can be counted once and you can see which question is yours. No name is attached. Emoji reactions are stored without any identifier and deleted after a few minutes. Questions are removed when the session is deleted, and the session owner can hide or delete any of them.

Logos, backgrounds and schedules. A session owner may upload a logo and a background picture. They are stored on the server for that session only, shown to people who join it, and deleted with the session. Opening and closing times are stored with the session.

Moderation and reports. Written answers can be hidden automatically by a simple word filter, and the session owner can hide or delete any answer. Participants can report a session from the link at the bottom of the page. A report stores the reason, your optional note, the time and a one-way hash of your network address (to limit spam reports). Reports are reviewed by the site administrator and deleted together with the session.

What we collect from creators

• From your Google account: your Google account ID, email address, name and profile picture. We request only the basic sign-in scopes (openid, email, profile). We never see your Google password and we do not access your Gmail, Drive or any other Google data.
• The sessions, questions and results you create.
• A short security log (sign-ins, session creation and deletion, administrative actions) with the hashed network identifier described above.

Sharing results

A creator can switch on a read-only link to a session's results. Anyone who has that link can see all results of that session, including written answers and names on a quiz leaderboard, but cannot answer or change anything and does not see the join code. The creator can switch the link off at any time, and it stops working if the session is deleted.

Cookies and local storage

We use only what is strictly necessary: a sign-in cookie for creators (and for visitors who open the home page, so the Google sign-in can be protected against forgery) and one identifier in participants' local storage. We do not use advertising or analytics cookies. Google's sign-in button loads from Google and is subject to Google's own privacy policy. Fonts load from Google Fonts.

How we use data

Only to run the service: show results to the person running the session, let creators export or delete their data, keep the service secure, and fix problems. We do not sell data and we do not use it for advertising.

How long we keep data

Sessions that are not used for 90 days are deleted automatically together with their questions, answers and nicknames. Creators can delete any session at any time. Security log entries are deleted after 180 days.

Your choices

• Download all of your data (JSON) and delete your account from your dashboard. Deleting your account removes all your sessions and results.
• Participants: clear your browser's site data to drop your identifier. To ask about a particular answer, contact the person who ran the session.
• Other requests: contact us at the address above.

Service providers

The service is hosted on a web hosting provider (Hostinger) and uses Google for sign-in. Data may be processed in the countries where these providers operate.

Security

Connections use HTTPS. Creators can only access their own sessions. No system is perfectly secure, so please do not use the service for highly sensitive information.

Children

The service is not directed at children. Creators who run sessions for minors are responsible for having the permissions their organisation or local law requires.

Changes

If we change this policy, the date above changes. Significant changes will be announced on the home page.