JURIST
JURIST ARM public offer2026-10-08.1

JURIST ARM public offer

Edition dated 8 October 2026. Version 1.1.0. ARM service market. Armenian is the governing text; English and Russian translate the same release. The RU market has a different seller and separate documents at https://legal.maxproject.pro/jurist.

Individual Entrepreneur Danielov Ernest Igori (ԱՁ ԴԱՆԻԵԼՈՎ ԷՌՆԵՍՏ ԻԳՈՐԻ), TIN 20124605, registration 286.1561607 dated 19 February 2026. Address: Armenia, Tavush, Dilijan, Moldovakan St., Cottage 70/78, postal code 3901.

support@maxproject.pro · +374 41 091 204

https://jur.maxproject.pro/ · https://app.jurist.maxproject.pro/ · https://legal.maxproject.pro/jur

1. Service and subject

The Provider offers legally capable individuals aged 18 or older access to JURIST, an information and analytical service. One account owns one workspace; projects contain lawfully supplied materials, extracted text, factual matrices, search and draft results. Available functions are described before purchase and use. JURIST is not an advocate, court representative or final legal opinion, creates no advocate-client privilege and guarantees no case outcome. The user checks law, deadlines, evidence, particulars and AI results before consequential action.

2. Acceptance and documents

Specific commercial terms, this offer, privacy policy and notices are shown before an order. A paid order requires a separate explicit acceptance and a confirmed advance payment. Separately granted lawful access without payment requires an explicit acceptance before use; acceptance creates neither payment nor entitlement. Visiting a page, logging in, silence and OAuth do not accept the contract. Privacy acknowledgement, contractual acceptance and optional processing consent are separate. Consent controls start unchecked and are requested individually before dependent functions.

The server records the actually presented locale, revisions and content/rendered hashes, ARM market, seller, release and audience, together with matching governing Armenian evidence. A current complete checkout receipt avoids duplicate first-login acceptance; actual mandatory revision drift requires explicit reacceptance. New texts do not rewrite previous acceptance or paid orders.

3. Prices and payment

The own JURIST server offer specifies price, currency, period, access and separately charged external operations before acceptance. This edition sets no ARM tariff, currency or exchange rate and inherits none from another product. Until own payment/accounting is enabled, it cannot be purchased. Once enabled, own Paynet and the method shown before payment are used; card details stay with the payment provider. A browser return is not payment evidence. No recurring card charge applies without specific separate consent.

Balances and reserves are internal advance accounting, not bank accounts or electronic money. Access and operation accounting is disclosed before purchase; a reservation is not final charging and one confirmed effect is not charged twice. Cabinet product-help requests are service-funded, reserve and debit no user balance, and zero balance alone does not prevent help. Paid provider operations remain closed without own approved ARM accounting.

4. Account and market

One verified email identifies one JURIST owner and workspace across markets. An ARM account belongs to the Armenian Provider above; language, IP, another entry domain or project jurisdiction cannot change the seller. Market migration is not automatic. Users protect passwords, recovery means and second factors. Ordinary login requires verified contact, a permanent password and configured MFA. One-time activation/recovery does not replace a normal session; link validity is disclosed at issuance and a retry creates no second workspace.

5. ChatGPT and Plugin

Users own their ChatGPT account, accept OpenAI terms and separately pay for a suitable plan. The Plugin connects through own OAuth to an existing account. Access entitlement, contract, optional consents and OAuth permissions are checked separately; only enabled authorized commands are available. Connection transfers neither all chats nor all attachments. A ChatGPT file is not received by JURIST without a separately supported transfer and confirmation. Existing cabinet upload follows original/material lifecycle rules.

Connection revocation stops new calls under that permission but does not delete the account, materials or OpenAI chats, terminate the contract or request a refund. A new connection requires authorization again. Purchases and renewals occur outside ChatGPT.

6. Materials, external processing and help

