Privacy Policy

AutoMint (automint.online) is operated by its developer, AutoMint-HilFing. In this Policy, “AutoMint,” “we,” “us” and “our” refer to that operator. Privacy and deletion requests are handled at [email protected].

This Policy explains how AutoMint processes information through its website, escrow, marketplace, messaging, exchange-discovery features, Account Services, native applications, connected Discord services and related features. Account Services include AutoSec, My Accounts securing and storage, and supported account transfers.

It covers information supplied directly, information obtained through supported integrations and information derived through service operation.

In this Policy, “personal information” or “personal data” means information that identifies an individual or can reasonably be linked to one. Privacy law often refers to that individual as the “data subject”. For example, a wallet address may identify a transaction on a public network. Once you provide that address for a Deal, AutoMint may also be able to associate it with your role in the transaction.

A “Deal” is a transaction administered through AutoMint’s escrow service. A “counterparty” is the person on the other side of that transaction. References to an account can mean your AutoMint profile or an external account you ask us to secure, store or transfer. The information needed to administer a Deal depends on which of those services you use.

Different features process different categories of information. Using one feature does not mean every category described below is collected in every case.

This Policy does not waive your rights or constitute blanket consent to processing that legally requires consent.

Player versus Player.

This Policy also covers Paper practice, funded Live PvP Matches, related community channels and the processing necessary to administer participant funds. In this Policy, an escrow Deal and a PvP Match are distinct transactions.

Information may come from:

• You, including forms, messages, uploads and instructions.
• Devices, browsers and applications used to access the Services.
• Counterparties, support personnel and other participants.
• Connected authentication and verification providers.
• Blockchain records and infrastructure providers.
• Account-security and game-service providers.
• Relevant public profiles or records.
• Connected community and historical transaction records.
• Security, moderation, diagnostic and operational systems.

Another participant may provide communications, attachments, identifiers or evidence concerning you.

For example, a buyer asking about delivery may supply a conversation with a seller, and a seller challenging a payment may provide a transaction reference that relates to both participants. This information may reach AutoMint even if you did not submit the support request. When submitting evidence, include enough context to identify the issue and leave out unrelated correspondence or information about other people.

Where an identity is linked through an applicable feature, existing records may become associated with that identity or profile.

Account and profile information

This may include usernames, display names, email addresses, provider identifiers, avatars, biographies, settings, roles and account status.

Authentication and authorisation information

We collect sign-in and session records, permissions for connected services, and information about authorised devices, access times and revocations.

Transactions and purchases

This may include Deal and order identifiers, assets, networks, amounts, deposit and destination addresses, transaction references, fees, tips, entitlements, status and settlement history.

Communications and submitted content

This may include Deal chats, direct messages, marketplace communications, support messages, listings, screenshots, files, page submissions, design conversations and transcripts.

Account-service information

Depending on the Account Service, we may process private sign-in and recovery details that you provide or that we generate while carrying out the service. These details can include passwords, authentication secrets, verification codes and session tokens. We may also process account security settings, current and past versions of those details, records of work carried out, mailbox information, game profiles and account check results.

Security and abuse-prevention information

To detect fraud, impersonation and misuse, we use account and contact details, device and network information (including browser details and IP addresses), profile content, transaction activity and moderation records. We may use this information to identify related accounts.

We obtain approximate location and connection information from DB-IP under the CC-BY 4.0 licence.

Usage and diagnostic information

This may include features used, actions, timestamps, application versions, operating-system and environment information, persistent identifiers, errors and performance information.

Notifications and preferences

This may include delivery destinations, device notification tokens, subscription preferences, language or display preferences and delivery status.

Derived information

We may derive moderation assessments, account-linkage findings, service statistics, reputation information, risk indicators and aggregated measurements from the relevant records.

A record of an event and an assessment of that event have different meanings. A transaction reference can help locate a payment. A report by a participant records what that person said happened. An account association or moderation finding reflects a conclusion drawn from the available information. If you challenge a record, identify the event, report or conclusion that you believe is inaccurate.

Information in requests and evidence

Support, privacy, rights or legal requests may include additional information supplied to explain the issue or establish identity, control or authority.

Do not submit unrelated sensitive information merely because a message or file can be uploaded.

PvP records.

