Privacy

1Who is responsible

Plauso is run by Nordkod Media AB. We are the controller for the data about you as our customer: your account, your order, your invoice and your contact with us.

Company

Nordkod Media AB

Company registration number

559591-6759

VAT number

SE559591675901

Address

Bultgatan 38, 442 40 Kungälv, Sweden

Service

plauso.app

Contact

support@plauso.app

2Two roles, kept apart

For your own customers' details, you are the controller. You met them and you decide who gets the request. We are your processor and handle the details only according to what you do in the service.

As a processor we do nothing of our own with them. We do not sell them, do not lend them to another customer, and do not use them to train any model. If one of your customers wants to know what is stored, we help you answer, and if data leaks we tell you without undue delay.

The terms for that processing, the data processing agreement, are in the terms of service and apply from the moment you create an account. They say what we may do with the data, how we protect it, how we help you and what happens when the agreement ends.

3What we store about you and your business

• Your account: business name, email address, country and language, text sender name, and your review profiles: for Google only the profile's place_id, for other platforms the link.
• Your team: the email addresses of the people you invited and the role each one has.
• Payments: which plan you have, texts you bought, and the basis for the invoices. Card details sit with Stripe and never pass through us.
• If you order signs or print: order number, what you bought, the delivery address and the basis for the invoice.
• The trial: when it started and ends, and a one-way hash of the email address so the same address cannot try twice.
• Integrations: the key or approval from a system you connected, sealed and never shown again, and when we last fetched from it. Of what we fetch, we keep only the first name and contact detail of customers to ask.
• Google Business Profile, if you connect it: the Google account's email address and Google's id for the account, which location you chose, the key Google gave us (sealed), your consent with time and text, and our log of what we changed in the profile. What we fetch from the profile, and how long it is kept, is in the section on Google Business Profile.
• Directory check: the business name, address, phone and web address you typed in, and which directories you ticked off.
• Visibility: the competitors you chose (only their place_id), the questions you asked in the AI search check with the answers' recommendations and sources, and the results of the map ranking.
• The monthly report: whether you want it, who in your team chose it, extra recipients you added, and the logo you uploaded.
• Profile check: we only fetch the home page you enter and store nothing from the check itself.

4What we store about your customers

• Customers you add (by hand, from a file, in the app, from a connected system or through a booking): first name and mobile number or email address, when and where they came in, and your confirmation that they bought from you.
• The sending: when the request and any reminder went out, with which template and to which of your profiles the link led, whether they arrived, whether and when the link was opened, and whether the recipient opted out.
• The sending log: a hash of the contact detail (never the number or address in the clear) that keeps track of the 90-day block and the opt-outs. The hash is unique to your account, so nobody can see that the same person exists at another business.
• Bookings through your website with us: name, phone or email, address, service, requested time, the message, whether the customer wants a RUT or ROT deduction, and the customer's own choices in the form: no to the review request and yes to a reminder to book again.
• Your short link and QR code: number of clicks per day and channel. We store no IP addresses.
• Google reviews, if you connected your Business Profile: the reviewer's display name, the rating, the text and the reply, encrypted for at most 30 days and never in the backups. We never match a Google review with the customers you added, and a review never affects who gets the request or where it leads.

5The request, autopilot and the link

With autopilot on, the service sends the request by itself to customers who are added, after the delay and up to the daily limit you chose. It does exactly what the Send now button does, with the same rules: never between 21:00 and 09:00 for the recipient, never the same person twice within 90 days, and at most one reminder. Before it is switched on for the first time, you confirm that the contacts bought from you, that you don't pick them by what you expect them to think, that everyone gets the same question and that they can say no. The confirmation is stored with the time and the version of the text.

The link in every text and email is unique to the recipient: a short address with eight random characters. It contains no name, no number and no email address, and the code is not derived from any of them. When the customer opens the link they are sent straight on to your profile, and we note that the link was opened and when. That is all: no IP address, no cookie, nothing about the device.

That fact is used for two things: someone who has already opened gets no reminder, and you see in your account who opened and how many per channel. Previews in messaging apps and email scanners are not counted. Whether the customer then writes a review, we cannot see. The link works for 120 days after the latest message; when it was opened stays on the customer's row for as long as the row exists.

If you share your requests between several profiles, the choice of review site is logged: on the customer's row, which profile the link led to, the version of the plan and the random draw; and in a log, the plan's shares and reasons, so that it can be shown afterwards that the choice was blind. No new detail about the customer is stored, and the choice never reads the customer's name, contact details, source or earlier answers. The plan never stores a number of reviews or a rating.

