Account and content
Future terms must explain eligibility, account responsibility, user-owned career content, service permissions, prohibited use, and the distinction between imported claims and confirmed facts.
Terms · Drafting principles
Terms should describe the product people actually receive.
Binding customer terms are not published from this internal foundation. The future agreement must match the implemented product, pricing, privacy choices, ownership model, acceptable use, cancellation, export, deletion, and dispute process.
This route is a product-language preview, not legal advice, a customer agreement, or a statement that MeritLog is open for registration.
Service and limits
They must accurately describe plan limits, dependency failures, permitted public sources, AI proposal boundaries, no guaranteed outcomes, and the user's responsibility to review consequential materials.
Billing and exit
They must reconcile price, promotion duration, renewal, cancellation, downgrade behavior, refunds, export, deletion timing, processor handling, and backup expiration with the deployed flows.
Publication gate
Legal copy follows executable truth.
Complete the relevant product, billing, privacy, export, deletion, support, and vendor flows.
Reconcile the agreement with every customer-visible price, entitlement, claim, and recovery state.
Complete jurisdiction, processor, source-rights, tax, accessibility, and consumer-protection review.
Version the terms and privacy notices, preserve acceptance records, and explain material changes.
Publish only after the founder assigns the legal owner and the release evidence matches the text.
Protected product preview
Your career, remembered. Your next move, prepared.
Jurisdiction-specific legal text remains a required general-availability dependency.