For Live Matches we may process account and player identities, invitations, accepted terms and timing, game settings, actions and results, room messages and attachments, deposit and withdrawal addresses, transaction references, stakes, awards, fees and tips. AutoMint uses these records to administer Matches and room balances, handle payment instructions, deliver notices, investigate disputed results and respond to lawful requests. Counterparties, authorised personnel, blockchain and notification providers, and viewers entitled to see the relevant information receive the details needed for their respective roles.

Paper practice.

Simulated Paper balances, statistics and practice history may be stored in the browser. Clearing browser data can remove those records. Shared community messages sent from Paper mode reach AutoMint and the applicable channel audience. Paper practice records do not establish a Live financial entitlement.

We use information for the following purposes.

• Providing requested services: Authentication, escrow, purchases, account operations, custody, delivery and transfers
• Communications: Deal messages, support responses, requested notifications and service notices
• Security and safety: Fraud prevention, impersonation detection, account-linkage analysis, access control and moderation
• Disputes and accountability: Evidence review, settlement records, consent history and complaint handling
• Reliability and improvement: Diagnostics, service analytics, usage measurement and dispute-quality review
• Legal obligations: Applicable preservation, reporting, disclosure and rights-request requirements

A “lawful basis” is the legal ground for a particular use of personal data. Where applicable law requires a lawful basis, the relevant ground may include one or more of the following.

• Performance of a requested contract.
• Legitimate interests in operating and protecting the Services, subject to applicable necessity and balancing requirements.
• Compliance with legal obligations.
• Consent where required or where we specifically rely on it.

The appropriate basis depends on the processing. The existence of a contract does not automatically make every unrelated use necessary for that contract.

For example, when you request an escrow payout, we use the Deal record, the required authorisation, the asset and network, and the destination details to carry out that request. Without the necessary destination or authorisation, we may be unable to complete the transfer. If the same Deal is later disputed, examining its messages and payment history serves the separate purpose of determining what happened and who is entitled to settlement.

Where we rely on legitimate interests, we consider the purpose of the use, the information reasonably needed and the effect on the people concerned. Investigating suspected impersonation and diagnosing repeated application errors involve different information and different interests. A legal requirement to preserve a particular record applies to the material needed for that obligation. You can ask us which purpose and basis apply to information about you.

Where consent is the relevant basis, withdrawal affects future processing based on that consent, subject to applicable law.

Authorised staff may review relevant Deal chats, direct messages, support requests and attachments to help users, resolve disputes, investigate abuse, administer the Services or meet legal obligations. Recipients may keep their own copies.

Use the designated private fields for any sign-in or recovery details needed for the authorised service. Private details shared in ordinary messages or attachments can appear in moderation reviews and transcripts. Editing or deleting a message may leave copies in an earlier transcript, quotation, backup or recipient’s possession.

A screenshot of a delivery problem might also show another person’s email address, a private conversation or private sign-in or recovery details. Before sending it, check the whole image and remove unrelated details while keeping the evidence relevant to the issue. If you discover that you shared information by mistake, identify the message or attachment when contacting support. Avoid sending another copy of the sensitive material.

We use automated systems, including external AI analysis providers, to review marketplace content, detect impersonation and linked accounts, analyse Deals and service use, and assess dispute-handling quality. These systems may process relevant messages, device and account information, profile images and transaction activity.

A review of how staff handled a dispute may include direct messages between support staff and the Deal participants during that dispute. Staff decide contested escrow settlements.

An automated finding may lead to content removal, a timeout or an account restriction without advance human review. Restrictions may extend to accounts we identify as linked. You can challenge a finding through official support and request any review available under applicable law.

When requesting review, identify the affected account, listing, message or Deal and explain which fact or association you dispute. For example, if a restriction affects a separate account you control, say which action you want reviewed and why you believe its basis is inaccurate. This helps staff distinguish a challenge to an account restriction from a dispute over payment or delivery.

PvP results and review.

Live Match actions and accepted rules determine competitive results. AutoMint also uses relevant activity and Match records to investigate collusion, manipulation and disputed outcomes. Competitive results may be excluded from statistics following review. A statistical exclusion, an account restriction and the settlement of real funds serve different purposes. Affected Players may raise a factual error or challenge a decision through official support.

For an authorised Account Service, we exchange relevant information with the providers that help carry out the work and with the account or game provider, including Microsoft or Minecraft. We use that information to carry out requested account security changes, check access and account condition, deliver or return access, and investigate problems.

We retain the private sign-in and recovery details we receive or generate, including earlier versions, as described in Data retention. We encrypt these details in storage. Authorised systems use them to carry out requested work, and authorised personnel may access them when necessary for investigation, recovery or maintenance.

