Skip to content

Polish Legal Review Packet

Prepared: 2026-06-14

This packet is for Polish counsel review before the paid pilot. It is not legal advice. It describes the current MamNajem product posture, the user-facing materials to review, and the legal questions that need written counsel answers before public launch.

Review Goal

Counsel should confirm whether the current product language and workflows are legally honest for a Poland-first landlord SaaS pilot:

  • owner setup, lease setup, documents, rent schedules, handovers, payment proof, messages, reminders, and final settlement evidence;
  • no claim that MamNajem replaces legal advice;
  • no claim that an in-app tap equals written form;
  • no claim that occasional or institutional lease workflows are fully automated;
  • no claim that Stripe Connect rent checkout is the default or approved Polish rent-collection model.

The current launch posture is an operational product for self-managing Polish landlords. Legal workflow hardening is still in the roadmap after this review.

Source Materials

Counsel should receive these files or exported PDFs:

Current Product Posture

MamNajem currently supports:

  • owner and tenant accounts;
  • property setup;
  • bank account setup for rent transfer details;
  • lease setup with tenant details, term settings, payment schedule settings, and lease document upload;
  • tenant invitation;
  • lease documents and asset upload;
  • payment schedules, payment requests, receipt/proof upload, manual mark-paid, deferral request, approval, and rejection;
  • Stripe Connect rent checkout and webhook handling;
  • handover protocols with items, photos/assets, confirmation, and decline;
  • final settlement initiation, confirmation, decline, and status display;
  • messaging, notifications, calendar events, audit log, data export, and account deletion surfaces.

The pilot posture should remain conservative:

  • bank transfer and proof workflows are the default rent-management story;
  • Stripe Connect rent checkout exists but is not required for owner-only activation and should not be marketed as the default Polish rent collection model without counsel approval;
  • native Apple/Google billing is subscription infrastructure, not part of lease or rent legal workflow;
  • in-app handover and settlement confirmations are evidence records unless a later counsel-approved workflow says they are formal written-form documents;
  • current ordinary/occasional/institutional lease-type support is not complete enough to market special lease automation.

Terms And Privacy Items To Review

Counsel should review the current terms and privacy policy for:

  • company identity, contact details, governing law, complaint handling, and ADR;
  • subscription withdrawal, cancellation, grace period, Archive/read-only posture, and gross VAT-inclusive pricing;
  • liability limits and whether consumer/prosumer carve-outs are sufficient;
  • account suspension process and appeal wording;
  • privacy roles and legal bases for lease, property, payment, bank account, message, asset, telemetry, notification, and audit-log data;
  • retention periods, especially lease/property data, messages, payment records, audit logs, notifications, and analytics;
  • statement that automated retention enforcement is still being implemented;
  • active lease deletion restrictions;
  • Stripe, Apple, Google, AWS, Cognito, Expo, Firebase, New Relic, and diagnostic provider disclosures;
  • IBAN handling, masking, encryption, data export, deletion, and legacy data posture.

Current Landlord Onboarding Copy

Current onboarding presents:

  • "Set up your rental workspace";
  • no-card trial before payout details;
  • bank account as required for real transfer details;
  • first property as required so leases, tenants, and payments have a place in the app;
  • Stripe Connect as optional and returnable later if the owner does not want in-app card payments yet.

Counsel should verify that this copy does not imply:

  • legal advice;
  • legal compliance of lease documents;
  • legally binding signing;
  • automatic lawful notices;
  • automatic eviction, enforcement, or debt collection.

Current Lease Setup Flow Description

The current mobile lease setup flow collects:

  • tenant first name, surname, email, phone, identity-document fields, primary tenant flag, and optional registration address;
  • lease term type, start date, end date, lease status, deposit refund days, and contract-rule toggles such as rent changes, inspection, subletting, pets, and subletting notes;
  • rent bank account, currency, rent amount, payment frequency, due day, reminder days, optional tax estimate, optional owner/tenant payment windows, and optional deposit, utilities, and service charge settings;
  • lease documents through the asset upload flow;
  • optional send-invitation toggle and invitation link flow.

Counsel should treat this as operational setup, not approved legal drafting. The flow currently does not fully model:

  • ordinary vs occasional vs institutional lease type;
  • execution method such as wet ink, external e-sign, QES, notary/hybrid, or unknown;
  • formal delivery proof for legal notices;
  • special occasional lease annexes and tax-office notice proof;
  • statutory rent increase, termination, arrears warning, or vacate-demand logic.

Handover Confirmation Wording

Current handover behavior and copy includes:

  • protocol list, create, edit, delete, item create/edit/delete;
  • confirm and decline actions;
  • "Your confirmation will be saved on this protocol. The protocol is complete when both sides confirm it.";
  • "Review the protocol and confirm it if everything looks right.";
  • "You confirmed this protocol.";
  • "Both sides have confirmed this protocol.";
  • "Tenant declined this protocol. Create a replacement to continue.";

Counsel should decide whether this language is acceptable as evidentiary handover confirmation. It should not be interpreted as a qualified signature, written form, notarial confirmation, or court-proof settlement by itself.

Final Settlement Wording

Current final settlement behavior and copy includes:

  • owner starts settlement;
  • tenant reviews and confirms or declines;
  • both sides can show confirmation state;
  • "After confirmation, the settlement will be marked as accepted when both sides confirm it.";
  • "After rejection, the landlord will see your note and must revise and resend the settlement.";
  • "Both sides confirmed the deposit refund. Details remain available in the lease overview.";