Users retain material rights, ensure lawful collection, transfer and instructions, authority and legal grounds for third-party data, and minimize or anonymize data where possible. Until a separate protected mode exists, do not submit unauthorized protected secrets, special-category or biometric data, minors' data, passwords, keys or full payment credentials. Your consent does not authorize processing other people's data. The Provider processes materials for the chosen operation, security, support and law; it does not sell them or use them for its advertising or training a public model.

AI and external search may send necessary text/parameters to the identified provider on a separate legal ground. Once cabinet help is enabled, the product question and bounded context go to a separately selected model. Help reads only own English FAQ and anonymized examples, answers in the question's language, accesses no projects/files and executes no paid commands. Do not send case materials or secrets to help. It is not a consultation, may err, and has disclosed limits and email support. Publishing these documents enables neither the bot nor new file-transfer methods.

7. Deletion, copies and retention

Available copy, clear and delete functions require owner confirmation. Keep originals and critical results independently; JURIST is not your sole archive. Restoration after deletion is not guaranteed. Account closure, contract termination, connection revocation and monetary claims are separate actions.

| Category | Starting event and period | |---|---| | original upload | delete immediately after terminal processing and verify absence; stuck staging: 86,400 seconds from staged_at | | extraction, matrix, index, project, personal template | workspace lifecycle; confirmed deletion immediately blocks access, physical deletion within one calendar month | | history/undo | 14 calendar days from the change | | export link / artifact | 7 / 14 days from readiness | | verified operational/recovery/offsite backup | 14 days from verification | | unpaid/failed/contact-expired order | 30 days from its terminal event | | paid operational order / provider/accounting evidence | at least 12 calendar months from the applicable event; mandatory legal/accounting schedules may be longer, including at least five years where applicable law requires this | | trial HMAC marker | while the once-ever rule applies, then the applicable dispute/legal-hold period; the marker contains no raw email | | account/contact/session/acceptance/security | the applicable existing category policy and law; no new general period is introduced |

Evidence periods do not extend user-material retention. Restoration must enforce current deletion and access restrictions; a backup must not reactivate a deleted workspace or revoked access. Revoking a connection does not restart retention. External providers have their own disclosed schedules.

8. Encryption and availability

Main infrastructure is in Russia. Encrypted offsite backups and a sealed operational key on an operator node in Kazakhstan are used under a separate choice/legal ground to prevent loss. TLS and disk encryption are not end-to-end: authorized runtime/administrators and external providers can see plaintext during processing. Backups are encrypted before transfer using a separate key; the private decryption key is not stored in Russia/Kazakhstan. Key or infrastructure loss may make data unrecoverable. Planned daily backups retained for 14 days guarantee no strict RPO/RTO or absence of loss.

Absolute uptime is not promised. Maintenance, network, DNS/TLS, infrastructure, platform, AI/payment/mail failures and regulatory/export restrictions may interrupt service. The Provider takes reasonable steps within its control and honors mandatory consumer rights if paid access cannot materially be delivered; third-party involvement does not waive its own responsibility.

9. Withdrawal, refunds and consultation

Send termination or monetary claims to support@maxproject.pro with account email and order details, without secrets. Consumers retain the statutory right to withdraw from a distance contract within 14 days and other mandatory rights. Refunds use the applicable statutory period and original payment method unless a lawful alternative is agreed, accounting for services actually provided and only legally permitted documented expenses. Deletion or OAuth revocation alone is no monetary claim. Defect remedies and mandatory protection in the residence country remain available.

A personal consultation requires a separate published own offer describing price, time, channel, cancellation and settlement before ordering. Payment or booking alone does not mean it was performed. This edition activates no new consultation/payment runtime.

10. Rights, liability and changes

For a statutory withdrawal from a distance contract, received payments are refunded no later than 14 days after receipt of the withdrawal notice, allowing only actually received services as permitted by law. Starting work or providing access alone does not waive that right. On request, materials and data supplied or created by the user are made available free of charge, without unjustified obstacles and within a reasonable time, subject to statutory exceptions. Mandatory rights to retrieve materials survive termination of access.