AutoSec may access mailbox messages, information about those messages and account activity to protect the account, verify or recover access, or investigate a problem. This can include unrelated messages. We limit our use of that information to what these purposes reasonably require.

An authorised buyer, owner or return recipient may receive the details they need to access the account. Recipients may keep copies of those details beyond our control. AutoMint remains responsible for processing carried out on its behalf.

An account transfer can involve information about both the person submitting the account and the person entitled to receive it. The recipient may need current login or recovery details to take control of the account. Keeping an earlier credential for an authorised operation, or inspecting mailbox information to verify access, does not by itself entitle the recipient to that history or correspondence. Access depends on the operation you authorised and the account’s custody status.

AutoSec subscriptions and activity

We link a pass to the subscriber’s Web account. We record the tier, paid and granted periods, start and end dates, and changes to allowances or coverage. For a checkout we record the invoice and support references, the quoted price and surcharge, payment asset and network, wallet address, amounts observed and confirmed, transaction references, payment status, and any review or correction. When the checkout is created, we record which version of the Terms was accepted, when it was accepted and, where available, the IP address and browser or app information associated with that acceptance.

We use these records to provide purchased time, verify payments, apply the correct limits and fees, resolve billing questions and account for transactions. To administer allowances, we record additions that are pending, completed or released and the relevant times. The subscription activity view shows the signed-in subscriber their completed addition counts, current holdings and accounts in private custody, and counts of completed private transfers they sent or received. The available seven- and 30-day activity views are reporting periods.

When a pass qualifies an AutoSec escrow agreement for reduced fee floors, the agreed pricing is visible to both participants. That price can reveal that one participant has a qualifying pass. The price display does not give the counterparty access to the subscriber’s invoices, usage history or private activity view.

Authorised personnel use the relevant records for support, payment review and adjustments. Blockchain providers process the details needed to verify or collect a payment, and on-chain transfers may be publicly visible. Receipts, expiry reminders and tier-change notices may be delivered through AutoMint messages or notifications and, depending on connections and settings, through email, Discord, Telegram or push. We use the destination, preferences and delivery status for that purpose. The channel may receive the tier, term dates or receipt details included in its message. Push previews direct the user to My Accounts for details.

You can link different Discord identities for sign-in, notifications and server verification. Each connection is managed separately. Verification can associate your Discord identity with server roles and names, transaction and moderation records, statistics and hosted transcripts.

With your permission, we retain encrypted Discord authorisation to add or re-add your account to official AutoMint servers. This authorisation is removed when you unlink Discord server verification. You can disconnect other links separately.

Discord processes information sent through its services under its own policies. Unlinking or deleting information on Discord may leave records AutoMint already holds for transactions, security, moderation or transcripts.

If you use one Discord identity to sign in and another for server verification, identify the connection you mean when asking for help. A request to stop Discord notifications concerns message delivery. A request about the identity attached to a hosted Deal transcript concerns server verification. Specifying the connection helps us locate the records relevant to your request.

Managing permissions.

You may also revoke the application’s permission in Discord’s authorised-app settings. If a verification request expires before completion, a new request may be necessary. Provider-side revocation affects the provider’s authorisation. AutoMint’s separate connection controls and retention rules apply to information already held.

Desktop diagnostics

The desktop app may send diagnostic events, a persistent installation or device identifier, and information about the app, operating system, hardware and regional settings. These records may be linked to your account. You can turn off detailed feature-usage events in the app. Authentication, security and requested functions still use the information they need.

Android notifications

To send push notifications, we associate a delivery token with your account or installation and share the information needed for delivery with notification providers. Your device settings control where messages appear, including on the lock screen.

MintAuth

Linking MintAuth leaves your existing local account library on your device. Cloud saving and synchronisation follow your choices. Validation may contact Minecraft even for an account saved only on your device. MintAuth keeps its diagnostic records locally.

Revoking a device stops future authorised access. It may also request clearing of local credentials, including accounts you imported only on that device. Credentials already copied may remain available. Manage cloud-saved credentials separately. Copies held in other apps or for an active transaction may remain.

If you lose your device or the means to unlock it, local credentials may be unrecoverable. Separately saved cloud credentials may still be available after reauthorisation.

Desktop diagnostic choices.

The desktop application stores an installation identifier on the device. Diagnostic events help us investigate crashes and reliability issues and can be associated with your account. You can turn off detailed feature-usage events in the application or contact AutoMint to request deletion or object to processing where applicable.