6Bookings and rebook reminders

When someone books through your website with us, the booking is stored in your account, and the customer gets a receipt, a message when you confirm or decline, and a reminder the day before. Right in the form the customer can decline the review request, and then no request is queued.

The rebook reminder tells a customer it is time to book again, and it goes only to someone who ticked the box for it in the booking themselves. The box is never pre-ticked, and neither you nor we can tick it for the customer. We store when the customer said yes, which text they saw, and after how long the reminder was to go. It goes once, by text or email, and not at all if the customer has already booked again.

The reminder has its own opt-out, separate from the review requests: a no to one does not affect the other. An opt-out is stored as a hash of the contact detail.

7The monthly report

On the 1st of every month we email the account owner a summary of the previous month: how many got the request and opened the link per channel, reminders, the queue, texts, clicks on the short link, bookings, the latest AI search check and map ranking, plus one tip. The report holds only numbers and your own questions, never a customer's name or contact detail.

Team members get the report only if they choose it themselves, and on Pro you can add up to 3 extra recipients. Every recipient has their own link in the report to stop with one press, without signing in, and the owner can also switch it off under Settings. An extra recipient who stopped is stored as a hash, so they are not added again by mistake.

The report is also a page in your account, with the same numbers as the email. If you connected your Business Profile, the report links to the numbers from Google in your account; they are not in the report and are not stored with it.

8The Plauso app and notifications

The app is Plauso in your browser, placed on the home screen. It stores nothing from the account on the phone (no customers, no pages), so a lost phone does not carry the customer list with it.

If you add a customer from your phone's contacts, the phone opens its own list, and only the contact you choose is read. Of that contact, the first name and one number or address are sent to your account, nothing else.

When you turn notifications on we store, per device: the address your browser's push service gave the device, two keys to encrypt the notification, which notifications you want, the language, a plain description such as “Chrome on Android”, and who in your team turned them on. A notification says what happened, never a customer's number or address, and only your device can read it. A notification about a new Google review can also carry the rating, the review and the suggested reply, so that you can read and publish straight from it.

If you turn notifications off under Settings, we delete the device's details straight away. If you turn them off on the phone, or remove the app, we delete them the next time we try to send and the push service answers that the address is gone. If someone leaves your team, notifications stop going to their devices.

9The reply assistant and other AI suggestions

When you paste in a review and ask for reply suggestions, the review is sent to Anthropic together with the rating, the tone you chose, your business name, who is replying (name and role), what you wrote about the business under AI replies, and the signature and contact route you want to end with. The review may contain the reviewer's name. Anthropic writes the suggestions, and we show them to you.

If you connected your Business Profile, Google reviews go to Anthropic the same way, with text, rating and the reviewer's display name: when you ask for suggestions, by themselves for every new review from Start, and when an auto-reply is to be written if you switched that on.

A review you paste in is not stored, and neither are the suggestions or the rating. The only thing stored about them is how many suggestions the account has had this month. Your AI reply settings (the tone, who is replying, the signature, the contact route and what you wrote about the business) are stored on the account until you change them or delete the account, and are included when you export your data. Suggestions for Google reviews are kept encrypted for at most 30 days, outside the backups, and are written with the same settings so that they can be written while you are not signed in.

The same goes for profile texts, posts, the website draft and the AI search check: only what you write in the form yourself, your business name and your town go to the language model, never your customer list. Under Anthropic's terms for business customers, the content is not used to train their models.

If you share a review as an image, the image is drawn in your browser. Neither the review nor the name is sent to us.

10If you sign in with Google

If you choose Google instead of waiting for a code by email, we ask Google for two things: openid and email. The first is what makes it a sign-in at all, the second is what tells us which address you are signing in with. We do not ask for your name, profile picture, contacts, Gmail, Calendar or Drive, and what we do not ask for, we cannot receive.

For the sign-in we also do not ask for the right to reach anything at Google once you have left. The permission applies at the moment of signing in, and no longer. The connection to your Business Profile is a separate permission, set out in the next section.

Here is everything we get, line by line, and what happens to it:

11Google Business Profile, if you connect it

Connecting is optional, and only the account owner can do it. You are sent to Google and approve there that Plauso may manage your Business Profile. We ask for openid and email, so that we know which Google account was connected, and for business.manage. That permission gives both read and write access, and Google's Business Profile APIs offer none narrower.

