# The Privatus Analytics mobile app > What the Privatus Analytics mobile app shows, approving testimonials in it, how you log in, push notifications, the app lock and signing a device out. The mobile app is a companion to the web app, for iPhone, iPad and Android. It shows your analytics and tells you when something happens. It is view only, with one exception: you can approve and reject testimonials in it. Everything else you do in the web app: adding sites, creating goals, editing alerts and managing your team. ## What it shows - **Your sites**, for every workspace you can open in the app. Switch site or workspace from the top of the menu. - **Each site's Overview** with the period, comparison, segment and filters you know from the web app. - **Uptime checks** and **alerts**. - **Testimonials**, with the ones waiting for your decision first. See [Approve and reject testimonials](#approve-and-reject-testimonials). - **The menu of the web app.** The app lists a report once it has a screen for it, under the same name and in the same place as on the web. A report the app has no screen for is left out of the menu. The app sells nothing. It shows no prices and has no upgrade button. A report that isn't part of the workspace's plan says "Not included in this workspace's plan" and nothing more. ## It is view only, except for testimonials No screen in the app creates, edits or deletes anything. The server enforces this too: the app's login can only read, so a request from it that would change something is refused with `403`. There are two exceptions: the app saves its own notification settings for the device, and it can approve a testimonial, reject it or return it to pending. Where the web app has any other button that changes something, the app has none. An empty list says to add the first one in the web app. ## Approve and reject testimonials Open **Testimonials** in a site's menu. The list starts on **Pending**, the testimonials waiting for your decision, with the number of them. **Approved** and **Rejected** show the rest. Each card has what the person wrote, their rating, their name and title and when it arrived. A video or audio testimonial is marked as one. Play it in the web app. - **Approve** and **Reject** are on every pending card and on the testimonial's own screen. One tap is enough, and there is no confirmation. - **Back to pending** is on an approved or rejected testimonial. - After each change a bar at the bottom offers **Undo**, which takes the testimonial back to where it was. You need a role that may edit testimonials (the `content.write` permission: Owner, Admin, Editor and Analyst have it, see [Roles](/docs/teams/roles)). With a role that only views, you see the testimonials without the buttons. A testimonial marked **Waiting for the monthly limit** can't be approved yet, in the app or on the web. It is safe, and it can be approved once it is released. See [the Inbox](/docs/testimonials/inbox). The app changes nothing else about a testimonial. Editing the text, tags, collections, pinning, the trash and changes to many at once are in the web app. ## Log in or create an account Tap **Log in** or **Create account**. Both open the Privatus Analytics website in your phone's browser, then bring you back to the app. 1. Log in the way you always do: your password, an email login link, a passkey, Google, GitHub, Apple or your company's single sign-on. If your account has two-factor authentication, you are asked for it here. 2. A page titled **Continue to the Privatus Analytics app** lists the workspaces you'll see in the app, and any that are not available with the reason. 3. Tap **Continue**. The browser closes and the app opens on your sites. **Cancel** takes you back to the app without logging in. **Create account** starts on the sign-up page instead, with the same options as [on the website](/docs/getting-started/create-account), and goes on to the same approval page once the account exists. If you choose an email login link, open the link on the same phone and in the same browser. If the link leaves you on the website instead of in the app, go back to the app and tap **Log in** again. The browser still knows you, so the approval page opens straight away. The login and sign-up pages the app opens carry only the logo, the form and a footer line with the Terms and the Privacy Policy. There is no workspace to pick and no access to choose. One login covers every workspace you may open. The app always gets read-only access, plus approving and rejecting testimonials when your role allows it. ## Which workspaces appear The app follows each workspace's [login rules](/docs/teams#workspace-security-settings), the same ones a browser follows. A workspace is left out, with one of these reasons on the approval page, when: | What the page says | Why | What to do | |---|---|---| | You logged in with single sign-on, which opens that workspace only | A login through a workspace's identity provider opens that workspace and no other | Log in to the app with your own login (an email link, your password, a passkey, Google, GitHub or Apple) to see the others | | Requires two-factor authentication | The workspace requires it and your account has neither an authenticator app nor a passkey | Set one up under **Account → Security** on the web (see [Two-factor authentication](/docs/teams/two-factor)), then log in to the app again | | Doesn't allow the way you logged in | The workspace's **Allowed login methods** leave out the method you used | Log in to the app another way | | Asks its members to log in again more often | The workspace's **Sign members out after** limit is shorter than the age of your login | Log in to the app again | | Your role in this workspace can't view analytics | Your role there has no permission to read reports | Ask an owner or admin of the workspace | The app checks again by itself, regularly while you use it: - A workspace you joined since you logged in appears. You don't have to log in again. - A workspace you left, or one whose rules your login no longer meets, disappears. A workspace that turns on **Require two-factor authentication** closes to the app at once if you have no second factor. If you have no workspace yet, the app says so. Add your first site on the website, on a computer, then come back to the app. ## Notifications The app can send push notifications on every plan, Free included. There is nothing to set up on the web: no notification channel and no alert rule for uptime. After you log in, the app asks **Turn on notifications?** You get a notification about the sites you can open: | Kind | When | |---|---| | **Uptime** | A check goes down, and again when it is back up. The "back up" notification replaces the "down" one | | **Alerts** | An alert triggers, and again when it resolves. Muted alerts send nothing. An alert about a new testimonial opens that testimonial | | **Site audit** | A site audit finishes, with the score and the number of new and fixed issues | | **Experiment** | An experiment ends, with the winner if there is one | | **Monthly event allowance** | The workspace has used 80% of the month's events, or has reached the limit. Owners and admins only, like the emails | Tapping a notification opens what it is about in the app. A member whose access is limited to some sites is only told about those sites. Notifications are written in the language of your phone when Privatus Analytics has it, and in English otherwise. ### Switch kinds and sites off Open **Settings → Notifications** in the app: - A switch for each kind in the table above. - Under **Sites**, a switch for each site. - **Turn off on this device** stops every notification to that phone or tablet. You stay logged in. The switches belong to the device, so a phone and a tablet can differ. A new site starts switched on. If notifications are blocked for the app in your phone's own settings, the app says so. Allow them there first. ### How they differ from alert channels App notifications go to your own devices and need no channel. **Browser push** is something else: a [notification channel](/docs/reports/alerts#channels) on Pro and up that an alert rule sends to, for members who turned on browser notifications on the Channels page. Email, Slack and the other channels work as before, whether or not anyone uses the app. ## App lock **Settings → App lock → Ask for Face ID or fingerprint** makes the app ask for your face or fingerprint each time it opens. The setting shows on devices that have one set up. The check happens on your device, and nothing about it is sent to us. ## Log out or sign a device out - **In the app:** **Settings → Log out**. Notifications to that device stop. - **From the web:** **Account → Security → Mobile app** lists every device where the app is signed in, with its name, when it signed in and when it was last active. **Sign out** ends that login at once. Use it for a phone you lost or sold. See [Account settings](/docs/dashboard/account-settings#security). Changing your password signs the app out on every device. A login that is not used for 90 days ends by itself. ## Delete your account **Settings → Delete account** opens the deletion form on the website in your browser. You may be asked to log in first. Type your email address to confirm, as on the web (see [Deleting your account](/docs/dashboard/account-settings#deleting-your-account)). Afterwards you are back in the app, logged out. A login through a workspace's single sign-on can't delete the account. Log in with your own login first. ## Privacy The app holds no analytics of its own about you: it has no tracking and no advertising code. To send notifications we store your device's push address, its language and time zone, and what you switched off. They are removed when you turn notifications off, log out or delete your account. The [Privacy Policy](/legal/privacy) has the details.