Privacy Policy
This policy describes how Luviamo (the “Service”) collects, uses, retains, and shares personal data. Luviamo is a marketing lifecycle platform for Nordic small and medium-sized businesses: ideation, planning, content creation, publishing, and analytics in a single application.
1. Data Controller
Innovasystems Oy
Business ID: 3639849-5
Postal address: Pilotinkatu 48, 33900 Tampere, Finland
Privacy contact: tietosuoja@luviamo.app
Contact person: Petri Korhonen
2. Personal data we process
We process the following data arising from use of the Service:
- User account: email address, name, password hash (unless you use OAuth-only sign-in), role, language preference, creation time, notification settings, and records of your marketing permission and of your acceptance of the terms and the data processing agreement.
- Organization: company name, business/VAT ID, subscription plan, and Stripe customer and subscription identifiers (no card data).
- Security log (audit log): actor, IP address, user agent, and action metadata. Purpose: abuse prevention and security (GDPR Art. 32).
- Newsletter subscribers (Messaging module): recipients that your organization imports or who join through a signup form: email address, subscription status, name and grouping labels (tags) where given, and consent details (time, source, signup channel and IP address). These are your own contacts, which we process on your behalf.
- Sessions: refresh tokens in the database together with the sign-in IP address and user agent. Purpose: session management and abuse detection. A token expires in 7 days, and expired or revoked rows are deleted automatically after 90 days.
- Sign-in identifiers (OAuth): if you sign in with Google or Microsoft, we receive your email address, name and account identifier from the provider. We never receive your password.
- Media: images and media files you upload, stored in object storage (R2).
- Brand voice: the descriptions and example texts you save in a brand voice profile (see section 6).
- Enquiries and demo bookings: name, email address, the content of your message and the time of the booked meeting. Created when you contact us by email or book a slot on the “Book a demo” page.
3. Purposes and legal bases
- Providing the Service (account, content creation, publishing, reporting) — legal basis: contract (Art. 6(1)(b)).
- Security and abuse prevention (audit log, rate limiting) — legitimate interest (6(1)(f)).
- Luviamo’s own customer communications and marketing based on the voluntary opt-in given at registration or in settings — consent (6(1)(a)). You can give or withdraw consent at any time in the application (Settings → Privacy) or by contacting tietosuoja@luviamo.app.
- Feedback survey after the trial — if your trial ends without a subscription, we may send one feedback survey by email (why you did not continue, what was missing). Legal basis: legitimate interest (6(1)(f)), improving the Service. This is not marketing, and you can decline by replying to the message or by contacting tietosuoja@luviamo.app.
- Billing and subscription management — contract and legal obligation (accounting).
- Sending newsletters on your behalf — you act as the controller for your own contacts; Luviamo is the processor.
- Responding to enquiries and arranging demo meetings — steps taken at your request prior to entering into a contract (6(1)(b)).
4. Google user data (Google Analytics 4 and Google Ads)
If you connect your own Google account, Luviamo reads your reporting data on a read-only basis. We never modify, create, or manage your accounts, campaigns, or settings.
What data is retrieved
- Google Analytics 4 (Data API): sessions, users, conversions, and traffic source breakdown. The Admin API is used to list properties so you can select the property to report on.
- Google Ads: campaign performance — impressions, clicks, cost, conversions, and conversion value. The account list is retrieved so you can select the account to report on.
How the data is used
The data is displayed back to the users of your own organization in the Track view and PDF reports. If the weekly report is enabled, it is emailed to the organization’s owners. It is not used for anything else and is not combined with other customers’ data (per-organization isolation).
Retention, sharing, and deletion
- Account-level aggregate metrics are stored in the organization database to provide the Service (trends, comparison). They are deleted when the connection is removed (Settings → Channels) or when the organization account is deleted; Luviamo then also deletes the Google token from its database. The access granted by your Google Account stays in place at Google, because other Luviamo connections made with the same Google Account, including in other organizations, may use it. You can remove the access at any time in your Google Account settings. Doing so disconnects every Luviamo connection made with that Google Account.
- Google data is not shared with any third party or with AI. This is verified in code: only a derived, de-identified numeric performance-index value is sent to AI — no raw data, account identifiers, source breakdown, or personal data.
- OAuth refresh tokens are stored encrypted with AES-256-GCM; they are never returned to the browser or written to logs. Access tokens are derived at fetch time and not stored.
- When you disconnect a channel, the integration and its tokens are deleted.
- The performance index derived from all channels (a 0–100 score and its components) contains no raw Google data. It is kept for up to 25 months and is removed when you disconnect a channel.
Luviamo's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Meta data (Facebook, Instagram and Threads)
If you connect your Facebook Page and its linked Instagram Business account, or your Threads profile, we process for publishing and reporting purposes:
- Access tokens: the Page access token and a long-lived User access token, which is used to renew the Page token and to read advertising data. Both are stored encrypted with AES-256-GCM on the server and are never sent to the browser or written to logs. The User access token is deleted immediately when Meta notifies us that the app was removed, and otherwise in the nightly clean-up once no connection uses it.
- Account information: Facebook Page ID and name, Instagram account ID and username, the ID of the ad account you select, and an app-scoped user ID (for webhook mapping). For a Threads profile we store its ID, username and a long-lived access token, encrypted like the other tokens and renewed before it expires.
- Published content and its metadata (posts), which you publish on your own initiative.
- Insights: follower, reach and engagement figures for the Page and the Instagram account, the follower count of the Threads profile, and post statistics such as impressions, reach, reactions, comments, shares, saves, clicks and video views. For Threads posts, views, likes, replies, reposts, quotes and shares are retrieved; Threads does not report reach. For posts published from Luviamo, the text and image address are also retrieved from the platform for the Published view.
- Post comments: comments on posts published from Luviamo and their replies (the commenter's name or username and platform user ID, text, time, like and reply counts and hidden status), so that you can read them on the post card in Luviamo without leaving for the platform. Comments are the commenters' data, and we process them on behalf of your organization: your organization is their controller and Luviamo the processor (data processing agreement). They are shown only to the users of your own organization and are not processed with AI. A comment is deleted from Luviamo when the post is deleted or moved to the trash or the connection is removed, within a day of the comment disappearing from the platform (for example, its author deleted it), and at the latest 12 months after the comment was posted. When you reply to, hide or delete a comment from Luviamo, Luviamo sends your reply or the hide or delete request to the platform at your request and records the action (who, when, which comment) in the security log; the reply text is stored only as your own comment on the post card, and a deleted comment is also removed from Luviamo.
- Advertising data (Meta Ads): campaign names and spend and performance figures (e.g. impressions, reach and clicks) from the ad account you select. Luviamo only reads advertising data and does not create or change ads.
Insights and advertising data are shown to the users of your own organization in the Track view and in reports. Page, account and advertising figures are kept for up to 25 months and are deleted when the connection is removed. Statistics for posts published from Luviamo are kept with the post for up to 25 months.
When you remove the app from Facebook or Threads or request data deletion, Meta sends a signed request to our callback URL. We verify the signature (HMAC-SHA256) and delete the stored connection data (the encrypted tokens and the account linkage), the Page, account and advertising figures retrieved from Meta, and the comments retrieved through the connection. See data deletion.
6. AI (content creation and speech recognition)
We use Anthropic’s AI to assist with content creation. Only the following is sent to the AI:
- your own content-creation input (ideas, briefs, brand voice) that you provide; and
- a derived, de-identified numeric performance-index value for the analytics summary.
We do not send Google or Meta raw data, email addresses, access tokens, or account identifiers to the AI. The AI produces suggestions that the user reviews and edits; this is not automated decision-making producing legal effects within the meaning of GDPR Art. 22.
Brand voice example texts. When you save example texts in a brand voice profile, Cloudflare Workers AI (model bge-m3) converts them into numeric vectors. The vectors are stored in a Cloudflare Vectorize search index together with the example text (up to 1,200 characters per example), and the index is isolated per organization. They are used to pick the examples that best fit each piece of content for the AI. The vectors are deleted when you delete the profile or when the organization is deleted.
Dictation (speech recognition). When you start dictation with the microphone button, your browser asks for microphone permission and your speech is sent in short chunks through Luviamo’s server to Cloudflare Workers AI speech recognition (Whisper), which turns it into text. The audio is processed only for the duration of recognition: no recording is stored by Luviamo or by Cloudflare, and only the recognised text remains in your document or text field, where you can edit it. You choose the dictation language yourself.
AI assistant connector (Claude). You can connect your own AI assistant (currently Claude) to Luviamo, after which the assistant can, at your request, read your organization’s data: your name, email, role, the organization and its plan, connected channels, post texts and figures, campaigns, brand voice, the Analytics summary, Meta ad spend and results, and the budget. The connector only reads data, and it does not pass on Google Analytics or Google Ads data or the data of people who comment on your posts. You connect by signing in to Luviamo and approving the connection separately. The data is transferred to the assistant’s provider, which processes it under its own terms; Luviamo is not its processor. The restriction above (no Google or Meta raw data) applies to Luviamo’s own AI, not to an assistant you connect yourself. The access token is valid for one hour, and the connection renews for at most 30 days (it ends after 14 days of inactivity). Every assistant request is recorded in the security log (tool name and time, not the content of the requests). You can revoke the connection at any time under Settings → Sessions, and Sign out everywhere revokes all assistant connections. The connection also ends when you change your password or your account is deleted, and the connection data is deleted with the account.
7. Subprocessors
We use the following subprocessors. A data processing agreement (DPA) under GDPR Art. 28 is in place with each — where the name is a link, it opens that subprocessor's DPA. Transfers outside the EU/EEA are covered by the EU Standard Contractual Clauses (SCC).
| Subprocessor | Role | Data processed | Location / transfer |
|---|---|---|---|
| Cloudflare | Hosting (Workers, Pages, D1, R2, KV), bot protection (Turnstile), speech recognition and text vectorization (Workers AI), and a search index (Vectorize) | All application data, media and sessions; brand voice example texts as vectors; dictation audio only for the duration of recognition | Database and media in Europe (Cloudflare’s Eastern Europe region); KV cache, Workers AI and Vectorize on Cloudflare’s global network · SCC; no audio is stored |
| Anthropic | AI (content creation) | Your own content input + de-identified index value | USA · SCC |
| Stripe | Payments and subscriptions | Billing email address, organization or user name, and customer and subscription IDs (card details are handled by Stripe, not Luviamo) | USA/Ireland · SCC |
| Resend | Transactional and newsletter email | Recipient email + message content | USA · SCC |
| Meta | Social publishing (on your initiative) and reading Page, post and advertising statistics | Content and media to publish; we receive insights and advertising data (see section 5) | USA/Ireland · SCC |
| Source of analytics data (read-only) | We send no personal data; we receive reporting data | — | |
| Google Workspace | Email, calendar and demo bookings | Name, email, message content and meeting time from enquiries and bookings | EU/USA · SCC + EU–US DPF |
| Microsoft | Sign-in with a Microsoft account (if you choose it) | Email address, name and account identifier | EU/USA · SCC |
| Backblaze | Backups (encrypted, separate cloud) | Encrypted copy of the database | EU (Amsterdam, Netherlands) · SCC |
8. Data location and transfers
Application data (database) and media files are stored on Cloudflare’s European servers (Eastern Europe location region). In addition, a daily backup of the database is encrypted (AES-256-GCM) before transfer and stored with Backblaze in the EU (Amsterdam, Netherlands) in a separate cloud, so that an outage at a single provider cannot take out both copies. Only Luviamo holds the encryption key, so Backblaze cannot see the contents of the backup. Backblaze, Inc. is a US company, and its data processing agreement includes the EU Standard Contractual Clauses (SCC). Some subprocessors (Anthropic, Stripe, Resend, Meta, Google, Microsoft) operate outside the EU; those transfers are covered by the EU Standard Contractual Clauses (SCC). Dictation speech recognition and the vectorization of brand voice examples (Workers AI), and the search index (Vectorize), run on Cloudflare’s network under Cloudflare’s data processing agreement and the Standard Contractual Clauses; no audio is stored. Short-lived security data, such as the two-step sign-in challenge with its IP address, rate-limit counters and the status of Meta deletion requests, is held in Cloudflare’s KV cache, which replicates across Cloudflare’s global network. It expires automatically, within 90 days at most.
9. Retention periods
| Data category | Retention |
|---|---|
| Account and organization data | For the life of the account. After your subscription ends the account remains, but if you don't sign in for 6 months the account and its data are deleted (signing in keeps the account active; you receive an email warning about 30 days before deletion). You can also delete the account yourself at any time. After a deletion request there is a 30-day cancellation period during which you can cancel the deletion; after that the account is deleted permanently, and if you were the organization’s last member, so is the organization’s data. Data disappears from backups as the backup rotation progresses; see the “Backups” row |
| Security log (audit log) | 12 months |
| Post comments (third parties' comments on posts published from Luviamo) and the comment action log | Comments at most 12 months from posting. A comment that has disappeared from the platform is deleted within a day, and the comments of a deleted or trashed post are deleted in the daily cleanup. Comment action log (reply, hide, delete) 12 months |
| Analytics: channel aggregate metrics, advertising data, post statistics and the derived performance index | Up to 25 months. Channel metrics, advertising data and the performance index are also removed when the connection is removed, post statistics with the post, and all of it on account deletion |
| Email delivery logs (opens, clicks, bounces) | Removed on organization deletion |
| Sessions (refresh tokens, incl. sign-in IP and user agent) | A token expires in 7 days; expired or revoked rows are deleted after 90 days |
| Media (R2) | Until you delete the file or the account is deleted. A deleted file stays in the trash for 90 days before permanent deletion |
| Brand voice example texts (Vectorize) | Until you delete the profile or the organization is deleted |
| Marketing permission history (when permission was given and withdrawn) | Until the account is deleted, as proof of the permission |
| Integration tokens (OAuth) | Deleted on disconnect or deauthorize/deletion request |
| Backups (encrypted copy of the database) | Daily 30 days, weekly 12 weeks, monthly 12 months. Backups are encrypted and used for nothing other than restoring the service after an incident |
| Billing data | 7 years (accounting law). Invoices and payment records are held by Stripe, not in this service's database |
| Demo bookings and enquiries | Up to 24 months from the last contact, unless a customer relationship begins |
10. Your rights
You have the rights under GDPR Art. 15–22: access, rectification, erasure, restriction, data portability, and objection.
- Access and portability: you can download a machine-readable export of your data (Settings → Privacy); the download link is HMAC-protected and time-limited. As a customer, you can also export your newsletter subscribers as a CSV file (Messaging → Lists).
- Erasure: you can delete your account and organization; related data is deleted in a cascade. You can also disconnect any channel.
- Consent management: you give and withdraw permission for Luviamo’s marketing messages in settings (Settings → Privacy), and the change takes effect immediately.
To exercise your rights: tietosuoja@luviamo.app.
11. Security
Access tokens and sensitive identifiers are encrypted (AES-256-GCM); passwords are stored as hashes. Application secrets reside only on the server, never in the browser. Organizations’ data is isolated from one another through three-layer tenant isolation (query-level scoping, static analysis, and an integration test).
12. Cookies, analytics and embedded content
The application itself (app.luviamo.app) uses only strictly necessary session tokens for sign-in.
This marketing website (luviamo.app) uses Google Analytics 4 for visitor analytics only if you consent in the cookie banner. Nothing is loaded before you make a choice. If you choose "Necessary only", no analytics are used at all. Your choice is stored in your browser's local storage (localStorage), and you can change it at any time via the Cookie settings link in the page footer.
When analytics is allowed, Google Analytics collects information about how the site is used (e.g. page views and visited pages) with IP anonymisation. The data is processed by Google Ireland Ltd; transfers are covered by the EU Standard Contractual Clauses and the EU–US Data Privacy Framework.
The same consent also loads Google Tag Manager, through which the site may run marketing measurement tags such as Meta Pixel (Meta Platforms Ireland Ltd) and Google Ads and LinkedIn measurement. These measure advertising performance (e.g. which ad a visitor arrived from) and may set their own cookies. If you choose “Necessary only”, none of these are loaded.
Bot protection (Cloudflare Turnstile). The bot protection on the front page newsletter form loads only when you start filling in the form. Turnstile processes data about your browser and connection (e.g. your IP address) only to tell a person from a bot. This prevents misuse of the subscription you asked for and is not tracking. The same protection is used on the application’s sign-up and sign-in pages.
Booking a demo
You can book a demo slot on this site. The booking calendar is provided by Google (a Google Workspace calendar appointment schedule), and the booking is stored in Luviamo’s Google Workspace environment. When booking you provide your name, email address and the time you choose, plus anything you write into the booking form fields. The meeting is held on Google Meet.
The legal basis is steps taken at your request prior to entering into a contract (GDPR 6(1)(b)). We use the data only to arrange the meeting, to remind you of it and for related correspondence — booking a demo does not add you to any newsletter.
The calendar is third-party content: when it opens, your browser connects to Google and Google may set its own cookies. On the front page the calendar loads only after you click “Book a demo”, and on the booking page it loads with the page, because booking is that page’s entire purpose. In both cases this is a service you requested yourself, not tracking. Google’s own processing is described in the Google privacy policy.
13. Right to lodge a complaint
If you believe we process your data unlawfully, you may lodge a complaint with the supervisory authority: the Office of the Data Protection Ombudsman (tietosuoja.fi), Finland.
14. Luviamo’s own marketing communication (newsletter)
When you subscribe to Luviamo’s own newsletter from the marketing website (luviamo.app), Innovasystems Oy acts as the controller — unlike our customers’ own newsletters, where Luviamo is a processor (see section 2).
- Data processed: your email address and subscription status (confirmed / unsubscribed), plus the confirmation timestamp and IP address as proof of consent.
- Purpose: product news, tips and Luviamo marketing.
- Legal basis: consent (GDPR Art. 6(1)(a)). Subscription uses double opt-in: you receive a confirmation link by email and are not added to the list until you confirm.
- Unsubscribe: you can unsubscribe at any time via the link at the bottom of every newsletter. It is immediate and requires no sign-in.
- Retention: your address is kept until you unsubscribe; after that, consent records are retained as evidence that the communication was permitted.
- Your rights (access, rectification, erasure, etc.) are as in section 10. Delivery is via the sub-processor Resend (section 7).
15. Changes to this policy
We may update this policy. Changes are published on this page; the “updated” date and version number indicate the latest version.