Counsel should decide whether "confirm settlement" and "accepted" are safe labels, or whether the product should use narrower language such as "acknowledge statement" until a separate formal settlement-agreement workflow exists.

Rent Reminder And Payment Proof Wording

Current rent/payment behavior includes:

  • payment schedules;
  • payment requests;
  • reminder-day settings in lease setup;
  • payment request statuses including pending, processing, paid, overdue, partially paid, canceled, and deferral states;
  • receipt/proof upload;
  • owner mark-paid;
  • tenant deferral request;
  • owner deferral approval and rejection;
  • calendar events for payment due dates.

Current privacy policy says calendar events such as lease expiry reminders and payment due dates are informational and do not constitute legally binding obligations or notices.

Counsel should confirm:

  • whether reminder copy should explicitly say it is not a statutory arrears warning or termination notice;
  • what minimum payment-proof fields and audit events are required for useful dispute evidence;
  • whether uploaded proof plus owner mark-paid is enough for the pilot payment story;
  • whether any late-rent or overdue copy risks implying legally valid arrears escalation.

Stripe Connect Rent Payment Posture

Current product and backend support Stripe Connect rent checkout. Current research recommends Poland-first rent management as off-ledger by default: landlord IBAN, payment request, reminder, tenant proof upload, owner confirmation, and audit log.

The pilot posture should be:

  • subscription billing can use Stripe, Apple, and Google as configured;
  • rent payment checkout through Stripe Connect is optional infrastructure;
  • owner-only activation does not require Stripe Connect;
  • no MamNajem take-rate should be promised or implied for MVP rent payments;
  • if Stripe Connect remains visible, counsel should review payment-services, marketplace-payout, refund, dispute, negative-balance, and support language.

Counsel should answer whether Stripe Connect rent checkout may remain visible in pilot, should be feature-flagged, or should be hidden until a dedicated payment-services review is complete.

Counsel Questions

Ordinary Residential Lease

  • Which ordinary lease variants can MamNajem safely support at pilot: indefinite, fixed-term up to one year, fixed-term longer than one year, or all three?
  • Should a fixed-term ordinary lease longer than one year be blocked unless the execution method is wet ink or QES?
  • What wording should the UI use if the owner has only an uploaded draft or in-app acknowledgement rather than written-form execution?
  • Which rent increase, arrears warning, and termination flows must be excluded until the product has statutory notice logic?

Occasional Lease

  • May MamNajem expose occasional lease in pilot at all, or should it be hidden until the special annex pack is modeled?
  • What exact eligibility declaration is needed for a private landlord who is a natural person and not conducting business in renting premises?
  • What exact artifact checklist is required: notarial deed, alternate premises, alternate-premises owner consent, notarized signature where demanded, and tax-office notice proof?
  • What wording should avoid promising "faster eviction" or guaranteed enforcement?

Institutional Lease

  • Should institutional lease be hidden until business-landlord support exists?
  • What owner/business-landlord eligibility data would be required?
  • Which notarial statement and written-form requirements must be represented in product before exposing this lease type?
  • What copy should distinguish institutional lease from occasional lease without overclaiming enforcement.

Deposit Handling

  • What deposit caps should be enforced by lease type?
  • Must ordinary lease deposit return include statutory indexation logic?
  • How should the one-month deposit-return deadline interact with pending utility reconciliation or disputed handover items?
  • Which final settlement labels are safe for in-app confirmation, and which require a formal settlement agreement?

QES, Notary, And Delivery Proof

  • Which current artifacts can rely on in-app confirmation as evidence?
  • Which current or planned artifacts require wet ink, QES, notarial deed, notarized signature, or officially certified signature?
  • Which notices require legal delivery proof, and which channels can satisfy it: in-app, email, registered mail, e-delivery, external signing package, in person, or other?
  • What metadata must be stored for delivery proof: document hash, dispatch channel, address snapshot, proof of posting, proof of delivery, returned mail, open/download event, timestamp, signer identity, and provider audit report?

GDPR, Retention, And IBAN Handling

  • Are the current privacy legal bases and retention periods acceptable for paid pilot, including the statement that automated retention enforcement is still being implemented?
  • Should lease, handover, settlement, payment proof, and message data be kept for different retention periods?
  • Should account deletion during active leases be restricted as currently described?
  • Should data export return the full IBAN (current behavior) or a masked IBAN?
  • Are current IBAN security statements sufficient now that bank account details are stored as plain values protected by encryption at rest (see IBAN storage policy decision)?

Requested Counsel Output

Please return written answers in this structure so Product Owner can record them in the Legal review response log:

  1. Required copy changes before pilot.
  2. Required product blocks or feature flags before pilot.
  3. Workflows acceptable for pilot with current implementation.
  4. Workflows acceptable only after later implementation.
  5. Any terms/privacy changes required before paid users.
  6. Any questions that need business-owner decision rather than legal answer.

Product Owner Send Checklist

Before sending this packet, attach or link:

  • current terms and privacy policy;
  • this packet;
  • the three research docs listed above;
  • current English and Polish onboarding/property/account translation files;
  • mobile flow docs for payments, documents, handovers, and audit;
  • screenshots only if counsel asks for visual proof of a specific screen.