Offer, analysis allowances and technical conditions

• First purchase of MapEngine: 365 days of access. The current net price is shown in the Pricing page on the MapEngine website and in the portal before an order is placed.
• Continuation: EUR 249 net for the next 365 days. Customers who pay for the first purchase by 31 December 2026 inclusive (23:59:59 Polish time, according to confirmation of payment) are guaranteed this net price for every continuation; later customers do not have this guarantee, and the price of their continuation will be stated before purchase. Details and the effect of a refund: Terms, point 7. The price of the first purchase may change, but only for future orders.
• Applicable tax is added to net prices. A consumer must see the full price payable (including tax and mandatory charges) before placing a binding order; the net price alone is not the final offer for a consumer. The checkout shows the full amount payable, including the tax applicable in your country, before payment.
• A continuation is a separate purchase, with no automatic renewal and no recurring payments. While access is active, a continuation adds 365 days from its end, and after expiry it counts 365 days from the time payment is confirmed. The licence key and the registered computers stay the same.
• Discounts apply only to the first purchase, on the terms of the given code, and never to a continuation.

• The Windows application for the customer: Compare 2D, map table, HEX, Surface 3D, editing of the MOD file, Undo/Redo, interpolation, copying data and increments, and OFFSET alignment – according to the release.
• Map analysis and DTC decoding for supported patterns work through the online service. The library of patterns stays on my side.
• The account in the portal: management of the licence and computers, support requests and the functions available for your access status.
• Updates released during the paid period – according to the offer.
• Within the allowances there is no additional charge for individual analyses.

• Maps – different files (different content) – In a full UTC hour: 10; In a UTC day: 40
• Maps – all completed analyses, including repeats – In a full UTC hour: 30; In a UTC day: 200
• DTC – completed analyses, including repeats – In a full UTC hour: no separate hourly allowance; In a UTC day: 10

• You can have one active job at a time per account – shared by maps and DTC.
• The largest file for analysis: 16 MiB (exactly 16,777,216 bytes). Files smaller than 64 bytes are rejected.
• A queue or a technical rate limit may temporarily refuse to accept a job even if you have a free allowance. These are not additional paid analyses and not consent to permanent non-performance of the service.
• Allowances belong to the account, not to a file name, a program window, a key or a computer. Regenerating the key, changing computer and reinstalling do not reset allowances.
• I count in UTC: an hour starts on the full hour (for example 14:00:00–14:59:59), and a day at 00:00 UTC. The hourly allowance resets on the full UTC hour and the daily one at 00:00 UTC. Changing the clock or time zone in Windows does not give an earlier reset. These are not “rolling” windows (60 minutes or 24 hours).
• An unused allowance does not carry over to the next period and cannot be exchanged for money.

• The allowance is reduced only when an analysis finishes successfully and gives a non-empty result, saved for collection.
• The allowance is not used up by: an error, an unsupported file, an empty result, cancellation before the analysis ends, a file not sent, a lost connection or a failure on my side.
• A job in progress reserves a place in the allowance until it ends. This may briefly make it harder to start the next job, but does not reduce your counter.
• If an analysis finished successfully on my side and you then cancel it or lose the connection, the analysis remains counted. You can collect the result again, without sending the file again and without being counted a second time, for as long as it is available (about 15 minutes from completion).
• Reading again a result you already have is not a new analysis.
• Whether a file is “the same” is decided by its content (SHA-256 hash). Changing only the name does not make it a new file.
• 24-hour exception for maps: if your account has successfully analysed the same content within the last 24 hours, the next analysis of that file does not take another place in the “different files” allowance. The repeat still counts towards the allowance of completed analyses (30 per hour and 200 per day). So the exception frees you from one allowance; it does not mean that every number on the bar stays unchanged.
• DTC has no such exception: every completed DTC analysis, including a repeat, counts towards the allowance of 10 per day. DTC does not reduce map allowances and vice versa. A DTC analysis gives no exemption for maps.
• Editing files in the program, saving a MOD, Undo/Redo and refreshing counters do not use up the allowance.