Depending on the feature, information may be disclosed to:

• Counterparties and intended recipients: Transactions, communications and authorised account delivery
• Authorised personnel: Support, administration, investigation, recovery and security
• Hosting and storage providers: Operating infrastructure and retaining records
• Authentication and connected platforms: Sign-in, identity linking and platform functions
• Blockchain infrastructure providers: Querying records and submitting transactions
• Account-security and game providers: Authorised securing, validation and account operations
• AI and moderation providers: Selected analysis and moderation, including processing by Groq
• Notification and email providers: Message delivery, including Android push notifications through Google Firebase
• Diagnostic and analytics providers: Reliability and usage measurement
• Public viewers and transcript recipients: Applicable public or shared features
• Authorities and other lawful recipients: Legally required or otherwise lawfully justified disclosure

Not every recipient receives every category of information.

Where applicable law uses these terms, a “controller” determines the purposes and means of processing personal data. A “processor” handles personal data on a controller’s behalf and under its instructions. The role depends on the activity. AutoMint determines why it needs Deal records to administer escrow. A provider delivering a notification on our instructions may act as a processor for that delivery. A connected platform may separately determine how it manages accounts on its own service.

Consider a Deal involving an account transfer. The counterparty may receive information needed to establish what is being traded. The account-security provider receives information needed to carry out authorised changes. Blockchain providers process the details needed to submit or confirm the payment. A person viewing a public listing may see the advertised account details. Being able to view that listing does not authorise them to collect credentials or obtain the participants’ private messages.

Providers may have different technical settings, retention practices and contractual terms, according to their role and the service involved.

We do not sell personal information. We do not rent or trade personal information to third parties for marketing purposes.

Public features

Profiles, listings, marketplace content, pages, reputation information and other public features may be visible to their applicable audience.

Publicly posting information may allow others to copy, index, screenshot or retain it.

Routine trade summaries

Routine summaries may disclose participant identifiers and transaction-related information under the relevant feature and visibility settings.

These summaries are distinct from full Deal transcripts.

Ordinary escrow Deal transcript links

AutoMint may automatically generate a shareable transcript after settlement and deliver its link privately to the participants. Eligible participants may also create or obtain a link.

Anyone possessing the link may be able to view the transcript without signing in.

Links do not necessarily expire merely because a Deal ends or an account setting changes. Do not assume a general ability to recall every previously shared copy.

AutoSec summaries

Structured AutoSec summaries may include game usernames, statistics and redacted check results.

Those structured summaries exclude credentials, recovery secrets, session tokens and account-login email addresses.

Ordinary chat messages and attachments may still contain secrets manually supplied by users. Review the transcript before sharing it.

Before forwarding a link, consider the people identified in the conversation as well as the information you submitted yourself. A screenshot may identify someone by a different username, and a payment reference may let a viewer associate a participant with public blockchain activity. A recipient can forward the link, save a copy or make a screenshot. A copy they keep may remain available after the original record changes.

Verification tools

Public verification tools may return limited exact-match evidence concerning supplied identifiers, recorded relationships or transaction states.

That disclosure is distinct from opening private account records or Deal communications to the public.

Blockchain records

Public blockchain information may include addresses, amounts, transaction references and timing.

Information may become associated with a person when combined with other sources.

AutoMint cannot erase or rewrite public blockchain records.

Community trade summaries.

Completed escrow Deals may generate summaries in AutoMint community trade channels. Depending on the applicable visibility choices, a summary may show participant names, the asset or network, an amount, the transaction reference and completion time. Routine summaries omit private Deal messages and credentials. Public blockchain information can still identify a transaction even if a participant’s name is hidden.

PvP archives have separate access rules.

The shareable-link rule above concerns ordinary escrow Deal transcripts. A PvP Match transcript or replay requires sign-in and permission for the relevant room. Reserving a seat for an invited opponent can still allow eligible spectators to watch. A private-room invitation alone does not entitle the invitee to read its private archive.

PvP visibility and recipients.

The room’s visibility can affect who sees player names, avatars, permitted game actions, pot information, results, room chat and attachments. Wins and tips from public rooms, including publicly viewable rooms with an invited opponent, may appear in community feeds. Eligible results from private Matches may count towards named profile statistics and leaderboard totals without publishing the individual private Match. Authorised personnel may review relevant room records for support, settlement, moderation or security. Enabled notification channels may deliver invitations, results or payment updates to the intended account, and a recipient can retain a copy.