Code, interface, methods and help belong to their right holders. Users receive a limited non-transferable right within authorized access; bypassing protection, accessing others' data and reselling product configuration are prohibited. Lawful material rights remain; AI output may not be unique. Users check and take responsibility for final use without removing the Provider's statutory liability.

New revisions apply to future acceptance and cannot retrospectively worsen paid terms without lawful grounds. Complaints seek settlement, then a competent authority/court; mandatory pre-action procedures apply only by law. Armenian law applies without excluding mandatory consumer protection in the residence country. Armenian governs; the Russian ARM translation is not a Russian-seller contract.

Privacy and personal data policy — JURIST ARM 2026-10-08.1

Privacy and personal data policy — JURIST ARM

Edition dated 8 October 2026. Version 1.1.0. ARM service market. Armenian is the governing text; English and Russian translate the same release. The RU market has a different seller and separate documents at https://legal.maxproject.pro/jurist.

Individual Entrepreneur Danielov Ernest Igori (ԱՁ ԴԱՆԻԵԼՈՎ ԷՌՆԵՍՏ ԻԳՈՐԻ), TIN 20124605, registration 286.1561607 dated 19 February 2026. Address: Armenia, Tavush, Dilijan, Moldovakan St., Cottage 70/78, postal code 3901.

support@maxproject.pro · +374 41 091 204

1. Scope and controller

The Controller above serves only ARM accounts. This policy covers the ARM website, own cabinet, orders, workspace, JURIST Plugin, support and service messages. Language, IP and project jurisdiction do not change the seller. Processing is lawful, purpose-limited, proportionate and no longer than necessary. User data are not sold or used by the Controller for advertising or training a public model. Publishing a policy enables no feature and creates no user consent.

2. Subjects and data

Subjects include visitors, adult customers, account owners, support contacts and people whose data the user lawfully includes in materials. Data include name/email and verification; account/workspace IDs, generations, market, seller, access state, password hashes, MFA/session and security events; order amount/currency/status and payment evidence; legal release/revisions/locales/content/rendered hashes and user actions; temporary uploads, extraction, queries, factual matrices, indexes, templates, results, changes and exports; necessary consultation contacts/events when enabled; IP, browser, cookies and minimized diagnostics. Open passwords, card security codes, provider keys and full materials are excluded from ordinary logs.

A separate domain-separated HMAC of verified normalized email prevents a repeat trial. It is pseudonymous, not anonymous; it stores no raw email, cannot message the person and is not used to infer links between different addresses. Account email remains a separate contact category. Deleting an account does not restore consumed trial eligibility. Identity uniqueness across markets is a separate routing/security purpose, not advertising.

3. Purposes and grounds

Contract and pre-contract actions provide orders, contact verification, account/access, chosen functions, exports and support. Law supports compulsory accounting, subject requests and competent-authority requests. Security, fraud prevention and evidence protect rights. Article 9(4)(2) of the Armenian personal-data law recognizes consent for data obtained under a contract and used for its stipulated actions; it is not unlimited permission. Separate specific consent is sought for dependent external/material processing when needed. Privacy acknowledgement is distinct from contractual acceptance and optional consent; all optional controls begin unchecked. Withdrawal stops new dependent processing but not lawful independent obligations.

4. Operations and materials

Necessary collection, recording, organization, storage, correction, retrieval, use, transfer/access, blocking, deletion and destruction may be automated or mixed. Users determine material content and operations, ensure rights and legal grounds for third-party data and minimize disclosure. The Controller performs instructed technical processing and remains responsible for its own confidentiality and security obligations. Special-category, biometric, minors' data and unauthorized protected secrets are prohibited until a separate lawful protected mode. Your consent does not replace another subject's legal ground.

5. Plugin and help

OAuth records connection/client/permission, authorization, revocation and minimal technical events. Passwords/MFA are not Plugin arguments. Only the authorized command's necessary arguments/results are exchanged; neither all chats nor all attachments are copied automatically. A ChatGPT file requires separately supported transfer and confirmation. Revocation stops new use of that grant, but does not erase OpenAI data or JURIST account/material/payment/acceptance history. Fresh authorization is required to reconnect; restored backups cannot silently revive revoked grants.