The bar at the bottom of the program shows how much you can still do, not how much you have used (in the form “remaining/allowance”).

• “Maps · new files: 0/10 h · 28/40 d” means: in this hour nothing is left of the different-files allowance, and in this day – 28.
• “Maps · jobs: 20/30 h · 188/200 d” means: 20 analyses are left in the hour and 188 in the day.
• “DTC: 0/10 day” means: the daily DTC allowance has been used.
• In that case a known map file may still pass under the 24-hour exception, if you have a free allowance of completed analyses.

The bar counts down the time to reset and has a “Refresh counters” button. I fetch the data when the program starts, roughly once a minute, after an analysis and at reset. The number shown may be briefly out of date; on an error I mark it as out of date and do not show the full allowance. The server always decides whether a job is accepted. Reading the counters may refresh licence and security verification data, but does not send the ORI file and does not create an analysis.

• Windows 10 or 11, 64-bit, with .NET Framework 4.x. The program does not run on 32-bit Windows, Windows 7 or Windows 8.
• Minimum: 8 GB RAM and a display resolution of at least 1600 × 900. At resolutions below 1600 × 900, the program window is not optimal and work is harder.
• You need space to save files, projects, copies and updates. The size of the EXE file does not reflect the full disk and memory needs. For large files and many results the requirements may be higher.
• The program requires active access and the internet when it starts, when checking entitlement and for new analyses. There is no offline mode. Losing the connection does not by itself close work in progress, but it will prevent a new analysis and the next start.
• If the service is not working and a job has not been created, you do not use up an allowance.
• I assess cooperation with programming tools, antivirus and firewall according to the real requirements and the cause of the problem.

• The program does not contain ready-made definitions of all maps. It judges and filters suggestions based on similarity to patterns, so a result may be missing for a given controller or map. You check controller-family coverage in the “Database capabilities” tab on mapengine.pro. The number of families and definitions describes the library.
• The AI Similarity setting changes the matching threshold; a lower threshold may give less precise suggestions.
• The HIGH, MEDIUM and REVIEW labels and the confidence indicator need your verification.
• Recognition is based on similarity to patterns derived from original files. Use an unmodified read as the ORI. A modified file loaded as the ORI can produce a weaker match.
• Format, sign, byte order, factor, offset and alignment must agree with the real data. A neat chart of the Y axis or a 2D fragment does not prove that a definition is correct. OFFSET alignment also requires your judgement.
• The DTC function (F6) decodes DTC codes when you ask and shows recognised codes, descriptions and a state assessed from the file. It is not a live diagnosis of the vehicle; the state may be undetermined. The program does not write DTC changes to the file.
• Modified files and their checksums must be checked separately. The program does not program a controller in a vehicle.

• Support: requests and attachments, up to 5 files per message, each up to 8 MiB (8,388,608 bytes). Support attachments are not deleted as quickly as files for analysis. Do not send passwords, keys, unnecessary personal data or materials you have no right to. I aim to reply within 2 working days. Statutory complaint deadlines are unchanged.
• Wishlist: an account with active access (or granted trial access) receives 3 votes and may submit up to 3 suggestions per voting week. The week runs from Saturday 00:00 to the next Saturday 00:00 Europe/Warsaw time (taking account of clock changes), which differs from the reset of analysis allowances (UTC). Suggestions are moderated. Votes show interest; they are not an order or a promise of a date for adding a family. Specific promises made in the offer still bind me.

I release updates through one official channel. The program may show a notification and a description of changes; I do not force installation. Downloading requires valid entitlement and a connection. The release of a future version is not a promise that all functions will remain for ever. Necessary updates and significant changes to the paid service are governed by law. After the period ends I do not automatically collect a further payment, and expiry of access does not delete your files.