Legal
Privacy policy
This Privacy Policy explains how Oplema ApS collects, uses, shares and retains personal data when you use oplema.com and the Oplema Service, and how you can exercise your rights.
Last updated
Oplema ApS ("Oplema", "we", "us" or "our") provides oplema.com and the Oplema products Strata, Vista, Cloud, Console, Echo and Elara (together, the "Service"). This Privacy Policy explains how we process personal data as controller and provides the information required by Articles 13 and 14 of the General Data Protection Regulation ("GDPR").
1. Who we are
The controller is Oplema ApS, a Danish company registered under CVR number 46635183, with its address at Byporten 8, 2700 Brønshøj, Denmark. You can contact us at hello@oplema.com.
Oplema is the controller for account, billing, website and Service-operation data, and for the use of Elara conversations for product improvement described in section 6. Otherwise, where a customer stores or processes personal data in the Service as Customer Content, Oplema processes that data as processor on behalf of the customer under the Data Processing Agreement, and the customer's own privacy notice applies to that processing.
In this Privacy Policy, "Customer Content" has the same meaning as in the Terms of Service and the Data Processing Agreement: data, files, projects, flows, dashboards and other content that you or the users of your account upload, store, connect, create or process in the Service, including data read through connectors and prompts and project context sent to Elara.
2. Scope of this Privacy Policy
This Privacy Policy applies to oplema.com, the sign-in and account pages and the Service, including Google sign-in, the Google connector and other connectors you authorise. It does not apply to third-party websites and services that you use through the Service, including connector providers, model providers you connect with your own API key or endpoint, and Paddle's checkout. Those are governed by their own terms and privacy notices.
The Data Processing Agreement governs the processing of Customer Content. The Terms of Service govern all other use of the Service. If a translation of this Privacy Policy differs from the English version, the English version prevails.
3. Processing on your device
Projects run in your browser by default. Files you open from your device and data you process locally stay on your device unless you save them to Cloud, run them as a hosted run or schedule, publish them, or send them to Elara or a connector.
Your browser's local storage and IndexedDB keep your local projects, version history and preferences on your device. Visiting oplema.com and using features that rely on our servers involve the processing described in section 4.
4. Personal data we process
Depending on how you use the Service, we process the following categories of personal data. We receive this data from you, from your device, and from the third parties named below. Section 5 sets out the purposes and legal bases.
Website
When you visit oplema.com, our servers and network provider process the technical data needed to deliver and protect the website, including your IP address, browser and device information, the pages you request and the time of each request. The website is hosted by Cloudflare and delivered through its global network, so this data may be processed at the Cloudflare location nearest to you.
Account
When you create an account, we process the account data you provide at sign-up, including your name and email address, your sign-in credentials, the region you choose, a record of your agreement to the Terms and your region confirmation (including the time, your IP address and browser information), your profile settings, a history of changes to the Share data for product improvement setting, your team memberships in Console and records of your use of the Service. If you follow a link that contains a referral code, we store the code in a cookie and apply it at checkout (see section 13).
Sign-in
You can sign in with email and password, Google or GitHub. If you sign in with Google, we receive your name, email address and Google account identifier from Google (see section 7). If you sign in with GitHub, we receive your GitHub user ID, your name or, if none is set, your GitHub username, and your verified email address from GitHub.
Use without an account
Without an account, you can use Strata, Vista, Cloud storage (within guest limits of 25 MB of files and 200 MB of projects) and connectors. We process the files, projects and connections you store or use in this way. Files and projects stored in Cloud without an account are deleted about 30 days after the guest session started, unless you create an account. Elara, sharing, publishing and schedules require an account.
Cloud
When you save projects or files to Cloud, or share or publish them, we store that content, which may include personal data, together with related metadata such as file names and sharing and publishing settings. Your account and Cloud data are stored in your region (see section 10).
Connectors
When you connect a data source, we store the connection tokens or credentials and process the data you or your flows read from or write to that source (see sections 7 and 8).
Elara
When you use Elara, we process what you write, Elara's responses and the parts of your project Elara needs to answer, which can include data from your project (see section 6).
Hosted runs and schedules
When you run a flow as a hosted run or on a schedule, we process the flow, the data it reads and writes, and the run history, including when each run took place, how long it took and whether it succeeded, failed or timed out.
Billing
Purchases are made through Paddle, which collects the payment and tax details it needs at checkout, including an optional VAT number. We receive information from Paddle about your subscription and purchases, such as the plan, billing period, amounts and transaction status, and we keep records of your usage balance.
Support and contact form
When you use the contact form, we process the topic you choose, your name, your email address and your message, and we use your IP address to limit abuse. When you email us, we process your email address, the content of your message, any attachments and our correspondence with you.
Cookies and analytics
We use Umami to count visits to the website and the Service, and how many visits lead to an attempt to message Elara without an account, a sign-up or a checkout, without cookies. Umami receives the page you visit without any query string except campaign labels, the referral link you arrived through when you sign up or start a checkout, the website that referred you (without its page address), your browser, operating system, device type, language and screen size, and your approximate location, which Umami derives from your IP address. Umami does not store your IP address or anything on your device. It combines your IP address and browser information with a value that changes every month into a pseudonymous identifier, so it can recognise repeat visits within a month but not across months.
We use strictly necessary cookies to operate the website and the Service. If you allow all cookies in the cookie banner, we use Google Analytics 4 and Google Ads conversion measurement, which process information such as the pages you visit, the campaign or ad click that brought you to the website, device and browser information, and identifiers stored in cookies (see section 13). If you have given consent, our servers also send purchase and refund conversion events, including amounts, transaction identifiers and the click and analytics identifiers stored in those cookies, to Google Analytics 4 and Google Ads.
5. Purposes and legal bases
We process personal data for the following purposes and on the following legal bases:
- Creating and managing your account, signing you in and providing the Service, including use without an account, Cloud, connectors, Elara, hosted runs, schedules, sharing and publishing. Legal basis: Performance of a contract (Article 6(1)(b) GDPR).
- Sending transactional email, such as email verification, password resets and messages about your account. Legal basis: Performance of a contract (Article 6(1)(b) GDPR).
- Managing purchases, subscriptions, usage balances and the sign-up credit. Legal basis: Performance of a contract (Article 6(1)(b) GDPR).
- Delivering and securing the website and the Service, including strictly necessary cookies, preventing abuse and fraud, and enforcing our Terms. Legal basis: Legitimate interests in operating a secure and reliable Service (Article 6(1)(f) GDPR).
- Responding to support requests and contact form messages. Legal basis: Performance of a contract where the request concerns your account (Article 6(1)(b) GDPR); otherwise legitimate interests in responding to enquiries (Article 6(1)(f) GDPR).
- Improving Oplema, including training and evaluating our models with Elara conversations while the Share data for product improvement setting is on. Legal basis: Legitimate interests in improving the Service (Article 6(1)(f) GDPR).
- Counting visits to the website and the Service with Umami, without cookies. Legal basis: Legitimate interests in understanding how the website and the Service are used (Article 6(1)(f) GDPR).
- Measuring website use with Google Analytics 4 and ad conversions with Google Ads. Legal basis: Consent (Article 6(1)(a) GDPR).
- Keeping billing and accounting records. Legal basis: Legal obligation under the Danish Bookkeeping Act (Article 6(1)(c) GDPR).
Where we rely on legitimate interests, you have the right to object as described in section 14. Where we rely on consent, you may withdraw it at any time.
6. Elara
Hosted models
Hosted Elara models are provided through OpenRouter and, for accounts in the EU region, also Eden AI. They route each request to the provider that runs the selected model. We have data processing agreements with OpenRouter and Eden AI, and have configured both not to use your prompts for training. Some model providers may keep requests for a limited period to detect abuse, as described in their terms, which are linked on the Model providers page.
Requests from accounts in the US East and US West regions are processed by providers in the United States. Requests from accounts in the EU region are processed by providers in Europe, which may include the European Economic Area, the United Kingdom and Switzerland. Requests from accounts in the Asia region are not subject to a location restriction and may be processed in any country, depending on the model and on which provider serves the request. The models available in each region, and where each is processed, are listed on the Model providers page.
Elara receives what you write and the parts of your project it needs to answer, which can include data from your project.
Your own API key or model endpoint
If you connect your own API key or model endpoint, requests go to the provider you choose under your own agreement with that provider. That provider's terms and privacy notice apply to its processing.
Product improvement
Your account has a setting, Share data for product improvement, which is on by default. When it is on, we may use your Elara conversations to improve Oplema, including to train and evaluate our models. You can switch it off at any time in your profile settings.
Data obtained through Google APIs is excluded from this use (see section 7).
7. Google
This section describes how we use information received from Google APIs through Google sign-in and the Google connector.
Google sign-in
If you sign in with Google, we request the openid, email and profile scopes and receive your name, email address and Google account identifier. We use this information to create your account and sign you in.
Google connector scopes
If you connect Google Drive, Google Sheets or BigQuery, we request the following scopes:
https://www.googleapis.com/auth/drive.file: read and write access only to the Google Drive files, including Google Sheets, that you pick in Oplema or that Oplema creates for you. We do not request access to your whole Drive.https://www.googleapis.com/auth/bigquery.readonly: read-only access to BigQuery.https://www.googleapis.com/auth/bigquery: requested optionally, when you choose to write to BigQuery.
We use these scopes to perform the reads and writes you or your flows request. Data read through the Google connector passes through our servers to your browser or hosted run.
Limited Use
Oplema's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
We do not use data obtained through Google APIs to develop, improve or train generalised AI or machine-learning models.
Revoking Google access
You can remove a Google connection in Oplema, which deletes the stored tokens, and you can revoke Oplema's access to your Google account at https://myaccount.google.com/permissions.
8. Connectors
OAuth connectors
You can connect the following services through OAuth: Google (Drive, Sheets, BigQuery), Microsoft (OneDrive), Dropbox, Airtable, Notion, HubSpot, QuickBooks and Xero. Each provider shows its own consent screen, and the access you grant there determines what we can read or write.
Credential connectors
You can connect PostgreSQL, MySQL, SQL Server, Supabase, Snowflake, Databricks and Stripe by providing credentials.
How we use connector access
Connection tokens and credentials are stored encrypted on our servers and used only to perform the reads and writes you or your flows request. Data read through connectors passes through our servers to your browser or hosted run. You can write data to Google Sheets, BigQuery, OneDrive, Dropbox, PostgreSQL, MySQL, SQL Server, Supabase, Snowflake and Databricks. Airtable, Notion, HubSpot, QuickBooks, Xero and Stripe are read-only: Oplema reads data from them and does not write to them.
Each connector provider processes data under its own terms and privacy notice. You can remove a connection in Oplema, which deletes the stored tokens or credentials, and you can revoke access in the provider's account settings, where available.
9. Recipients
We share personal data with the following categories of recipients:
- Service providers acting as our processors: Hetzner (servers and databases), Cloudflare (website hosting and delivery, DNS, network, TLS, file storage and backups), Fly.io (hosted runs and schedules), OpenRouter and Eden AI (Elara model routing) and Resend (transactional email). The model providers engaged by OpenRouter and Eden AI are their subprocessors. The current list of subprocessors, with their purposes and locations, is set out in Annex 3 of the Data Processing Agreement.
- Paddle: Paddle.com Market Ltd, United Kingdom, is our reseller and merchant of record. It processes payments, VAT and invoices as an independent controller, not as our subprocessor. Paddle's buyer terms apply to the payment, and Paddle's privacy notice applies to its processing.
- Sign-in providers: Google and GitHub, when you choose to sign in with them.
- Website analytics: Umami, which counts visits without cookies as our processor and stores the statistics in the European Union (see section 4).
- Google analytics and advertising services: Google Analytics 4 and Google Ads conversion measurement, only after you allow all cookies in the cookie banner.
- Providers you choose: connector providers you connect, and model providers you connect with your own API key or model endpoint.
- People you share with or publish to: "Anyone with the link" editor links let anyone who has the link edit, including people without an account. Published dashboards show data from your connectors and Cloud files using your connections, to everyone you publish to. You are responsible for whom you share with and what you publish.
- Authorities: public authorities, courts or other parties where disclosure is required by applicable law.
10. Regions and international transfers
When you create your account, you choose a region: US East (Virginia, United States), US West (Oregon, United States), EU (Germany) or Asia (Singapore). Your account and Cloud data are stored in that region. If you use Oplema without an account, any Cloud data is stored in the region we estimate to be nearest to you, based on your IP address. Certain processing takes place outside your region, as described in this section and in section 6.
Our servers and databases are hosted by Hetzner in Nuremberg (Germany), Ashburn (Virginia, United States), Hillsboro (Oregon, United States) or Singapore, according to your region. Cloud storage and backups are held on Cloudflare R2, within the European Union for EU accounts and, for other accounts, with a Cloudflare location hint for eastern North America (US East), western North America (US West) or Asia-Pacific (Asia). Cloudflare also hosts and delivers the website and provides DNS, network and TLS services through its global network. Hosted runs take place on Fly.io in Frankfurt (Germany), Ashburn (Virginia, United States), San Jose (California, United States) or Singapore, according to your region. Email is sent through Resend from Ireland, whatever your region. Elara requests are processed as described in section 6.
Personal data is transferred outside the European Economic Area where you choose the US East, US West or Asia region; where it is processed by recipients established outside the European Economic Area, including Cloudflare, Fly.io, OpenRouter, Resend and Umami in the United States and Paddle in the United Kingdom; where Elara requests from accounts in the Asia region are processed without a location restriction; and where you use Google sign-in or accept analytics and advertising cookies, in which case Google may process the data in the United States. These transfers rely on an adequacy decision or on the European Commission's Standard Contractual Clauses in our agreements with the recipients. You can request further information about these safeguards by contacting us.
11. Retention
We keep personal data for the following periods:
- Account data and Customer Content: While your account exists, until you ask us to delete it.
- Elara conversations and run history: We keep Elara conversations and run history with your account to operate, support and improve Oplema.
- Billing and accounting records: 5 years from the end of the financial year they relate to, as required by the Danish Bookkeeping Act.
- Support correspondence: Up to 3 years.
- Files and projects stored in Cloud without an account: About 30 days after the guest session started, unless you create an account.
- Analytics data: In accordance with Google's retention settings, up to 14 months.
- Umami visit statistics: Up to 2 years.
- Backups: Deleted data may remain in backups for up to 90 days.
Cookie durations are set out in section 13.
12. Security
We use technical and organisational measures to protect personal data, including TLS encryption in transit, encryption of stored connector credentials and API keys, isolated, short-lived machines for hosted runs, access controls, rate limiting and regular backups. These measures are designed to provide a level of security appropriate to the risk. They reduce, but do not eliminate, security risks.
13. Cookies and similar technologies
We use the following cookies:
(Necessary): Sign-in session. Duration: Until the browser closes; the session itself expires after 30 days.cm_session(Necessary): Stores your cookie choice. Duration: 180 days.oplema_consent(Necessary): Records consent withdrawals until they are processed. Duration: Until processed, at most 180 days.oplema_withdrawals(Necessary): Remembers the referral link you arrived through, so we can credit the referrer, apply its discount and label your sign-up or checkout in our visit statistics. Duration: 30 days.cm_ref(Analytics, with consent): Campaign attribution. Duration: 90 days.oplema_analytics(Advertising, with consent): Ad-click attribution. Duration: 90 days.oplema_advertising(Analytics, with consent): Google Analytics. Duration: Up to 180 days._ga,_ga_*(Advertising, with consent): Google Ads conversions. Duration: 90 days._gcl_au
Necessary cookies are required to operate the website and the Service and do not require consent. Umami does not use cookies or store information on your device. We use Google Analytics 4 and Google Ads conversion measurement only after you allow all cookies in the cookie banner. You can change your choice at any time through the Cookie preferences link.
Browser storage (local storage and IndexedDB) keeps your local projects, version history and preferences on your device.
14. Your rights
Subject to the conditions and exceptions in applicable law, you have the following rights:
- Access: to obtain confirmation of whether we process your personal data and a copy of it.
- Rectification: to have inaccurate personal data corrected and incomplete data completed.
- Erasure: to have your personal data deleted.
- Restriction: to have the processing of your personal data restricted.
- Data portability: to receive personal data you have provided to us in a structured, commonly used and machine-readable format, and to have it transmitted to another controller.
- Objection: to object to processing of your personal data.
- Withdrawal of consent: to withdraw your consent at any time, without affecting the lawfulness of processing based on consent before its withdrawal. You can withdraw consent to analytics and advertising cookies through the Cookie preferences link.
Right to object to processing based on legitimate interests. You have the right to object at any time, on grounds relating to your particular situation, to processing of your personal data based on our legitimate interests, including the use of your Elara conversations for product improvement. You can also switch off the Share data for product improvement setting in your profile settings.
To exercise your rights, including to request deletion or an export of your data, email hello@oplema.com from the email address associated with your account. We handle requests manually and respond within the time required by applicable law.
You may also lodge a complaint with a data protection supervisory authority.
15. Additional information for US residents
Residents of certain US states may have rights under state privacy laws regarding their personal information. We do not sell personal information or share it for cross-context behavioural advertising, except that we use Google Ads conversion measurement when you have given consent. Residents may exercise their rights by email to hello@oplema.com.
16. Automated decision-making
We do not make decisions based solely on automated processing, including profiling, that produce legal effects concerning you or similarly significantly affect you.
17. Whether you must provide personal data
Providing the account data requested at sign-up is necessary to create an account. If you do not provide it, we are unable to create an account for you, but you can use the parts of the Service available without an account. Providing other personal data, including consent to analytics and advertising cookies, is voluntary.
18. Children
The Service is intended for persons aged 18 or older. We do not knowingly collect personal data from persons under 18. If you believe that a person under 18 has provided us with personal data, please contact us.
19. Changes to this Privacy Policy
We may update this Privacy Policy. The updated version applies from the effective date shown at the top of this page.
20. Contact
For questions about this Privacy Policy or to exercise your rights, contact us at hello@oplema.com.
Oplema ApS
CVR: 46635183
Byporten 8
2700 Brønshøj
Denmark
Email: hello@oplema.com
See also the Terms of Service and the Data Processing Agreement.