This is what we fetch: which accounts and locations the Google account reaches, the location's details such as name, address, categories, opening hours, description, services, website and whether it is verified, the reviews with the reviewer's display name, rating and text, your replies and Google's review of them, your posts, Google's own suggested changes, the statistics on views, calls, direction requests, clicks and bookings, and the search terms per month.

We use it only for what you see in your account: showing and replying to the reviews, the profile check and the changes you approve, the posts, the numbers and the booking button. Emails about the connection only say that something happened, never what a review says.

We write to Google only what you or someone in your team approved with a press: a reply, a change to the profile, a post, the booking button or the website link. The exception is auto-replies, which you switch on separately with a consent of their own and which only answer new reviews rated 4 or 5. We never revert Google's own changes by ourselves, and you get word of our changes within 48 hours.

Everything we fetch is stored encrypted for at most 30 days, kept out of the backups and cleaned out every day. We build no history of ratings or numbers: the “Since you started with Plauso” view is worked out from Google each time you look. Beyond that we keep only what the connection needs: the Google account's address and id, which location you chose, the key Google gave us (sealed and kept out of the backups), your consent and our own log of what we changed, without text.

The reviews go to Anthropic for reply suggestions, as the section on the reply assistant describes. The search terms stay with us, except when you choose one of them yourself as a search phrase in the map ranking: then the phrase goes to DataForSEO as in every measurement, and the measurement is stored as your own. No other customer sees your data from Google, and we never compare it with anyone else's.

You can disconnect whenever you like, under Google profile in your account. We then revoke the access at Google and delete what we stored from the profile at once, and the same happens when the account is deleted. Revoking can cover all of Plauso's permissions for that Google account, including signing in with Google if you use it, and then you approve it again the next time you sign in. If the same Google account is connected to another Plauso account, we do not revoke, and only remove the connection here.

12Limited use of Google user data

Google's User Data Policy sets four requirements on what an app may do with data from Google. We follow them, and here is what they mean here:

• The data is used only for features you see and use yourself: the sign-in to sign you in, and a connected Business Profile for the reviews and replies, the profile check, posts, numbers and the booking button in your account. What we fetch from the Business Profile is stored encrypted for at most 30 days, and if you disconnect the profile it is deleted at once.
• We do not pass it on, with one exception you agree to when you connect the profile: the reviews go to Anthropic, which writes the reply suggestions. Nothing goes to ad networks, data brokers or analytics suppliers, and nothing is sold. Your email address leaves us only when we email you at it.
• No human sits and reads it. Your address appears in your own account, and reviews and other data from the profile are seen only by you and the people you invited. We look only if you explicitly ask us to in a specific case, if it is needed for security, such as investigating a fault or abuse, or if the law requires it. Never as a list someone browses.
• We do not sell it, and do not use it for advertising, retargeting or credit scoring. No AI model is trained on data from Google, neither by us nor by Anthropic, whose terms for business customers do not allow what we send to be used for training.

13Google Maps, ratings and competitors

When you choose your business profile in the place search, the search text you type goes to Google and you point yourself out in the list. Google Maps is written under the list, as Google's terms require. Of everything Google answers with, we store a single field: place_id, the profile's id. The name and address in the list are shown on screen and thrown away. The same applies when you choose competitors.

The rating and the number of reviews, yours and those of the competitors you chose, we do not fetch from Google Places but through DataForSEO, which reads these public details from Google. DataForSEO is sent the place's place_id and, if that gives no answer, your business name for an ordinary search. A fetched rating is never shown once it is older than 12 hours, and is then cleaned away. We build no rating history, although the morning backup can pick up a rating that sat in the cache at that moment; it goes when the backup is pruned. If the fetch does not go through we show nothing rather than an old number. With needs-based routing, your own number of Google reviews is also read every morning to work out the shares. The number is used only in that calculation and follows the same limit: routing stores shares and reasons, never the number or the rating.

The map ranking on Pro asks DataForSEO where your business lands for a search phrase, seen from a grid of points around you. We get the centre point from Google Places. The positions are stored as your own measurements.

The link that takes your customer to the review box is built from place_id the moment someone clicks. That is not stored either.

The place search is Google Maps content, and when you use it the Google Maps End User Additional Terms of Service (maps.google.com/help/terms_maps) and the Google Privacy Policy (policies.google.com/privacy) apply as well.

14If you sign in with BankID

The BankID sign-in goes through Idura, who own the connection to BankID. From there we receive your Swedish personal identity number, and it never leaves that part of the code in the clear. What gets stored is a keyed hash of the number, which can only be compared against itself and not reversed.