When product help is enabled, only the product question and bounded context/metadata go to separately selected OpenRouter/model providers after concrete disclosures and applicable separate consent. Help reads own English FAQ/anonymized examples and no user projects/files. It performs no paid user operation; the service funds provider costs even at zero user balance. Do not send case materials, third-party data or secrets. Persistent dialogue history is not introduced; ordinary metrics/logs do not store complete messages by default. Email support remains available if external AI is declined. Provider retention/no-training/ZDR depends on verified route terms, not this policy.

6. Recipients and countries

REG.RU provides main account/workspace infrastructure and separate service mail in Russia. MegaHost Kazakhstan hosts encrypted offsite backup and sealed operational-key functions under a separate choice/ground. Own Paynet (Digital Brains LLC and the chosen payment provider) handles order/payment/contact fields only when own ARM payment is enabled; card data stay there. OpenRouter and the selected model see necessary prompts and may process in the USA/other provider countries; OpenAI independently processes user ChatGPT chats and authorized command results. Parser API receives minimal public-source queries only for enabled RU-jurisdiction operations, independently of seller market. Planerka receives necessary consultation contacts/time/status only when a separate offer/consent is available. DNS/TLS/network providers handle connection metadata. Roles, selected route/country and necessary fields must be disclosed before dependent processing; unknown or unlawful routes remain closed.

Infrastructure location does not change the Armenian Controller. Armenian law Articles 26–27 require lawful third-party/cross-border conditions, adequate protection or the competent authority's permission where required; consent alone does not waive these requirements. Applicable Russian localization/notification rules are honored when they apply to collection of Russian-citizen data. No declaration here claims an unverified regulatory filing or permission. External provider policies are linked in the external-services notice.

7. Retention and ending processing

  • original upload: delete immediately after terminal processing and verify absence; stuck staging: 86,400 seconds from staged_at
  • extraction, matrix, index, project, personal template: workspace lifecycle; confirmed deletion immediately blocks access, physical deletion within one calendar month
  • history/undo: 14 calendar days from the change
  • export link / artifact: 7 / 14 days from readiness
  • verified operational/recovery/offsite backup: 14 days from verification
  • unpaid/failed/contact-expired order: 30 days from its terminal event
  • paid operational order / provider/accounting evidence: at least 12 calendar months from the applicable event; mandatory legal/accounting schedules may be longer, including at least five years where applicable law requires this
  • trial HMAC marker: while the once-ever rule applies, then the applicable dispute/legal-hold period; the marker contains no raw email
  • account/contact/session/acceptance/security: the applicable existing category policy and law; no new general period is introduced

Evidence periods do not extend user-material retention. Restoration must enforce current deletion and access restrictions; a backup must not reactivate a deleted workspace or revoked access. Revoking a connection does not restart retention. External providers have their own disclosed schedules.

Withdrawal/closure/deletion requests go to support@maxproject.pro. Processing with no continuing ground ends according to law; mandatory records and legitimate specific holds are distinct from materials. External suppliers retain already transferred data under their own law/terms; connection revocation alone does not delete them.

8. Cookies and security

Necessary session, limited pre-auth/form/OAuth and language cookies support login/security/locale. Optional advertising/analytics are not enabled on ARM legal pages or this ARM release's help/cabinet; future analytics requires a separate specific opt-in. Third-party payment/ChatGPT pages have independent cookies. TLS, access control, password/token protection, workspace isolation, disk encryption, encrypted signed backups and minimized logs are used; encryption is not end-to-end and authorized runtime/admin/provider processing can access plaintext. Backup private decrypt keys are outside RU/KZ; key loss may make recovery impossible. Absolute availability or strict RPO/RTO is not promised. Statutory incident duties apply.

9. Rights, revisions and language