We use cookies and related technologies for sign-in, security, preferences and service operation. Google Analytics may measure page views, approximate location and device or browser information. We configure analytics to limit identifying information. Our own records of feature use may be linked to your account or a persistent identifier.

You can manage cookies in your browser or use the Google Analytics opt-out browser add-on. Google describes its processing in its Privacy Policy. Opting out of Google Analytics still allows AutoMint to keep separate transaction, security and operational records.

You can withdraw consent for processing that relies on it. Other objection rights depend on the processing and applicable law.

We keep information according to its purpose, including active services, unresolved custody or disputes, security, accounting and legal requirements. We consider whether a less identifying record would serve the same purpose.

• Account and profile information: Generally while the account remains active or as necessary to provide the Services; specific records may remain following closure for justified purposes
• Transaction and escrow records: A minimum of two years after completion, with longer retention where justified by unresolved disputes, fraud prevention, enforcement, accounting or legal requirements
• Routine session logs: A standard period of 90 days, subject to specific preservation needs
• Security, device-linkage and moderation records: According to the continuing investigation, enforcement, repeat-abuse prevention or legal purpose; these are distinct from routine session logs
• Ordinary messages and submitted content: According to the relevant feature, conversation, transaction and preservation purposes; previously created copies may remain separately
• Diagnostics and usage records: According to the reliability, security or measurement purpose; aggregates may be retained separately where they no longer identify an individual
• Public blockchain records: Outside AutoMint’s deletion control
• Recipient-held copies: Subject to the recipient’s own possession and obligations, rather than a guarantee of universal recall

AutoSec credentials and private account-security records

We retain current and historical credential information while the associated account remains saved with AutoMint or is required for an active custody, delivery or return process.

After the account is removed and those processes have concluded:

• Credential material and associated private account-security records are deleted from active storage within 30 days.
• Corresponding restricted backup copies are deleted within 90 days, measured from the same date.

The corresponding schedule applies to copies processed on our behalf by our account-security providers.

For example, if an authorised return is the last reason we still hold a removed account’s credentials, both periods start when that return concludes. If no custody, delivery or return process remains, both periods start when the account is no longer saved with AutoMint. The backup period runs from the same event as the active-storage period. A separate fee or settlement record can still be needed for the Deal after the credentials associated with it have been deleted.

A specific legal preservation requirement may extend retention of necessary material. Separate non-secret transaction, consent, delivery, security and dispute records follow their applicable rules.

Removing an account from one person’s library does not necessarily remove information still required for an authorised recipient or unresolved custody process.

AutoSec pass records

Completed pass purchases and related financial corrections follow the transaction-record minimum of two years after completion of the relevant transaction. We may keep them longer for the reasons stated in this section. We retain non-financial allowance and usage records, activity summaries, adjustment details and notice-delivery records according to the purposes they serve, including applying rolling limits, administering lifetime free additions, supporting a current or queued term, and resolving a specific dispute. The end of a pass does not start the 30-day active-storage or 90-day backup deletion periods for account credentials. Those periods start when the saved account is removed and any active custody, delivery or return has concluded.

PvP retention.

We retain funded PvP financial records, including deposits, reserved stakes, settlement credits, game fees, corrections and withdrawals, for a minimum of two years after completion of the relevant transaction. An unresolved claim, a specific preservation obligation or another applicable reason set out in this section can require longer retention. Gameplay, chat, attachments, replays and fair-play review records follow the purpose-based criteria for the activity concerned. The two-year minimum applies to their financial record, not automatically to every associated message or replay.

You can request account deletion through the account-deletion page or official support. We assess each category of information separately. Where applicable law allows or requires retention, we keep only the information needed for that purpose. The periods above explain what may remain after closure.

You can also describe a narrower issue, such as an incorrect profile detail, information included in a particular attachment, or a saved account you no longer wish us to hold. Identify the record and the outcome you seek. The request can then be assessed in light of who controls the copy, the interests of any other participant and the reasons the information is still held.

Unlinking a provider ends the relevant connection. Revoking a device stops its future authorised access. To remove a saved token, use the controls for the place where you saved it. Deleting a cloud token removes the usable token from cloud storage, while limited status or audit records may remain. Local and recipient-held copies may still exist.

Removing a saved account is subject to the rights of an authorised recipient and completion of any active custody, delivery or return. Closing your account leaves public blockchain records and records needed for unresolved obligations in place.