So we never store your personal identity number, neither in storage nor in a cookie. BankID gives us no email address, so we ask for one and confirm it with a code.

15Why, and on what basis

The account, the sending, autopilot, the monthly report and what you order are needed to deliver what you signed up for. The basis is the agreement between us.

Notifications on your phone are sent only once you have said yes in the browser, and you can withdraw that whenever you like.

Invoice records we keep because Swedish accounting law requires it. Operational logs, abuse limits and the hash that stops one address trying twice we keep so the service stays safe and fair; there the basis is our legitimate interest in running it.

For your customers' details you choose the basis, because you are the controller. The service helps you keep to it: the customer can decline already in the booking, every message carries an opt-out, and the rebook reminder requires the customer's own yes.

The connection to your Business Profile rests on the agreement and on your own choice to connect it and approve it at Google. Auto-replies rest on a consent of their own. You can withdraw both whenever you like.

We do not use any of it to profile you or to make automated decisions about you.

16Who sees the data

We run nothing in a server room of our own. The suppliers below see data, and only the part they need for what they do. The list is the whole list: a supplier not on it is not switched on. The fuller version is in the sub-processors document.

17Transfers outside the EU and EEA

Several of the suppliers are American companies, and the service runs in Vercel's cloud without being tied to a region inside the EU. So expect data to be stored and processed in the United States.

Such transfers rest on the protection each supplier commits to in its own data protection terms: the European Commission's decision on the EU–US Data Privacy Framework, for companies that have joined it, or the Commission's standard contractual clauses. If you want to know what applies to a particular supplier, write to us and we will show you where it is stated.

18How long

We keep the account and your customers' details while you use the service. Customer rows stay, so the same person does not get the request twice and you can see the history. If you request deletion under Settings, or write to us, we remove the account, the customers and the bookings once we have confirmed that it is you.

Everything we store is backed up every morning to the same private storage, so that a mistake on our side cannot wipe your account, except what we fetched from your Business Profile and the key to it. Backups are pruned: the last two weeks are kept, and the first of each month for 3 months. A deleted account therefore remains in backups already taken until they are pruned, at most 3 months later. But we never put back an account deleted at your request.

Some things have their own times. The link in a message works for 120 days after the latest message, a fetched rating is shown for at most 12 hours, what we fetched from a connected Business Profile is kept for at most 30 days, and the details of a device with notifications disappear when you turn them off.

An opt-out we keep as a hash for as long as the account exists, so the person never gets the request again. The trial hash remains even after a deletion. It says only that the address has already tried.

Two hashes of the business's Google place also remain after a deletion: one for the free requests and one for the trial. They stop the same business from getting new free requests or a new trial by signing up with a new email address. The hashes cannot be turned back into the place.

Invoice records we must keep for seven years under Swedish accounting law, even if you close the account. There the law weighs heavier than a deletion request.

Your short link keeps pointing at your profile until you ask us to close it, so signs you already handed out do not stop working.

19How we protect it

The storage is private and reached only with a key that sits in the running environment, never in a browser. Signing in rests on a signed cookie, and the code we email is tied to the browser that asked for it, so a forwarded email signs nobody else in.

Secrets such as personal identity numbers and sign-in codes are stored hashed, not in the clear, and the logs must never contain them. Keys to systems you connected are stored sealed and never shown again, not even in an export. That includes the key to your Business Profile, and what we fetch from it is stored encrypted. If a secret leaks anyway, we tell you without undue delay.

20Cookies

The site uses no tracking cookies. Which cookies exist, what else is kept in the browser, and why none of it needs consent is on the cookie page.

21Your rights

You can ask what data we hold about you, have it corrected or deleted, have it moved, and object to its use. Write to support@plauso.app and we will answer.

If you signed in with Google or connected your Business Profile, you can also remove Plauso's access at any time inside your Google account, at myaccount.google.com/permissions. The Google button and the profile connection then stop working, but the account remains and the code by email works as usual.

If you think we handle your data wrongly you can complain to the Swedish authority, imy.se, or to the data protection authority in your own country. If you are a customer of someone using Plauso, go to the business that asked you. They are responsible for the data about you. If you only want to stop receiving messages, the link in the text or email is enough.

Company

Nordkod Media AB

Company registration number

559591-6759

VAT number

SE559591675901

Address

Bultgatan 38, 442 40 Kungälv, Sweden

Service

plauso.app

Contact

support@plauso.app