Privacy Policy
Last updated: November 9, 2026
Summary
This privacy policy provides an overview of the processing of your data by Patrick Probst, operating TacOps ("we", "us"). We take the protection of your personal data very seriously and treat your personal data confidentially and in accordance with the statutory data protection regulations and this privacy policy.
Preamble
With the following privacy policy, we would like to inform you about the types of your personal data (hereinafter also referred to as "data") we process, for what purposes, and to what extent. The privacy policy applies to all processing of personal data carried out by us, both in the context of providing our services and, in particular, on our websites, in mobile applications and within external online presences, such as our social media profiles (hereinafter collectively referred to as "online offering").
The terms used are not gender-specific.
Table of contents
- Preamble
- Provider and controller (Imprint)
- Overview of processing
- Relevant legal bases
- Security
- Transfer of personal data
- International data transfers
- General information on data storage and deletion
- Rights of data subjects
- Provision of online services and web hosting
- Use of cookies
- Registration, login, and user account
- Payment and subscription (TacOps Pro)
- Pay per call with USDC (public API)
- Cancellation, withdrawal, and contact declarations
- Community functions
- Single sign-on login
- Contact and inquiry management
- Web analysis, monitoring, and optimization
- AI-assisted support, search, and error analysis
- Current data processors
- Management, organization, and support tools
- Browser extensions
- Modification and updating
- Changes to this policy
- Definition of terms
Provider and controller (Imprint)
Patrick Probst
c/o IP-Management #8844
Ludwig-Erhard-Str. 18
20459 Hamburg
Germany
Email address: admin@tacops.gg
Contact form: tacops.gg/contact.html (answered within one working day)
Single point of contact for authorities and for users under the Digital Services Act (Art. 11 and 12 DSA): abuse@tacops.gg. A person reads every message. Languages for contact and for reports: English and German.
Overview of processing
The following overview summarizes the types of data processed and the purposes for which they are processed and refers to the data subjects.
Types of data processed
- Inventory data.
- Contact data.
- Content data.
- Contract and payment data.
- Usage data.
- Meta, communication, and procedural data.
- Log data.
Categories of data subjects
- Communication partners.
- Users.
Purposes of processing
- Provision of contractual services and fulfillment of contractual obligations.
- Communication.
- Security measures.
- Reach measurement.
- Office and organizational procedures.
- Organizational and administrative procedures.
- Feedback.
- Profiles with user-related information.
- Registration procedures.
- Provision of our online services and user-friendliness.
- Information technology infrastructure.
Relevant legal bases
Relevant legal bases under the GDPR: Below you will find an overview of the legal bases of the GDPR on the basis of which we process personal data. Note that in addition to the provisions of the GDPR, national data protection regulations may apply in your or our country of residence or domicile . If more specific legal bases are relevant in individual cases, we will inform you of this in the privacy policy.
- Consent (Art. 6 (1) (a) GDPR) - The data subject has given their consent to the processing of their personal data for a specific purpose or several specific purposes.
- Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR) - Processing is necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract.
- Legitimate interests (Art. 6 (1) (f) GDPR) - Processing is necessary for the pursuit of the legitimate interests of the controller or a third party, provided that the interests, fundamental rights, and freedoms of the data subject requiring the protection of personal data do not prevail.
National data protection regulations in Germany: In addition to the data protection regulations of the GDPR, national regulations on data protection apply in Germany. These include, in particular, the Act on the Protection against Misuse of Personal Data in Data Processing (Federal Data Protection Act - BDSG). The BDSG contains in particular special regulations on the right to information, the right to erasure, the right to object, the processing of special categories of personal data, processing for other purposes and transfer as well as automated decision-making in individual cases, including profiling. Furthermore, state data protection laws of the individual federal states may apply.
Security measures
We take appropriate technical and organizational measures to ensure a level of protection appropriate to the risk, taking into account the state of the art, implementation costs and the nature, scope, context and purposes of processing as well as the different probabilities of occurrence and the severity of the risk to the rights and freedoms of natural persons.
These measures include, in particular, ensuring the confidentiality, integrity, and availability of data by controlling physical and electronic access to the data as well as access to it, input, disclosure, securing availability, and separation. Furthermore, we have established procedures that ensure the exercise of data subjects' rights, the deletion of data, and responses to threats to data. In addition, we take the protection of personal data into account as early as the development or selection stage of hardware, software, and procedures in accordance with the principle of data protection, through technology design and data protection-friendly default settings.
Truncation of the IP address: If IP addresses are processed by us or by the service providers and technologies we use and the processing of a complete IP address is not necessary, the IP address is truncated (also known as "IP masking"). This involves removing the last two digits or the last part of the IP address after a dot or replacing them with placeholders. The purpose of shortening the IP address is to prevent or significantly impede the identification of a person based on their IP address.
Securing online connections with TLS/SSL encryption technology (HTTPS): To protect the data of users that is transmitted via our online services from unauthorized access, we use TLS/SSL encryption technology. Secure Sockets Layer (SSL) and Transport Layer Security (TLS) are the cornerstones of secure data transmission on the Internet. These technologies encrypt the information that is transmitted between the website or app and the user's browser (or between two servers), thereby protecting the data from unauthorized access. TLS, as the more advanced and secure version of SSL, ensures that all data transfers meet the highest security standards. When a website is secured by an SSL/TLS certificate, this is signaled by the display of HTTPS in the URL. This serves as an indicator to users that their data is being transmitted securely and encrypted.
Transfer of personal data
In the course of our processing of personal data, it may happen that this data is transferred to or disclosed to other bodies, companies, legally independent organizational units, or persons. The recipients of this data may include, for example, service providers commissioned with IT tasks or providers of services and content that are integrated into a website. In such cases, we observe the legal requirements and, in particular, conclude appropriate contracts or agreements with the recipients of your data that serve to protect your data.
International data transfers
Data processing in third countries: If we transfer data to a third country (i.e., outside the European Union (EU) or the European Economic Area (EEA)) or if this occurs in the context of the use of third-party services or the disclosure or transfer of data to other persons, bodies, or companies (which can be identified by the postal address of the respective provider or if the privacy policy expressly refers to the transfer of data to third countries), this is always done in accordance with the legal requirements.
For data transfers to the USA, we primarily rely on the Data Privacy Framework (DPF), which was recognized as a secure legal framework by an adequacy decision of the EU Commission on July 10, 2023. In addition, we have concluded standard contractual clauses with the respective providers that comply with the requirements of the EU Commission and stipulate contractual obligations to protect your data.
This double safeguard ensures comprehensive protection of your data: The DPF forms the primary level of protection, while the standard contractual clauses serve as additional security. Should changes occur within the framework of the DPF, the standard contractual clauses will serve as a reliable fallback option. In this way, we ensure that your data will always remain adequately protected , even in the event of political or legal changes.
We will inform you whether the individual service providers are certified under the DPF and whether standard contractual clauses are in place. Further information on the DPF and a list of certified companies can be found on the US Department of Commerce website at https://www.dataprivacyframework.gov/ (in English).
Appropriate security measures apply to data transfers to other third countries, in particular standard contractual clauses, express consent, or transfers required by law. Information on third country transfers and applicable adequacy decisions can be found in the information provided by the EU Commission at : https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection_en?prefLang=de.
General information on data storage and deletion
We delete personal data that we process in accordance with the statutory provisions as soon as the underlying consents are revoked or there are no further legal grounds for processing . This applies to cases in which the original purpose of processing no longer applies or the data is no longer required. Exceptions to this rule exist if legal obligations or special interests require longer storage or archiving of the data.
In particular, data that must be retained for commercial or tax reasons or whose storage is necessary for legal prosecution or to protect the rights of other natural or legal persons must be archived accordingly.
Our data protection information contains additional information on the storage and deletion of data that specifically applies to certain processing procedures.
If there are several specifications regarding the retention period or deletion deadlines for a piece of data, the longest period shall always apply. Data that is no longer required for its original purpose but is retained due to legal requirements or other reasons shall be processed by us exclusively for the reasons that justify its retention.
Storage and deletion of data: The following general periods apply to storage and archiving under German law:
- 10 years - Retention period for books and records, annual financial statements, inventories, management reports, opening balance sheets, as well as the work instructions and other organizational documents required for their understanding (Section 147 (1) No. 1 in conjunction with (3) AO, Section 14b (1) UStG, Section 257 (1) No. 1 in conjunction with ( 4) HGB).
- 8 years - Accounting documents, such as invoices and expense receipts (Section 147 (1) No. 4 and 4a in conjunction with (3) Sentence 1 AO and Section 257 (1) No. 4 in conjunction with (4) HGB).
- 6 years - Other business documents: commercial or business letters received, copies of commercial or business letters sent , other documents relevant to taxation, e.g. hourly wage slips, operating statements, calculation documents, price labels, but also payroll documents, unless they are already accounting documents, and cash register receipts (Section 147 (1) No. 2, 3, 5 in conjunction with (3) AO, Section 257 (1) No. 2 and 3 in conjunction with (4) HGB).
- 3 years - Data that is necessary to take into account potential warranty and damage claims or similar contractual claims and rights, as well as to process related inquiries based on previous business experience and customary industry practices, is stored for the duration of the regular statutory limitation period of three years (Sections 195, 199 BGB).
Start of the period at the end of the year: If a period does not expressly begin on a specific date and is at least one year, it automatically begins at the end of the calendar year in which the event triggering the period occurred . In the case of ongoing contractual relationships in which data is stored, the event triggering the period is the date on which the termination or other termination of the legal relationship takes effect.
Rights of data subjects
Rights of data subjects under the GDPR: As a data subject, you have various rights under the GDPR, which arise in particular from Articles 15 to 21 GDPR:
Right to object
You have the right to object at any time, on grounds relating to your particular situation, to processing that we base on a legitimate interest (Art. 6 (1) (e) or (f) GDPR). We then stop that processing unless we can show compelling legitimate grounds that override your interests, rights, and freedoms, or unless we need the data to establish, exercise, or defend legal claims.
You can object to our reach measurement, and you can also stop it yourself at any time with the "Opt out" button in the analytics notice on this website, or under Settings, Telemetry, in the app.
You can object to our server log files and error reports, which we keep to run the service securely and to find faults.
You can object to the access log for shared plans, which records a keyed hash of your shortened IP address for 90 days to protect shared links against misuse.
To object, write to admin@tacops.gg or use our contact form. We do not process personal data for direct marketing.
- Right to withdraw consent: You have the right to withdraw your consent at any time .
- Right to information: You have the right to request confirmation as to whether relevant data is being processed and to obtain information about this data as well as further information and a copy of the data in accordance with legal requirements.
- Right to rectification: In accordance with legal requirements, you have the right to request the completion of data concerning you or the rectification of inaccurate data concerning you .
- Right to erasure and restriction of processing: In accordance with legal requirements, you have the right to request that data concerning you be erased immediately or, alternatively, in accordance with legal requirements, to request a restriction on the processing of the data.
- Right to data portability: You have the right to receive data concerning you that you have provided to us in a structured, commonly used, and machine-readable format in accordance with legal requirements, or to request that it be transferred to another controller .
- Complaint to supervisory authority: Without prejudice to any other administrative or judicial remedy, you have the right to lodge a complaint with a supervisory authority, in particular in the Member State of your habitual residence, your place of work or the place of the alleged infringement, if you consider that the processing of personal data concerning you violates the provisions of the GDPR.
We make no automated decisions about you in the sense of Art. 22 GDPR, and we do no profiling for such decisions.
If you withdraw a consent, the withdrawal does not affect the lawfulness of the processing we carried out on that consent before you withdrew it.
You have to give us the account data we ask for to use the account features; everything else you give us is optional.
Competent supervisory authority: Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (LfDI BW), Heilbronner Straße 35, 70191 Stuttgart; website: https://www.baden-wuerttemberg.datenschutz.de.
Provision of online services and web hosting
We process user data in order to provide them with our online services. For this purpose, we process the user's IP address, which is necessary to transmit the content and functions of our online services to the user's browser or end device.
- Types of data processed: Usage data (e.g., page views and length of stay, click paths, usage intensity and frequency, device types and operating systems used, interactions with content and functions); Meta, communication, and procedural data (e.g., IP addresses, time stamps, identification numbers, persons involved). Log data (e.g., log files relating to logins or the retrieval of data or access times).
- Data subjects: Users (e.g., website visitors, users of online services).
- Purposes of processing and legitimate interests: Provision of our online offering and user-friendliness; IT infrastructure (operation and provision of information systems and technical equipment (computers, servers, etc.)). Security measures.
- Storage and deletion: Deletion in accordance with the information in the section "General information on data storage and deletion."
- Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR).
Further information on processing procedures, methods, and services:
- Provision of online services on rented storage space: To provide our online services, we use storage space, computing capacity, and software that we rent or otherwise obtain from a corresponding server provider (also known as a "web host"); Legal basis: Legitimate interests (Art. 6(1)(f) GDPR).
- Collection of access data and log files: Access to our online offering is logged in the form of so-called "server log files." The server log files may include the address and name of the web pages and files accessed, the date and time of access, the amount of data transferred, notification of successful retrieval, browser type and version, the user's operating system, referrer URL (the previously visited page) and, as a rule, IP addresses and the requesting provider. The server log files can be used on the one hand for security purposes, e.g. to prevent server overload (especially in the case of malicious attacks, known as DDoS attacks), and to ensure the utilization of the servers and their stability; legal basis: legitimate interests (Art. 6 (1) (f) GDPR). Deletion of data: We forward the server logs to BetterStack, which keeps them for 3 days and then deletes them. The copy that stays on the server is capped by size, not by age: the oldest entries drop out as new ones arrive. Data that must be retained for evidential purposes is excluded from deletion until the respective incident has been finally clarified by the authorities.
- Backups: We take a full snapshot of the database every 30 minutes and keep each snapshot for 7 days, on our server and on Cloudflare R2 object storage, which encrypts what it stores. Older snapshots are rotated out automatically. Because of this, data you delete can still sit in a backup for up to 7 days before it disappears for good. Our server host, Hetzner, also keeps a daily image of the server for 7 days, which can hold the same data, and then overwrites it; Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR).
- Image proxy: When a plan shows an image from an outside web address, the app loads it through our image proxy at img.tacops.gg, which runs on Cloudflare. The proxy fetches the image from the outside address on your behalf, checks that it is an image, and passes it to your browser. The site that hosts the image sees the proxy, not your IP address. The proxy keeps no log of who asked for which image; Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR).
- Content delivery network: We use a "content delivery network" (CDN). A CDN is a service that helps deliver content from an online offering, especially large media files such as graphics or program scripts, faster and more securely with the help of regionally distributed servers connected via the internet. Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR).
- Hetzner: Services in the field of providing information technology infrastructure and related services (e.g., storage space and/or computing capacity); Service provider: Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany; Legal basis: Legitimate interests (Art. 6 para. 1 sentence 1 lit. f) GDPR); Website: https://www.hetzner.com; Privacy policy: https://www.hetzner.com/de/rechtliches/datenschutz. Data processing agreement: https://docs.hetzner.com/de/general/general-terms-and-conditions/data-privacy-faq/.
- Cloudflare: Reverse proxy for all traffic to tacops.gg and app.tacops.gg, content delivery network for map tiles, and R2 object storage for map tiles, for custom maps that users publish with a shared plan, for share preview images, and for our database backups (a full snapshot every 30 minutes, kept 7 days and then rotated out; R2 encrypts the stored data); Service provider: Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA; Legal basis: Legitimate interests (Art. 6 (1) lit. f) GDPR); Website: https://www.cloudflare.com; Privacy policy: https://www.cloudflare.com/de-de/privacypolicy/. Basis for third country transfers: Data Privacy Framework (DPF), standard contractual clauses.
Use of cookies
The term "cookies" refers to functions that store information on users' end devices and read it from them . Cookies can also be used for various purposes, such as to ensure the functionality, security, and convenience of online offerings and to create analyses of visitor traffic. We use cookies in accordance with legal requirements. To this end, we obtain the consent of users in advance where necessary. If consent is not necessary, we rely on our legitimate interests. This applies if the storage and retrieval of information is essential in order to provide expressly requested content and functions. This includes, for example, the storage of settings and the ensuring of the functionality and security of our online offering. Consent can be revoked at any time. We provide clear information about their scope and which cookies are used.
Information on the legal basis for data protection: Whether we process personal data using cookies depends on consent. If consent has been given, it serves as the legal basis. Without consent, we rely on our legitimate interests, which are explained above in this section and in the context of the respective services and procedures.
Storage period: With regard to the storage period, the following types of cookies are distinguished:
- Temporary cookies (also known as session cookies): Temporary cookies are deleted at the latest after a user leaves an online offering and closes their device (e.g., browser or mobile application).
- Permanent cookies: Permanent cookies remain stored even after the device is closed. This allows, for example, the login status to be saved and preferred content to be displayed directly when the user visits a website again. Similarly, the user data collected with the help of cookies can be used to measure reach.
Which cookies TacOps actually sets: the "session" cookie keeps you signed in and expires after 30 days. A second cookie lives for 10 minutes and only exists during a sign-in with Steam, Discord, or Google, to match your browser to the answer that comes back from that provider. The "tacops-analytics-consent" cookie remembers your analytics choice across tacops.gg and app.tacops.gg for one year. When scoped map protection is enabled, the "tacops_tile_subject" cookie keeps one functional guest identity for map access for up to 24 hours. It is HttpOnly and is not used for analytics or advertising. Our analytics itself sets no cookie. On your device we also use the browser's local storage for your settings and your analytics choice, and IndexedDB for your plans, so that the editor works offline. All of this is strictly necessary to deliver the functions you ask for, so it needs no consent (§ 25 (2) TDDDG). We set no advertising or tracking cookies.
General information on revocation and objection (opt-out): Userscan revoke their consent at any time and also object to the processing in accordance with the legal requirements, including through their browser's privacy settings.
- Types of data processed: Meta, communication, and process data (e.g., IP addresses, time stamps, identification numbers, persons involved).
- Data subjects: Users (e.g., website visitors, users of online services).
- Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR), and consent (Art. 6 (1) (a) GDPR) where we ask for it.
Registration, login, and user account
Users can create a user account. During registration, users are informed of the required mandatory information and this is processed for the purpose of providing the user account on the basis of contractual obligation fulfillment. The data processed includes, in particular, authentication identifiers from the sign-in provider you choose: the user ID, username, and avatar URL from Steam, Discord, or Google, and, for Discord and Google, the email address of that account. You can connect several providers to one TacOps account under Linked Accounts and disconnect any of them again, as long as one remains.
When you sign in, we store the time of your last sign-in with your account. To protect TacOps and its users against abuse, for example a blocked person who comes back with a new account, we also keep a record of each sign-in: the time, the sign-in provider, a keyed one-way hash of the IP address and of its network (we do not store the address itself), the browser name and major version and the operating system (for example "Firefox 131 on Windows"), and a one-way hash of the browser's full user-agent string. We keep each record for 90 days and then delete it automatically. We look at these records only when we investigate abuse, to find accounts that may belong to the same person. A match is a hint that we check by hand; no decision is made automatically. Your data export includes your sign-in records, and deleting your account deletes them.
When you create an account, we store the date and time you confirmed that you are 16 or older; we never ask for or store your date of birth.
When you create your account, we also store where you came from: the domain of the website that linked you to TacOps (for example "reddit.com", never the full address), the first TacOps page you opened, and the campaign tags in that link (utm_source, utm_medium, and utm_campaign), if it had any. We do not store click IDs or other tracking identifiers. We use this information only in aggregate, to learn which channels bring new players. We keep it for as long as your account exists; your data export includes it, and deleting your account deletes it. Storage is based on our legitimate interest in learning how people find TacOps (Art. 6 para. 1 sentence 1 lit. f) GDPR).
With your account we also store activity dates and first-use dates: the day you were last active, and when you first used a feature, shared a plan, collaborated with others, and started a checkout. They are deleted with the account. Anonymous counts are computed from account and contract data; they hold no identifier (see "Web analysis, monitoring, and optimization").
If you merge two TacOps accounts into one, we keep a record of the merge: the user IDs of both accounts and the time of the merge. We keep it for 3 years and then delete it automatically, so that we can trace where an account's data came from if a merge is disputed or misused (Art. 6 para. 1 sentence 1 lit. f) GDPR).
If we block a person from using TacOps, we store the identifiers of their accounts (the user ID of each sign-in provider and the email addresses of those accounts), the reason, and the date, for as long as the block lasts, so that these accounts cannot sign in and cannot be used to create or link another account. Deleting the account does not lift a block. After we lift a block, we keep a record of the block and of its lifting for one year and then delete it. Storage is based on our legitimate interests in protecting the service and its users against misuse and other unauthorized use (Art. 6 para. 1 sentence 1 lit. f) GDPR). This data is not passed on to third parties unless it is necessary for the pursuit of our claims or there is a legal obligation to do so.
Users can be informed by email about processes that are relevant to their user account, such as technical changes. Further information on processing processes, procedures, and services:
- Types of data processed: Inventory data (sign-in provider user ID, username, and avatar URL; the email address of a Discord or Google account used to sign in; the sign-up source: referrer domain, first page, and campaign tags); contact data (the email address you enter at checkout, if you subscribe); Content data (e.g., text or image messages and posts, as well as related information, such as details of authorship or time of creation); Usage data (e.g., page views and length of stay, click paths, usage intensity and frequency, device types and operating systems used, interactions with content and functions). Log data (e.g., log files relating to logins or the retrieval of data or access times).
- Data subjects: Users (e.g., website visitors, users of online services).
- Purposes of processing and legitimate interests: Provision of contractual services and fulfillment of contractual obligations; security measures; organizational and administrative procedures. Provision of our online offering and user-friendliness.
- Storage and deletion: Deletion in accordance with the information in the section "General information on data storage and deletion." Deletion after termination.
- Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 para. 1 sentence 1 lit. b) GDPR). Legitimate interests (Art. 6 para. 1 sentence 1 lit. f) GDPR).
Further information on processing procedures, processes, and services:
- Deletion of data after termination: When users terminate their user account, their data relating to the user account will be deleted, subject to legal permission, obligation, or consent of the users; legal basis: contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR).
- No obligation to retain data: It is the responsibility of users to back up their data upon termination before the end of the contract. We are entitled to irretrievably delete all user data stored during the term of the contract ; Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR).
Payment and subscription (TacOps Pro)
If you subscribe to TacOps Pro, we process the data needed to conclude and run the subscription contract, to invoice you, and to keep the tax records the law requires. The payment itself runs through our payment provider Stripe; we never see or store your full card number.
- Types of data processed: Contact data (the email address you enter at checkout); inventory data (billing address and country, subscription status); contract data (plan, price, term, invoices); payment data (a summary of the payment method, never the full card number).
- Data subjects: Users who subscribe to TacOps Pro.
- Purposes of processing: Conclusion and performance of the subscription contract; invoicing; determining the applicable value-added tax; compliance with commercial and tax retention duties.
- Storage and deletion: Subscription data until you delete your account. Invoices and tax records for 10 years (§ 147 AO), after which we delete them.
- Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR) for the subscription; legal obligation (Art. 6 (1) (c) GDPR) for invoices and tax records.
Further information on processing procedures, methods, and services:
- Stripe: Payment processing, invoicing, tax determination, and the customer portal in which you find your invoices and manage your subscription; Service provider: Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland, with onward transfer to Stripe, Inc. (USA); Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR), legal obligation (Art. 6 (1) (c) GDPR); Website: https://stripe.com; Privacy policy: https://stripe.com/privacy. Basis for third country transfers: Data Privacy Framework (DPF), standard contractual clauses. Stripe also acts as an independent controller for its own purposes, in particular fraud prevention and its own legal duties; for that processing Stripe is the controller and its privacy policy applies.
Pay per call with USDC (public API)
If you use the public API without included API access, you can pay for a single request with USDC on the Base network. We process the payment data to check that the request was paid and to keep a record of it.
- Types of data processed: The wallet address you pay from, the transaction hash, the amount, and the timestamp.
- Data subjects: Users of the public API who pay per request.
- Purposes of processing: Verifying and recording a payment.
- Storage and deletion: We keep the transaction hash and the related payment record for 1 year, then delete it. The blockchain itself is public and outside our control: we cannot change or erase an entry there.
- Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR).
We pass no data to a third party for this payment. The transaction is public by design, because every transaction on the Base network can be read by anyone.
Cancellation, withdrawal, and contact declarations
When you cancel or withdraw on our cancellation page, or write to us through our contact form, we process what you enter so that we can act on your declaration and answer you.
- Types of data processed: From the cancellation page: your name, your email address, your TacOps sign-in name (Steam profile name or URL, or your Discord or Google name), an optional customer or invoice number, a requested end date, and a reason, plus the type of declaration and the time we received it. From the contact form: your name, your email address, and your message. In both cases the IP address the submission came from.
- Data subjects: Users and communication partners.
- Purposes of processing: Handling termination and withdrawal declarations and sending you the receipt the law requires (§ 312k and § 356a BGB); answering contact requests; detecting abuse of the forms.
- Storage and deletion: Cancellation and withdrawal declarations are kept for 3 years and then deleted, because that is the regular limitation period for claims out of the contract (§ 195 BGB). Contact messages are kept until your request is answered, and then for as long as the mailbox keeps sent and received mail.
- Recipients: Resend (delivery of the receipt and of contact messages by email); GitHub (a cancellation declaration is copied into an internal ticket in a private repository so that it is not lost).
- Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR), legal obligation (Art. 6 (1) (c) GDPR) for the receipt, and legitimate interests (Art. 6 (1) (f) GDPR) for detecting abuse of the forms.
A contact message is sent to us by email and is not stored in a database. A cancellation declaration is stored in our database, copied into the internal ticket described above, and recorded as an event in our own analytics, so that we notice a flood of automated submissions. Our analytics reads the IP address of the submission only to derive the country, and does not store it.
Community functions
The community functions provided by us allow users to engage in conversations or otherwise interact with each other. You may use the community functions only in compliance with the applicable legal situation, our terms and conditions and guidelines, and the rights of other users and third parties.
- Types of data processed: Inventory data (sign-in provider user ID, username, and avatar URL). Usage data (e.g., page views and length of stay, click paths, usage intensity and frequency, device types and operating systems used, interactions with content and functions).
- Data subjects: Users (e.g., website visitors, users of online services).
- Purposes of processing and legitimate interests: Provision of contractual services and fulfillment of contractual obligations; security measures. Provision of our online offering and user-friendliness.
- Storage and deletion: Deletion in accordance with the information in the section "General information on data storage and deletion."
- Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR). Legitimate interests (Art. 6 (1) (f) GDPR).
Further information on processing procedures, methods, and services:
- Protection of own data: Users decide for themselves what data they disclose about themselves within our online offering. For example, when users provide personal information or participate in conversations. We ask users to protect their data and to publish personal data only with caution and only to the extent necessary; Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR).
- Access logs for shared maps (share access log): When accessing map plans shared by users , an access log is created for security and misuse protection purposes . The truncated IP address (last octet anonymized) and a generalized browser identifier are stored. This data is automatically deleted after 90 days; Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR).
- Custom maps in shared plans: When you share a plan that uses a custom map you uploaded, your browser uploads the map image, cut into tiles, to our storage at Cloudflare R2, so that the people you share the link with see the map without uploading it themselves. Everyone who has the link can view the image. We keep it until no shared plan uses it any more: when you delete or stop sharing the last such plan, delete the custom map, or delete your account, we delete it. We also delete it when we remove it after a report (Terms, section 12) or block your account. Upload only images you have the rights to; Legal basis: Contract fulfillment (Art. 6 (1) (b) GDPR).
- Reports about shared maps: When you report a shared map with "Report this map" or by email, we store the time, the reason, the share link, your explanation, and, if you give them, your name and email address. We use your email address only to confirm that we received the report and to tell you our decision. The owner of the map learns our decision and the reason for it, but not who reported it. We delete a report one year after our decision. If we report a suspected crime to the police, we keep the records they need until they no longer need them; Legal basis: Legal obligation (Art. 6 (1) (c) GDPR, together with Art. 16 to 18 of the Digital Services Act).
- Names passed in by partner platforms (hand-off links): A partner platform can let its own users into a TacOps plan live through a one-use link, without a TacOps account. The platform passes us the name the person is shown under, and can pass its own identifier for the person and a group identifier. We show the name to the other people in the plan and report it, with the identifiers, back to the platform, so that it can see who is in the plan and end their access. We keep the name and identifiers while the person's access is open and for 30 days after it ends; then we replace the name with a generic guest name and delete the person's identifier. Audit records of joining and leaving are deleted after 90 days. No account is created, and your browser keeps the access key for that tab only, until the tab is closed. The partner platform is the controller for this data, and we process it on its behalf; to have it deleted sooner, contact the platform or us; Legal basis: Processing on behalf of the partner platform (Art. 28 GDPR), which determines the legal basis.
Single sign-on
"Single sign-on" or "single sign-on login or authentication" refers to procedures that allow users to log in to our online offering using a user account with a single sign-on provider (e.g., a social network). The prerequisite for single sign-on authentication is that users are registered with the respective single sign-on provider and enter the required access data in the online form provided for this purpose, or are already logged in with the single sign-on provider and confirm the single sign-on login via a button.
Authentication takes place directly with the respective single sign-on provider. As part of such authentication, we receive a user ID with the information that the user is logged in under this user ID with the respective single sign-on provider and an ID that cannot be used by us for other purposes (so-called "user handle"). Whether additional data is transmitted to us depends solely on the single sign-on procedure used, the data releases selected during authentication, and also on which data users have released in the privacy or other settings of their user account with the single sign-on provider. We offer three single sign-on providers. Steam transmits the SteamID64, the Steam username, and the Steam avatar URL to us, and nothing else. Discord transmits your Discord user ID, display name, avatar, and the email address of your Discord account together with its verification status. Google transmits your Google account ID, name, profile picture, and email address together with its verification status. We request no further permissions: no access to your Discord servers, messages, or friends, and none to your Google contacts, files, or calendar. We cannot see the password entered during the single sign-on process, nor do we store it, and we keep no access or refresh tokens from any provider; each sign-in is a one-time exchange.
Each time you sign in, we refresh your username and avatar URL from the provider you signed in with. The email address received from Discord or Google is stored as part of your account data so that we can identify the account; we do not use it to send you messages, and we never link or merge accounts on the basis of an email address. There is no separate profile at TacOps to edit. Under Linked Accounts in the app you can connect a further provider to your account, and disconnect a provider again, which deletes that provider's data from your account at once. The last remaining provider cannot be disconnected; to remove it, delete your TacOps account under Settings.
We can use the single sign-on registration, if agreed with the users, within the scope of or prior to the performance of the contract, insofar as the users have been asked to do so within the scope of a consent and otherwise use it on the basis of our legitimate interests and the interests of the users in an effective and secure login system.
If users decide that they no longer wish to use the link to their user account with the single sign-on provider for the single sign-on procedure, they must remove this link within their user account with the single sign-on provider. If users wish to delete their data from our system, they must cancel their registration with us .
- Types of data processed: Inventory data (sign-in provider user ID, username, and avatar URL; the email address of a Discord or Google account used to sign in); usage data (e.g., page views and dwell time, click paths, usage intensity and frequency, types of devices and operating systems used , interactions with content and functions). Meta, communication, and process data (e.g., IP addresses, time stamps, identification numbers, persons involved).
- Data subjects: Users (e.g., website visitors, users of online services).
- Purposes of processing and legitimate interests: Provision of contractual services and fulfillment of contractual obligations; security measures; registration procedures. Provision of our online offering and user-friendliness.
- Storage and deletion: Deletion in accordance with the information in the section "General information on data storage and deletion." Deletion after termination.
- Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR). Legitimate interests (Art. 6 (1) (f) GDPR).
Further information on processing procedures, processes, and services:
- Steam (Valve Corporation): Authentication service for user login via Steam OpenID. During the login process, the Steam ID (SteamID 64), Steam username, and Steam avatar URL are transmitted and stored by us. The user's Steam password is neither visible to us nor stored by us; Service provider: Valve Corporation, 10400 NE 4th Street, Bellevue, WA 98004, USA; Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR), legitimate interests (Art. 6 (1) (1) lit. f) GDPR); Website: https://store.steampowered.com; Privacy policy: https://store.steampowered.com/privacy_agreement/. Basis for third country transfers: Valve acts as an independent controller for the Steam account; the sign-in transfer is necessary for the contract you request (Art. 49 (1) (b) GDPR).
- Discord (Discord Inc.): Authentication service for user login via Discord OpenID Connect. During the login process, the Discord user ID, display name, avatar URL, and the email address of the Discord account with its verification status are transmitted and stored by us. We request only the "identify", "email", and "openid" permissions; the user's Discord password, servers, and messages are neither visible to us nor stored by us; Service provider: Discord Inc., 444 De Haro Street, Suite 200, San Francisco, CA 94107, USA; Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR), legitimate interests (Art. 6 (1) (1) lit. f) GDPR); Website: https://discord.com; Privacy policy: https://discord.com/privacy. Basis for third country transfers: Data Privacy Framework (DPF): Discord Inc. is certified under the EU-U.S. DPF, its UK Extension, and the Swiss-U.S. DPF; in addition, the sign-in transfer is necessary for the contract you request (Art. 49 (1) (b) GDPR).
- Google Sign-In (Google): Authentication service for user login via Google OpenID Connect. During the login process, the Google account ID, name, profile picture URL, and the email address of the Google account with its verification status are transmitted and stored by us. We request only the "openid", "email", and "profile" scopes; the user's Google password, contacts, files, and calendar are neither visible to us nor stored by us; Service provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland; parent company: Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA; Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR), legitimate interests (Art. 6 (1) (1) lit. f) GDPR); Website: https://www.google.com; Privacy policy: https://policies.google.com/privacy. Basis for third country transfers: Data Privacy Framework (DPF); in addition, the sign-in transfer is necessary for the contract you request (Art. 49 (1) (b) GDPR).
Contact and inquiry management
When contacting us (e.g., by mail, contact form, email, telephone, or social media) and within the framework of existing user and business relationships, the information provided by the inquiring persons is processed to the extent necessary to respond to contact inquiries and any requested measures.
- Types of data processed: Contact details (e.g., postal and email addresses or telephone numbers); content data (e.g., text or image messages and posts, as well as related information, such as details of authorship or time of creation). Meta, communication, and process data (e.g., IP addresses, time stamps, identification numbers, persons involved).
- Data subjects: Communication partners.
- Purposes of processing and legitimate interests: Communication; organizational and administrative procedures; feedback (e.g., collecting feedback via online form). Provision of our online offering and user-friendliness.
- Storage and deletion: Deletion in accordance with the information in the section "General information on data storage and deletion."
- Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR). Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR).
Further information on processing procedures, methods, and services:
- Contact form: When you contact us via our contact form, by email, or other means of communication, we process the personal data you provide to respond to and process your request. This usually includes information such as your name, contact information, and any other information you provide that is necessary for us to process your request appropriately . . We use this data exclusively for the stated purpose of establishing contact and communication; Legal bases: Contract fulfillment and pre-contractual inquiries (Art. 6 para. 1 sentence 1 lit. b) GDPR), legitimate interests (Art. 6 para. 1 sentence 1 lit. f) GDPR).
Web analysis, monitoring, and optimization
Web analysis (also known as "reach measurement") is used to evaluate visitor flows to our online offering. With the help of reach analysis, we can, for example, identify at what time our online offering or its functions or content are most frequently used or invite reuse. It also enables us to understand which areas require optimization.
How we do it: our analytics runs on our own server, sets no cookie, and writes nothing to your device. It reads what your browser exposes to every website: the page you asked for, your browser and operating system, your browser language, and your screen size. In the app it also records how the service is used: whether you use a phone, tablet, or desktop, whether it has a touch screen, your window width and screen pixel density rounded to a size band, whether your browser supports WebGL2, and a coarse graphics vendor class such as Apple, NVIDIA, or software rendering, never the exact graphics model. It also records a coarse hardware class (low, mid, or high) that it derives from the number of processor cores and the device memory your browser reports, never those numbers themselves. It records the app version, whether you are signed in, your subscription tier, which features you use (for example which map, tool, symbol set, or sign-in provider), the range of zoom levels you used, rounded timings such as how long a map took to load, how long a session lasted, or how smoothly the map moved and how fast it answered while you worked on it, page load performance (Web Vitals: time to first byte, largest paint, input delay, and layout shift) rounded to a band, and the category of an error, never its message. It never records your plans, your map content, or anything you type. It sets no cookie and stores nothing on your device beyond the separate cookie that remembers your analytics choice, so the consent rule for analytics device storage (§ 25 TDDDG) does not apply and we show no consent banner. The legal basis for the processing itself is our legitimate interest in understanding how the service is used and where to improve it (Art. 6 (1) (f) GDPR). Analytics runs unless you opt out. The analytics notice tells you about it; it does not ask for your consent, because analytics rests on our legitimate interest, not on consent. You can opt out at any time: on this website with the "Opt out" button in the analytics notice, on a shared plan page with "Opt out of analytics", and in the app under Settings, Telemetry, which the app's analytics notice links to. On product events from a signed-in user we attach a keyed hash of the account id; that hash is pseudonymous personal data, not anonymous data, because we can link it back to an account with the key that only our server holds.
Some product events come from our server instead of your browser: a plan activation, a feature limit reached, a checkout started, the billing portal opened, a subscription change reported by our payment provider, a cancellation submitted, and a request to our public API. For these events the server passes the requested address, your browser's user agent, the referrer, your browser language, and your IP address to our analytics, which derives the country and an approximate location (region and city) from the IP address and does not store the address itself. When Telemetry is off, the server shortens the IP address first (the last part is dropped), so it points to a network rather than to your device. When Telemetry is off, the server still records these events, but without the pseudonymous account identifier. A request to our public API also carries a keyed hash of the API key it used. That hash is pseudonymous personal data too, because we can link it to the account that owns the key. When the owner of the key switched Telemetry off, the event carries neither hash.
When you open a plan that someone shared with you, the same analytics counts your visit, whether you have an account or not. The share page links to the opt-out.
- Types of data processed: Usage data (e.g., page views and length of stay, click paths, usage intensity and frequency, device types and operating systems used, interactions with content and functions, click positions and scroll depth on the start page of this website, browser graphics capability, subscription tier, rounded timings, error categories). Meta, communication, and process data (e.g., IP addresses, time stamps, identification numbers, persons involved).
- Data subjects: Users (e.g., website visitors, users of online services).
- Purposes of processing and legitimate interests: Reach measurement (e.g., access statistics, recognition of returning visitors). Provision of our online offering and user-friendliness. We do not create advertising or interest profiles, and we do not use the data for advertising.
- Storage and deletion: Our reach measurement sets no cookies and stores nothing on the user's device. Collected usage data is deleted after 12 months, and otherwise in accordance with the section "General information on data storage and deletion." When you delete your account, the details of the usage events that carry its pseudonymous identifier are deleted within a day; only anonymous counts remain.
- Security measures: IP masking (pseudonymization of the IP address). The IP address is not stored.
- Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR).
Further information on processing procedures, methods, and services:
- Umami (self-hosted): We use Umami as a self-hosted, cookie-free web analytics solution for the anonymized evaluation of the use of our online offering. Umami is operated on our own infrastructure; no data is transmitted to third parties. No cookies are set and no personal data such as IP addresses are stored permanently. The data collected (page views, referral source, browser, operating system, device type) is anonymized and does not allow any conclusions to be drawn about individual users. On the start page of this website, Umami also records where visitors click and how far they scroll. In the app's map library, it records click positions only. These heatmaps help us see which parts of those pages are used: the click position, the size of the browser window and of the page, and the page address without query or fragment. It records no page content, no text, nothing you type, and no screen recording. For users signed in to the app, product events (for example a plan save or an upgrade click) may additionally carry a pseudonymous account identifier. That identifier is a keyed hash (HMAC-SHA256) of the account id with a secret held only on our server, and it exists so that we can measure how a signed-in user moves through the product. It cannot be reversed by a third party. Under Settings, Telemetry, in the app you can switch off the analytics your browser sends; the server-side product events described above then carry no account identifier and no API key hash. You can opt out of analytics on this website with the "Opt out" button in the analytics notice; legal basis: legitimate interests (Art. 6 para. 1 sentence 1 lit. f) GDPR); website: https://umami.is.
- Map tile statistics: Our map tile server counts, per hour, how often the tiles of each map were loaded, by map layer and zoom level, whether the content delivery network answered from its cache, and the country the request came from. To count a map view once, it hashes your IP address together with a random value in memory for 30 minutes; that hash is never stored or sent. No IP address, account, cookie, or browser identifier goes into the statistics; legal basis: legitimate interests (Art. 6 (1) (f) GDPR).
- Anonymous counts from account data: We count, from our own account and contract data, how many accounts signed up, were active, or subscribed in a period. The counts hold no identifier and cover all accounts, including the accounts of users who switched Telemetry off, because no personal data leaves the account database in them; legal basis: legitimate interests (Art. 6 (1) (f) GDPR).
- Map access protection: when enabled, a separate security system uses keyed pseudonymous guest or integration identifiers and a keyed network identifier to detect sustained bulk map collection. It counts requests, failures, estimated response bytes, and distinct map tiles in bounded windows. Detailed security windows remain in live storage for at most 24 hours; inactive security state is cleared after 24 hours without requests. A minimal alert acceptance timestamp remains for at most 24 hours after acknowledgement to prevent duplicate alerts. Grouped pseudonymous operational incidents can be sent to our operators through our existing email service and follow the retention of the receiving service. The system does not use browser fingerprinting and does not reuse these identifiers for product analytics. Anonymous browsing remains available without challenges or forced sign-in.
AI-assisted support, search, and error analysis
We use AI models for three jobs: to sort and analyze the feedback you send from the app, to analyze error reports so that we can fix faults, and to find maps that match a map search in TacOps Pro. The models make no decision about you, and we review their results before they change the service.
- Types of data processed: Content data (the title and text of your feedback, without your username and without the contact line; the device context described under GitHub below; facts about the plan you had open: map, size, sharing state, and, for the plan's owner, the Telemetry setting, sign-in provider, account creation date, and plan count; the text of a map search). Usage and meta data in error reports (stack trace, browser and operating system, the page address, and the IP address our error tracking recorded).
- Data subjects: Users who send feedback, use map search, or run into an error.
- Purposes of processing and legitimate interests: Sorting and analyzing feedback and error reports, and preparing fixes; matching maps to a search.
- Storage and deletion: Feedback stays in GitHub and error reports stay in Sentry, as described in the sections on those services. We keep the text of a map search for 30 days and then delete it. The AI providers keep what they receive according to their own privacy policies. The privacy policy of TypeSafe AI says that it does not train models on what it receives. The privacy policy of OpenRouter says that it does not use inputs and outputs for its own model training, and that a provider that hosts a model through OpenRouter can; that provider follows its own terms.
- Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR) for feedback and error analysis; contract fulfillment (Art. 6 (1) (b) GDPR) for map search.
Further information on processing procedures, methods, and services:
- OpenRouter: Access to the language model that analyzes feedback and error reports. OpenRouter passes each request to a provider that hosts the model; that provider can be located outside the European Union; Service provider: OpenRouter, Inc., USA; Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR); Website: https://openrouter.ai; Privacy policy: https://openrouter.ai/privacy. Third country transfer: to the USA, and to the country of the provider that hosts the model. OpenRouter's privacy policy names standard contractual clauses for transfers out of the EEA and the UK.
- TypeSafe AI (Jev): Scoring maps against a map search, and classifying feedback. A map search is sent without your account; feedback is sent without your username and without the contact line; Service provider: TypeSafe AI, Inc., USA; Legal basis: Contract fulfillment (Art. 6 (1) (b) GDPR) for map search, legitimate interests (Art. 6 (1) (f) GDPR) for feedback; Website: https://typesafe.ai; Privacy policy: https://typesafe.ai/privacy. Third country transfer: to the USA, where TypeSafe AI hosts its service. Its privacy policy names no transfer mechanism.
Current Data Processors (Key Services)
The following table lists key third-party services used for analytics, error monitoring, logging, feedback processing, AI-assisted analysis, payment, email delivery, and backups, including the data processed and legal basis. Additional providers used for hosting, content delivery, and authentication are described in the relevant sections of this privacy policy.
| Processor | Purpose | Data Collected | Retention | Lawful Basis |
|---|---|---|---|---|
| Umami | Usage analytics (anonymous; pseudonymous for signed-in users) | Page views, device type, browser (no PII); click positions and scroll depth on the website start page, and click positions in the app's map library; for signed-in users a keyed hash of the account id on product events; on public API requests a keyed hash of the API key; both hashes dropped when the user switched Telemetry off | 12 months | Legitimate interest (Art. 6(1)(f)) |
| Sentry | Error tracking | Error stack traces, browser and operating system details, IP address; tags for app area, map, 2D or 3D view, account tier, graphics card vendor class; every error, no sampling | 90 days | Legitimate interest (Art. 6(1)(f)) |
| BetterStack | Log aggregation & uptime monitoring | Server logs, IP addresses | 3 days | Legitimate interest (Art. 6(1)(f)) |
| GitHub | Feedback and cancellation tickets in a private repository | Username, feedback content, optional contact, device context, cancellation declarations | Until deleted on request | Legitimate interest (Art. 6(1)(f)) |
| OpenRouter | AI analysis of feedback and error reports | Feedback text and device context without username or contact, plan facts, error reports | According to the provider's privacy policy | Legitimate interest (Art. 6(1)(f)) |
| TypeSafe AI | Map search scoring, feedback classification | Map search text without account; feedback without username or contact | According to the provider's privacy policy; search text with us 30 days | Contract fulfillment (Art. 6(1)(b)), legitimate interest (Art. 6(1)(f)) |
| Stripe | Payment, invoicing, tax, and customer portal for TacOps Pro | Email address, billing address and country, payment method summary, subscription status, invoices | Until account deletion; invoices and tax records 10 years | Contract fulfillment (Art. 6(1)(b)), legal obligation (Art. 6(1)(c)) |
| Resend | Email delivery for receipts and contact messages | Recipient address, subject, message content, delivery metadata | Until the message is delivered, plus Resend's log retention | Contract fulfillment (Art. 6(1)(b)) |
| Cloudflare R2 (backups) | Off-server storage of database backups | A full database snapshot every 30 minutes, encrypted at rest | 7 days, then rotated out | Legitimate interest (Art. 6(1)(f)) |
| Cloudflare R2 (shared custom maps) | Storage and delivery of custom map images in shared plans | The map image as tiles, tied to your account id | Until no shared plan uses it, or the map or account is deleted | Contract fulfillment (Art. 6(1)(b)) |
| Hetzner (server images) | Disaster recovery for the server | A daily image of the server, which can hold the same data as the database backups | 7 days, then overwritten | Legitimate interest (Art. 6(1)(f)) |
| Steam (Valve Corp) | Single Sign-On Authentication | SteamID 64, Username, Avatar URL | Until account deletion or unlinking | Contract fulfillment (Art. 6(1)(b)) |
| Discord (Discord Inc.) | Single Sign-On Authentication | Discord user ID, display name, avatar URL, email address | Until account deletion or unlinking | Contract fulfillment (Art. 6(1)(b)) |
| Google (Google Ireland Ltd) | Single Sign-On Authentication | Google account ID, name, profile picture URL, email address | Until account deletion or unlinking | Contract fulfillment (Art. 6(1)(b)) |
Management, organization, and support tools
We use services, platforms, and software from other providers (hereinafter referred to as "third-party providers") for the purposes of organizing, managing, planning, and providing our services. When selecting the third-party providers and their services, we comply with the legal requirements.
In this context, personal data may be processed and stored on the servers of third-party providers. This may affect various data that we process in accordance with this privacy policy. This data may include, in particular, master data and contact details of users, data on transactions, contracts, other processes and their contents.
If users are referred to third-party providers or their software or platforms in the context of communication, business or other relationships with us, the third-party providers may process usage data and metadata for security purposes, service optimization or marketing purposes. We therefore ask you to observe the privacy policies of the respective third-party providers.
- Types of data processed: Content data (e.g., textual or pictorial messages and posts as well as information relating to them, such as details of authorship or time of creation); Usage data (e.g., page views and dwell time, click paths, usage intensity and frequency, types of devices and operating systems used , interactions with content and functions). Meta, communication, and process data (e.g., IP addresses, time stamps, identification numbers, persons involved).
- Data subjects: Communication partners. Users (e.g., website visitors, users of online services).
- Purposes of processing and legitimate interests: Provision of contractual services and fulfillment of contractual obligations. Office and organizational procedures.
- Storage and deletion: Deletion in accordance with the information in the section "General information on data storage and deletion."
- Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR).
Further information on processing procedures, methods, and services:
- Sentry: We use Sentry to detect, diagnose, and fix software errors in our online offering. When an error occurs, technical information such as browser type, operating system, error details (stack traces), and the user's full IP address are transmitted to Sentry. Each error report from your browser also carries the app area (the editor or a share link), the map shown, whether the 2D or 3D view was open, your account tier, and a coarse class of the graphics card vendor, never the exact graphics model. We keep every error report, not a sample. We use Sentry's EU data residency, so error events are received and stored in the European Union (Frankfurt) and are not transferred to a third country. Sentry deletes them after 90 days. The processing serves to ensure the functionality and stability of our service; Service provider: Functional Software, Inc. (dba Sentry), 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA; Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR); Website: https://sentry.io; Privacy policy: https://sentry.io/privacy/. Basis for third country transfers: None is needed for error events, because they stay in the European Union.
- BetterStack (Logtail): We use BetterStack (Logtail) to aggregate and analyze server log data. Server log data is transmitted to BetterStack for monitoring, troubleshooting, and ensuring the proper operation of our infrastructure. Technical data such as IP addresses, timestamps, error messages, and request information may be processed in the process; Service provider: Better Stack, Inc., 2261 Market Street #4242, San Francisco, CA 94114, USA; Legal basis: Legitimate interests (Art. 6 (1) (f) GDPR); Website: https://betterstack.com; Privacy policy: https://betterstack.com/privacy. Basis for third-country transfers: Standard contractual clauses.
- GitHub (for feedback and cancellation tickets): When users send feedback via the feedback function in our application, the content of the feedback is transmitted to GitHub together with the user's TacOps username and the name of the sign-in provider it comes from (Steam, Discord, or Google), the contact information you enter if you choose to (an email address or Discord name), and device context that helps us reproduce the problem: the app version, the open map and plan, counts of features and layers, the enabled overlays, whether 3D or a live session is active, your Telemetry setting, browser and operating system, language, screen size and pixel density, number of processor cores, device memory, whether you are online, and the graphics renderer, and stored there as an issue in a private repository that only we can read. We also copy a cancellation or withdrawal declaration from our cancellation page into such an issue, so that we act on it. An issue stays there until we delete it; you can ask us to delete it at any time. The processing serves to handle user feedback and declarations and to improve our service; Service provider: GitHub, Inc. (Microsoft Corporation), 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA; Legal basis: Legitimate interests (Art. 6 (1) (1) lit. f) GDPR); Website: https://github.com; Privacy policy: https://docs.github.com/de/site-policy/privacy-policies/github-general-privacy-statement. Basis for third country transfers: Data Privacy Framework (DPF), standard contractual clauses.
- Resend: Email delivery for the receipts we send after a cancellation or withdrawal and for messages from our contact form. The following data is processed: the recipient address, the subject, the content of the message, and delivery metadata such as the time of dispatch and whether the message was accepted by the receiving server. Emails are sent from the EU sending region (Ireland); the account data and the delivery logs are stored in the USA; Service provider: Plus Five Five, Inc. (Resend), 2261 Market Street #5039, San Francisco, CA 94114, USA; Legal basis: Contract fulfillment and pre-contractual inquiries (Art. 6 (1) (b) GDPR); Website: https://resend.com; Privacy policy: https://resend.com/legal/privacy-policy; Data processing agreement: https://resend.com/legal/dpa. Basis for third country transfers: Data Privacy Framework (DPF), standard contractual clauses.
Browser extensions
This section covers the Chrome extensions that TacOps publishes. Each paragraph applies to an extension from the day that extension is available in the Chrome Web Store. None of these extensions has analytics or an account. When you choose a link to TacOps in an extension, your browser opens that page, and this privacy policy applies there. The link carries a marker that tells us the visit came from an extension. It does not identify you.
Military Symbol Maker does not send data to us or to anyone else, and it does not read the pages you visit. It stores your recent symbols, favorites, settings, and last draft on your device, in the storage of your browser. That can include text that you type into a symbol. To remove this data, choose Clear saved symbols in the extension, or uninstall the extension.
Zulu Time: DTG and Military Time Converter collects nothing and makes no network calls. It saves your pinned zones and display choices in your browser's sync storage. That storage stays on your device when Chrome sync is off, and it leaves your device only through your own Chrome sync. The times and operation names that you type stay in the open popup and are gone when it closes. The extension writes to your clipboard when you click, and it never reads your clipboard. The link to TacOps does not contain the operation name or the time.
Workshop Mod Lists for Arma Reforger and Arma 3 stores your mod lists on your device,
in the storage of your browser. Removing the extension deletes them, so use Export to keep a backup.
A config.json that you paste stays in the memory of the open panel only. It is never
stored, logged, or sent. The extension reads data from the Workshop pages you open in your browser
and sends that data nowhere. It makes three kinds of request. Once a day it fetches the public map
list from TacOps, with no cookies and no list data, and we process that request as described in
Provision of online services and web hosting. It requests the same Arma Reforger
mod pages from Bohemia Interactive that a browser requests, without cookies. If you click to check
Arma 3 items and grant the permission that Chrome asks for, it sends the mod ids to the Steam Web API
of Valve. The extension has no telemetry, crash reports, or remote configuration.
MGRS Converter for Google Maps™ collects no personal data, keeps no history, and makes no network request of its own. It reads the address of the current tab only when you click its icon, and it discards that address when the popup closes. Text that you paste or select stays in the popup until it closes. Selected text passes briefly through the session storage of your browser and is removed when the popup reads it. The extension stores one setting, your chosen precision, until you uninstall it. If you click a map link, your browser opens that map site with the position you converted, as with any link.
Changes and updates
We ask you to regularly review the content of our privacy policy. We will amend the privacy policy as soon as changes to the data processing we carry out make this necessary . We will inform you as soon as the changes require action on your part (e.g. consent) or other individual notification.
If we provide addresses and contact information for companies and organizations in this privacy policy, note that the addresses may change over time. Check the information before you contact them.
When this policy changes, the app shows a short summary of the change the next time you open it, and asks you to confirm that you have read it. For an account, we store the policy version you confirmed and the time you confirmed it with your account, include both in your data export, and delete them when you delete your account. Without an account, your browser stores the version you confirmed on your device only. Shared plan pages and other read-only views do not show the notice. Legal basis: legitimate interests (Art. 6(1)(f) GDPR) in showing that we informed you of the change.
Changes to this policy
Each change to this policy, newest first, with a short summary of what changed.
-
When you share a plan that uses your own custom map, we now store the map image so that the people you share it with can see it. We also name the storage of share preview images and our contact point under the Digital Services Act, and how we handle reports about shared maps.
-
We added a section on the data handling of the TacOps Chrome extensions.
-
When you create an account, we store the date and time you confirmed that you are 16 or older. We never ask for or store your date of birth.
-
We no longer store IP addresses for sign-ins and the shared plan access log. We store a keyed one-way hash instead, which still lets us spot a blocked person who comes back.
-
We list the activity and first-use dates we keep with your account, the account merge record, and how we delete your analytics event details when you delete your account.
-
We describe the sign-up source we store on a new account: the referrer domain, the first page, and campaign tags.
-
We list page load performance (Web Vitals) among the rounded app statistics we collect.
-
We describe the short-lived functional cookie and bounded security records used when protection against sustained bulk map copying is enabled. These records stay separate from aggregate map-usage statistics and do not use browser fingerprinting. We also describe grouped operator alerts and their bounded duplicate-prevention record.
-
When you sign in, TacOps now records the time, the IP address, and the browser type, and keeps that record for 90 days to protect the service against abuse. If we block a person from TacOps, we keep the identifiers of their accounts for as long as the block lasts.
-
The app now records a coarse hardware class (low, mid, or high), worked out from your device's processor core count and memory, never the numbers themselves. It also records how smoothly the map draws and how fast it responds. When this policy changes, the app now tells you and records that you confirmed it.
Definition of terms
This section provides an overview of the terms used in this privacy policy. Where the terms are defined by law, their legal definitions apply. The following explanations are primarily intended to aid understanding.
- Inventory data: Inventory data includes essential information necessary for the identification and management of contractual partners, user accounts, profiles, and similar assignments. This data may include personal and demographic information such as names, contact information (addresses, phone numbers, email addresses), dates of birth, and specific identifiers (user IDs). Inventory data forms the basis for any formal interaction between individuals and services, facilities, or systems by enabling unique assignment and communication.
- Content data: Content data includes information generated in the course of creating, editing, and publishing content of all kinds. This category of data can include text, images, videos, audio files, and other multimedia content published on various platforms and media. Content data Content data is not limited to the actual content itself, but also includes metadata that provides information about the content, such as tags, descriptions, author information, and publication dates.
- Contact data: Contact data is essential information that enables communication with individuals or organizations. It includes telephone numbers, postal addresses, and email addresses, as well as communication tools such as social media handles and instant messaging identifiers.
- Meta, communication, and procedural data: Meta, communication, and procedural data are categories that contain information about how data is processed, transmitted, and managed . Meta data, also known as data about data, includes information that describes the context, origin, and structure of other data. It may include details such as file size, creation date, the author of a document, and change histories. Communication data captures the exchange of information between users across various channels, such as email correspondence, call logs, social media messages and chat histories, including the individuals involved, timestamps, and transmission routes. Process data describes the processes and procedures within systems or organizations, including workflow documentation, transaction and activity logs, and audit logs used to track and review operations.
- Usage data: Usage data refers to information that captures how users interact with digital products, services, or platforms. This data includes a wide range of information that shows how users use applications, which features they prefer, how long they stay on certain pages, and the paths they take through an application. Usage data can also include frequency of use, timestamps of activities, IP addresses, device information, and location data . It is particularly valuable for analyzing user behavior, optimizing user experiences, personalizing content, and improving products or services. In addition, usage data plays a crucial role in identifying trends, preferences, and potential problem areas within digital offerings.
- Personal data: "Personal data" is any information relating to an identified or identifiable natural person (hereinafter "data subject"); a natural person is considered identifiable if they can be identified, directly or indirectly, in particular by means of assignment to an identifier such as a name, an identification number, location data, an online identifier (e.g., cookie) or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that natural person.
- Profiles with user-related information: The processing of "profiles with user-related information," or "profiles" for short, includes any type of automated processing of personal data that consists of using this personal data to analyze certain personal aspects relating to a natural person (depending on the type of profiling, this may include various information relating to demographics, behavior, and interests, such as interaction with websites and their content, etc.) in order to analyze, evaluate, or predict them (e.g., interest in certain content or products, click behavior on a website, or location). Cookies and web beacons are often used for profiling purposes.
- Log data: Log data is information about events or activities that have been logged in a system or network. This data typically contains information such as timestamps, IP addresses, user actions, error messages, and other details about the use or operation of a system. Log data is often used to analyze system problems, monitor security, or create performance reports.
- Reach measurement: Reach measurement (also known as web analytics) is used to evaluate visitor traffic to an online offering and can include the behavior or interests of visitors in certain information, such as website content. With the help of reach analysis , operators of online offerings can, for example, identify at what time users visit their websites and what content they are interested in. This enables them, for example, to better tailor the content of their websites to the needs of their visitors. For the purposes of reach analysis, pseudonymous cookies and web beacons are often used to recognize returning visitors and thus obtain more accurate analyses of the use of an online service .
- Tracking: "Tracking" refers to the ability to trace user behavior across multiple online offerings. As a rule, behavioral and interest-related information about users is stored in cookies or on servers of tracking technology providers (so-called profiling). This information can then be used, for example, to display ads likely to match users' interests.
- Audience building: Audience building (often called "custom audiences") refers to defining target groups for advertising purposes. For example, based on a user's interest in specific products or topics, it may be inferred that this user is interested in ads for similar products. "Lookalike audiences" refers to showing content to users whose assumed profiles or interests are similar to users for whom profiles were originally built. Cookies and web beacons are commonly used for this purpose.
- Controller: The "controller" is the natural or legal person, authority, agency, or other body that, alone or jointly with others, determines the purposes and means of the processing of personal data.
- Processing: "Processing" means any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means. The term is broad and covers virtually every interaction with data, whether it is collection, evaluation, storage, transmission, or deletion.
Created with the free Datenschutz-Generator.de by Dr. Thomas Schwenke