Subjects may request information/access, correction, blocking/destruction, withdrawal and lawful objections, and complain to https://dataprotection.moj.gov.am/ or a competent court. Send requests to support@maxproject.pro; identity checks are proportionate. Statutory information/access on a proper written request is free within five days; other actions follow applicable statutory periods. A refusal states lawful reasons. Withdrawal does not retrospectively invalidate lawful processing or independent statutory/contractual grounds. A changed mandatory text has a new immutable revision and may require explicit reacceptance; optional purposes still need their own grounds. Armenian governs the same release's translations.

External services notice — JURIST ARM2026-10-08.1

External services notice — JURIST ARM

Edition dated 8 October 2026. Version 1.1.0. ARM service market. Armenian is the governing text; English and Russian translate the same release. The RU market has a different seller and separate documents at https://legal.maxproject.pro/jurist.

Individual Entrepreneur Danielov Ernest Igori (ԱՁ ԴԱՆԻԵԼՈՎ ԷՌՆԵՍՏ ԻԳՈՐԻ), TIN 20124605, registration 286.1561607 dated 19 February 2026. Address: Armenia, Tavush, Dilijan, Moldovakan St., Cottage 70/78, postal code 3901.

support@maxproject.pro · +374 41 091 204

1. Recipients and purposes

Only necessary fields for an enabled lawful operation are sent. The ARM seller above is distinct from the RU seller. Hosting does not change the Controller and publication does not activate suppliers.

| Recipient | Data and purpose | Country and condition | |---|---|---| | REG.RU cloud and separate mail | account/workspace, operations, logs; email/service message | Russia; main infrastructure and contractual mail | | MegaHost Kazakhstan | encrypted backup objects and sealed operational key | Kazakhstan; separate informed recovery choice; private backup decrypt key outside RU/KZ, verified backups 14 days | | own Paynet / Digital Brains LLC and chosen payment provider | order, amount/currency/status and required contact | Armenia/provider infrastructure; only after own payment activation; card credentials stay at provider | | OpenAI / user ChatGPT | authorized command arguments/results and connection events; user's own chats | provider-region countries; independent user terms, no automatic transfer of all chats/files | | OpenRouter and selected model | minimized selected text/metadata, output | USA/other selected provider countries; concrete route/country disclosed before operation and applicable separate consent | | Parser API | necessary public-source query | specific endpoint/data disclosed, enabled RU-project search only, no raw-response chat transfer | | Planerka | necessary consultation contact/time/status | provider statement: Selectel Russia; only separately enabled offer/consent, minimized JURIST events | | DNS/TLS/network suppliers | IP, host and connection metadata | necessary access/security infrastructure |

2. Product help and limits

When the cabinet help bot is enabled, the question and bounded context go to a separately selected AI model; the service pays, no user balance reservation/debit. Help reads own English FAQ/anonymized examples, not projects/files, and runs no paid commands. Do not supply case materials or secrets. It creates no persistent chat history; ordinary logs contain no complete messages by default. The concrete provider/country/fields and current retention are shown before the call. External AI may see plaintext; disk/TLS encryption does not hide it after termination. ZDR/no-training is not guaranteed without verified route terms.

3. Lawful transfer, withdrawal and provider policies

Consent does not replace Armenian Articles 26–27 third-party/adequacy/permission duties or applicable Russian localization/cross-border notification rules. Unknown/unlawful routes stay closed. Withdrawal stops new dependent calls; it does not erase data already at the provider or mandatory evidence. JURIST materials and evidence follow the privacy policy, not another product's schedules.

Primary provider statements: [Paynet](https://paynet.am/en/privacy), [OpenRouter](https://openrouter.ai/privacy/), [OpenAI](https://openai.com/policies/privacy-policy/), [REG.RU](https://help.reg.ru/support/pravovyye-voprosy/personalnyye-dannyye/mery-zashchity-personalnykh-dannykh-v-reg-ru), [MegaHost](https://megahost.kz/company/statement/), [Parser API](https://parser-api.com/), [Planerka](https://planerka.app/privacy-policy). Their websites describe their statements, not proof of an activated JURIST route. New material recipients/purposes/countries require review and a new immutable release/consent when applicable.