Nopsa.io · Data Haltuun Oy
Nopsa.io application privacy policy
Last updated: 13 October 2026
This Privacy Policy describes how nopsa.io ("we", "us", or "our") collects, uses, shares, and protects your personal data when you use the nopsa.io application and related services (the "Service"). We are committed to protecting your privacy and complying with the EU General Data Protection Regulation (GDPR) and other applicable data protection laws.
This update explains how our existing optional voice features use OpenAI. It does not introduce new uses of your data. You can continue using tasks, work hours, and invoices without voice features.
1. Data Controller
nopsa.io is the data controller for personal data processed through the Service. If you have questions or concerns about how we handle your data, contact us at:
Email: privacy@nopsa.io
nopsa.io, Finland
2. Data We Collect
We collect the following categories of personal data:
(a) Account Information
When you register, we collect your name, email address, and password (stored as a secure hash). If you register with Google Sign-In, we receive your name, email, and profile photo from Google.
(b) Business Profile Information
Optional information you provide, including company name, business ID, VAT number, address, phone number, and website.
(c) App Content
Tasks, projects, customer records, work hour entries, invoices, billing products, labels, filters, and other content you create within the Service.
(d) Payment Information
Subscription and billing data. Your payment card details are processed directly by Stripe and are never stored on our servers. We retain records of transactions, subscription status, and invoice history.
(e) Integration Data
When you connect third-party accounting software (Fennoa, Procountor), we store encrypted API credentials in our database. Calendar integration data (Google Calendar, Outlook) is processed to sync events. If you connect an AI assistant to nopsa.io (such as Claude via the nopsa.io connector), we store authorisation records (hashed access tokens and the granting account's identifiers) needed to maintain the connection you approved.
(f) Usage and Technical Data
Log data, device type, browser type, IP address, crash reports, and analytics data to help us improve the Service. Firebase Analytics may collect aggregated, anonymised usage statistics. If you accept analytics cookies, the Meta Pixel (Facebook) may also collect browser, device, IP address, and page-event data to help us measure the effectiveness of our marketing campaigns.
(g) Communications
If you contact us for support, we retain those communications.
(h) Optional Voice Features
When you use voice input, we process your recording and its transcript. Depending on the feature, we also send customer and project names, task identifiers or titles, and date, time, and language information to OpenAI to interpret your request. The task assistant includes summaries of up to 50 tasks: titles, due dates, completion status, priority, and associated customer and project names. This context accompanies task-assistant voice requests, including requests to create a task.
3. How We Use Your Data
We use your personal data to:
• Provide, operate, and maintain the Service.
• Create and manage your account and team memberships.
• Process subscription payments and generate invoices.
• Sync data with third-party integrations you authorise.
• Transcribe voice input, prepare task, work-hour, or invoice actions, and answer task questions when you choose to use voice features.
• Send service-related notifications (e.g., team invitations, billing alerts).
• Respond to support requests.
• Detect and prevent fraud, abuse, and security incidents.
• Comply with legal obligations.
• Improve the Service through aggregated, anonymised analytics.
• Measure the effectiveness of our marketing campaigns where you have accepted analytics cookies (via the Meta Pixel).
We do not sell your personal data to third parties.
We do not run advertising inside the Service itself, and you can opt out of marketing measurement at any time by rejecting analytics cookies in the consent settings.
4. Legal Basis for Processing (GDPR)
We process your personal data on the following legal bases:
• Contract performance: Processing necessary to provide the Service you have subscribed to (account management, task storage, billing).
• Legitimate interests: Security monitoring, fraud prevention, and service improvement, where these do not override your rights.
• Legal obligation: Retaining financial records as required by Finnish accounting law.
• Consent: Where we explicitly ask for your consent (e.g., certain optional integrations). You may withdraw consent at any time.
5. Data Sharing and Third Parties
We share your data only with the following categories of third parties, and only to the extent necessary:
(a) Firebase / Google Cloud
Our database (Firestore), authentication (Firebase Auth), hosting, and analytics infrastructure is provided by Google Firebase. Our Firestore database is located in Finland (EU). The locations used by other services depend on the provider and service. Google acts as a data processor under a Data Processing Agreement.
(b) Stripe
Payment processing. Stripe receives your payment card details directly. We share your name and email with Stripe to create customer records. Stripe's privacy policy applies to their processing.
(c) Mailjet
Email delivery service used to send team invitations and service notifications. We share only the email address and name required for delivery.
(h) Google Ads
With separate ad measurement consent, Google Ads receives ad click identifiers and a successful registration event with a hashed account identifier for deduplication. The _gcl_ cookies preserve attribution between nopsa.io and app.nopsa.io. The nopsa_ads_consent_v1 cookie shares this consent choice across both sites for 180 days. You can withdraw it in cookie settings on either site. Ad personalization remains disabled.
(d) Google (Sign-In and Calendar)
If you use Google Sign-In or Google Calendar integration, relevant data is exchanged with Google pursuant to your authorisation. Google's privacy policy applies.
(e) Microsoft (Outlook Calendar)
If you enable the Outlook calendar integration, relevant data is exchanged with Microsoft pursuant to your authorisation. Microsoft's privacy policy applies.
(f) Fennoa / Procountor
If you enable an accounting integration, customer and invoice data is transmitted to the respective provider. Their privacy policies apply.
(g) Meta Platforms (Facebook)
If you accept analytics cookies, we use the Meta Pixel to send pageview and conversion events from your browser to Meta Platforms Ireland Ltd. so we can measure the effectiveness of our marketing campaigns. When you complete a paid subscription via Stripe, we additionally send a server-to-server Purchase event to Meta via the Conversions API containing the purchase amount, currency, and a one-way hashed (SHA-256, irreversible) copy of your email address and account ID. The lawful basis for the server-side event is our legitimate interest in measuring marketing-campaign effectiveness for completed paid transactions; the hashed identifiers cannot be reversed to your underlying email or ID. Meta acts as a joint controller for this processing; their privacy policy applies (facebook.com/privacy/policy). You can withdraw browser-pixel consent at any time from the consent settings screen, and you can object to the server-side event by emailing privacy@nopsa.io.
(h) Anthropic (Claude AI assistant)
If you choose to connect your nopsa.io account to Claude using the nopsa.io connector, the task, project, and customer data you ask Claude to access is transmitted to Anthropic to fulfil your requests. This happens only after you explicitly sign in and approve the connection, and only for data your requests require. Anthropic processes this data under its own privacy policy (anthropic.com/legal/privacy). You can revoke the connection at any time from Claude's connector settings.
(i) OpenAI (Optional Voice Features)
We use the OpenAI API to convert recordings into text and interpret voice requests using the context described in section 2(h). Voice processing starts when you use a voice feature; ordinary manual entry does not invoke this processing. Data is sent over encrypted connections. Our voice service excludes recordings, transcripts, task context, and generated content from diagnostic logs.
OpenAI states that API inputs and outputs are not used to train its models by default, unless the API customer opts in to data sharing. Provider retention and international processing are described in sections 7 and 10. OpenAI's API data controls are documented at developers.openai.com/api/docs/guides/your-data.
(j) Legal Requirements
We may disclose data if required by law, court order, or governmental authority.
Apart from the marketing measurement described in (g), we do not share your data with any other third parties for marketing or analytics purposes.
6. Data Storage and Security
Our main application database (Firestore) is hosted in Finland (EU). The third-party processing described in section 5 also applies. We implement appropriate technical and organisational security measures, including:
• Encryption in transit (HTTPS/TLS) and at rest.
• Firebase Security Rules enforcing per-user data access controls.
• Role-based access within team accounts, enforced by server-side custom claims.
• API credentials for third-party integrations stored in encrypted form.
• Regular security rule reviews and access audits.
Despite these measures, no system is completely secure. We cannot guarantee absolute security of your data.
7. Data Retention
We retain your data for as long as your account is active and as long as necessary to provide the Service.
Financial and billing records are retained for a minimum of 7 years as required by Finnish accounting law (Kirjanpitolaki).
When you delete your account, we delete your personal data and app content within 30 days, except where retention is required by law.
Aggregated, anonymised analytics data that cannot identify you may be retained indefinitely.
For voice processing, OpenAI documents no application-state or abuse-monitoring retention for its audio transcription endpoint. For text interpretation, its standard abuse-monitoring logs may contain transcripts, context, and outputs for up to 30 days, unless longer retention is legally required. Retention depends on the applicable service and account controls. Tasks, work-hour entries, and invoices you save remain subject to our normal app-content retention.
8. Your Rights (GDPR)
As a data subject under the GDPR, you have the following rights:
• Right of access: You may request a copy of the personal data we hold about you.
• Right to rectification: You may correct inaccurate or incomplete data.
• Right to erasure: You may request deletion of your data (subject to legal retention obligations).
• Right to restriction: You may request that we restrict processing in certain circumstances.
• Right to data portability: You may request your data in a structured, machine-readable format.
• Right to object: You may object to processing based on legitimate interests.
• Right to withdraw consent: Where processing is based on consent, you may withdraw it at any time without affecting the lawfulness of prior processing.
To exercise any of these rights, contact us at privacy@nopsa.io. We will respond within 30 days. You also have the right to lodge a complaint with the Finnish Data Protection Ombudsman (tietosuoja.fi).
9. Children's Privacy
The Service is intended for use by adults (18+) in a business context. We do not knowingly collect personal data from children under the age of 16. If we become aware that a child has provided us with personal data, we will delete it promptly.
10. International Data Transfers
Our Firestore database is hosted in Finland. Providers described in section 5, including OpenAI and Stripe, may process data outside the EU/EEA. Voice processing is not restricted to the EU/EEA by our current integration.
International transfers are subject to GDPR requirements for a valid transfer mechanism, such as an applicable adequacy decision or Standard Contractual Clauses and any necessary additional safeguards. Contact privacy@nopsa.io for information about the transfer arrangements applicable to your data.
11. Cookies and Tracking
On the web, the Service uses cookies and similar local storage technologies for two purposes: (a) strictly necessary storage for authentication, language and theme preferences, and other functional app state; and (b) audience research / service improvement via Firebase Analytics (Google Analytics 4), which sets the "_ga" cookie and collects anonymised usage data such as a randomly generated cookie identifier, page views, and events.
Analytics and similar non-essential storage are off by default and only enabled after you give consent. We implement Google Consent Mode v2: until you accept, analytics_storage, ad_storage, ad_user_data, ad_personalization and personalization_storage signals are set to "denied", and no analytics traffic is sent. You can change your decision at any time from Settings → Cookie settings, and your choice is stored locally in your browser.
On native mobile and desktop platforms the Service does not use browser cookies. Firebase may use local storage mechanisms for authentication state persistence and performance, and Firebase Analytics may collect anonymised usage data using identifiers that do not personally identify you.
You can clear local storage, the consent decision, and authentication tokens by signing out of the Service or clearing your browser/app data.
12. Third-Party Links and Services
The Service may contain links to or integrate with third-party services. This Privacy Policy applies only to our Service. We encourage you to review the privacy policies of any third-party services you connect.
13. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by email or through a prominent notice in the Service at least 14 days before the changes take effect.
The updated policy will include a revised "Last Updated" date. Your continued use of the Service after the effective date constitutes acceptance of the updated policy.
14. Contact Us
For privacy-related questions, requests, or complaints:
Email: privacy@nopsa.io
General enquiries: legal@nopsa.io
nopsa.io, Finland
Data Protection Supervisory Authority (Finland):
Office of the Data Protection Ombudsman
tietosuoja.fi