We protect information with access controls, authentication, encryption for sensitive material, monitoring and audit records appropriate to the service. Protect your devices and linked accounts, and report suspected unauthorised access through official support.

If a personal-data incident occurs, we will give the notices and meet the deadlines that applicable law requires.

Practical safeguards.

AutoMint’s website uses HTTPS to protect information transmitted between a browser and the service. You can review and revoke active sessions through the dashboard and use available additional authentication to protect sensitive actions. Safeguards reduce the risk of unauthorised access, loss and misuse. If an incident occurs, we assess its effects and meet applicable duties to protect affected people, investigate and give notice.

Information may be retained or disclosed where required by valid legal process or otherwise lawfully justified for an applicable purpose, such as addressing fraud, protecting rights or responding to a claim.

Requests and allegations must be assessed in their context. A third party’s assertion does not automatically establish authority to obtain another person’s information.

Disclosure may be limited, delayed or withheld where appropriate or legally required. In some circumstances, the law may restrict notice to affected users.

If operation of the Services is lawfully transferred as part of a genuine business transfer or reorganisation, relevant records may be transferred subject to applicable obligations and continued protection of users’ rights. This does not authorise unrestricted personal-data brokerage or cancel existing privacy commitments.

Providers and infrastructure may process information in countries different from your own.

Where applicable law requires safeguards for an international transfer, the relevant processing must use an appropriate permitted arrangement.

You may contact [email protected] for information about the locations and safeguards relevant to the processing of your information, including a copy or explanation of applicable safeguards where the law gives you that right. Different providers and services may use different locations and transfer arrangements.

If your question concerns a particular transfer, specify the feature you used, such as account securing, a diagnostic report or notification delivery. The destination and safeguards relevant to one provider may differ from those that apply to another part of the same transaction.

Depending on applicable law and the processing, you may have rights to:

• Access your personal information.
• Correct inaccuracies.
• Request deletion.
• Restrict or object to particular processing.
• Receive eligible information in a portable format.
• Withdraw consent where consent is the relevant basis.
• Obtain applicable safeguards or review concerning automated decisions.
• Complain to the relevant data-protection authority.

To submit a request, use official support or the formal privacy contact identified in this Policy.

Where a right of access applies, you can ask us to explain what personal data we hold about you and how we use it, and to provide a copy of the data covered by that right. A right to data portability, where available, allows you to obtain eligible information in a structured, commonly used, machine-readable form for use elsewhere. Applicable law may limit portability to certain information you provided and particular grounds or methods of processing. The information available to you through access can therefore differ from the information eligible for a portable copy.

We may request proportionate evidence of identity, control or authority. An authorised representative may need to establish their authority.

Requests are assessed with regard to other people’s rights, security, transaction obligations and applicable legal exceptions.

For an access request, give us the account or feature involved and, if helpful, an approximate date or Deal reference. For a correction, describe the disputed information and the correction you seek. If a record contains information about a counterparty or another user, we may need to limit or redact that person’s details when responding. A representative should explain whom they represent and the scope of their authority.

Withdrawing consent, objecting to a use of information and seeking deletion address different outcomes. You may ask to stop future consent-based processing, challenge the grounds for a particular use, request removal of existing records, or combine those requests. Describing each outcome lets us assess it under the applicable rules. If you disagree with a decision, you can raise the specific point with our privacy contact or exercise any available complaint rights.

We aim to respond within 30 days and will comply with applicable statutory deadlines and permitted extension requirements.

A refusal or limitation under an applicable exception does not necessarily affect other parts of the request.

Privacy enquiries.

Questions about privacy, including questions outside a formal rights request, may be sent to the privacy contact. We aim to respond to privacy enquiries within 30 days. Where a statutory deadline governs, we will meet that deadline or follow the extension procedure the law permits.

The Services are intended for people aged 18 or older.

If we become aware that an ineligible minor has used the Services, we may restrict access and take appropriate steps concerning their information.

Some information may still need to be retained for unresolved transactions, safety, investigation or legal obligations.

Contact official support if you believe a minor’s information requires attention.

We may update this Policy to explain changes in processing or applicable requirements.

Material changes will be communicated through existing official channels.

An updated notice does not itself provide consent for processing that legally requires consent.

Operator: AutoMint-HilFing, the developer operating AutoMint (automint.online).

Privacy contact: [email protected].

Account-deletion requests may also be submitted through the account-deletion page.

Official AutoMint support channels may also be used for privacy questions and requests.