Polish Legal Review Checklist for MamNajem¶
Scope and source baseline¶
This checklist is designed to be handed to a Polish lawyer as a product-review brief, not used as final legal advice. It assumes the current MamNajem product is already strong on lease records, payment requests, handovers, final settlement, messaging, document storage, audit history, and Stripe-based payment rails, but that native legally binding signing, automated retention cleanup, and partner-integrated screening are still either missing or only part of the roadmap. The attached Poland-specific reports also point in the same direction: keep the MVP focused on landlord-tenant operations, treat screening as a handoff rather than a deep in-house build, and be cautious about embedded marketplace-style rent collection in Poland. fileciteturn0file8 fileciteturn0file9 fileciteturn0file10
I relied primarily on official Polish legal texts available through ELI/ISAP for the Civil Code and the Tenants’ Rights Act, plus official Stripe documentation for platform-funds-flow risk. The tenant-rights source retrieved here is the official 2023 consolidated text published through ELI, so counsel should still confirm that no later amending act changes the final implementation before launch. citeturn39view0turn40view0turn36view0turn31view2
The product-level takeaway is that MamNajem should not treat “ordinary,” “occasional,” and “institutional” lease flows as cosmetic variants of the same contract. Under Polish law, they differ on eligibility, maximum term, signing form, notarial requirements, rent-increase rules, vacate procedure, and deposit logic. Those differences are load-bearing for data model, templates, UX, delivery evidence, and public copy. citeturn20view4turn35view0turn18view1turn19view0
Lease-type workflows¶
Ordinary residential lease workflows
What MamNajem plans to do. Use the core lease lifecycle for standard residential tenancies: lease CRUD, fixed-term and open-ended variants, renewals, lease documents, tenant assignment, payment schedules, handovers, and final settlement.
What the lawyer should verify. Confirm that the product splits ordinary leases into legally distinct modes: open-ended, fixed-term up to one year, and fixed-term longer than one year. Under Civil Code article 660, a lease of real estate or premises for more than one year should be in writing; if that form is not preserved, the lease is treated as concluded for an indefinite term rather than as a valid long fixed term. Counsel should also verify that renewals and amendments preserve the required form under article 77, and that default notice logic for ordinary residential leases is not driven only by generic Civil Code rules where the Tenants’ Rights Act is more specific. citeturn20view4turn21view0turn17view3turn33view0
What product risk exists if the assumption is wrong. The UI could present a lease as safely fixed-term when the law treats it as indefinite, which would break expiry logic, renewal logic, termination templates, and marketing claims about “fully compliant lease handling.” That kind of error would not stay isolated; it would infect notices, rent-increase timing, arrears escalation, and move-out assumptions downstream. citeturn20view4turn21view0turn17view3
Occasional lease workflows
What MamNajem plans to do. Support an occasional-lease lane as a specialized version of the normal lease workflow, with extra documents, deposit handling, and a post-termination vacate path, while still relying on the same document storage and operational timeline.
What the lawyer should verify. Confirm that the product only offers this lane where the statutory prerequisites are actually met. Under article 19a, occasional lease is for a residential unit owned by a natural person who is not carrying on business in renting premises, and it must be fixed-term for no more than ten years. The occasional-lease pack must include the tenant’s submission to enforcement in a notarial deed, the tenant’s indication of an alternative premises, and the consent of that other premises’ owner or title-holder; on landlord demand, that consent can require notarized signature certification. The landlord also has to notify the tax office within 14 days from the start of the tenancy, and if that notice is missed, the special occasional-lease rules on rent and simplified vacate procedure do not apply. After the lease ends, the owner’s demand to vacate must be in writing with an officially certified signature. citeturn34view4turn35view0turn18view1
What product risk exists if the assumption is wrong. If the app treats occasional lease as “ordinary lease plus one checkbox,” landlords may lose the main benefit they expected: the occasional-lease enforcement path. That creates a particularly dangerous mismatch between product copy and reality, because the lease may still exist, but the accelerated evidentiary and enforcement workflow may not. citeturn35view0turn18view1
Institutional lease assumptions
What MamNajem plans to do. Eventually support a lane for professional landlords or PRS-style operators using the same general lifecycle as ordinary leases, but with a different contract basis, notarial annex, and special vacate flow.
What the lawyer should verify. Confirm the eligibility boundary first. Under article 19f, institutional lease is a residential lease concluded by a natural person, legal person, or organizational unit conducting business in renting premises. The agreement must be for a fixed term, and article 19g requires the agreement and any amendments to be in writing under pain of nullity. A tenant notarial statement submitting to enforcement is mandatory. Unlike the ordinary-residential regime, rent increases in institutional lease are governed by the contract, and the special vacate demand requires writing with an officially certified owner signature and a minimum fourteen-day vacate period. Counsel should also check whether the current product role model is precise enough to distinguish a true entrepreneur-landlord from a private landlord merely using “professional-looking” tooling. citeturn18view2turn19view0
What product risk exists if the assumption is wrong. MamNajem could end up offering “institutional lease” to customers who do not legally qualify, or generating the wrong formality and deadline for the vacate phase. That creates a high-risk combination of unenforceable documents and misleading sales language. citeturn18view2turn19view0
Deposits and move-in and move-out¶
Deposit limits and return deadlines
What MamNajem plans to do. Keep a deposit ledger tied to the lease, use that ledger inside final settlement, and let owners offset at least some end-of-lease claims against the deposit before refund.
What the lawyer should verify. Confirm that the product uses different deposit rules for each lease type. For ordinary residential leases, article 6 allows a deposit up to twelve times monthly rent, requires return within one month of vacating, and also provides a statutory indexation mechanism for return amount under article 6(3). For occasional lease, article 19a caps the deposit at six times monthly rent and requires return within one month after vacating, after deductions. For institutional lease, article 19f also caps the deposit at six times monthly rent, requires one-month return, and expressly allows the landlord to satisfy unpaid rent claims from the deposit and require top-up. Counsel should also confirm whether the app may lawfully hold back part of the deposit for still-unbilled utilities, or whether any such holdback must be expressly contract-based and narrowly documented. citeturn16view0turn35view0turn19view0
What product risk exists if the assumption is wrong. Deposit logic would become systematically wrong rather than occasionally wrong. The biggest hidden trap is ordinary-lease indexation: if the app stores only a nominal deposit amount and returns that nominal amount by default, it may understate what is due. The second trap is cross-applying institutional top-up logic to lease types that do not expressly authorize it. citeturn16view0turn19view0
Handover protocols
What MamNajem plans to do. Run move-in and move-out handover protocols with item condition, photos, confirmations, decline flows, and replacement protocols.
What the lawyer should verify. Confirm the minimum legal content needed for the initial handover protocol and the evidentiary sufficiency of the move-out protocol. Article 6c says that before the premises are handed over to the tenant, the parties prepare a protocol describing the technical condition and degree of wear of the installations and devices found in the premises, and that this protocol is the basis for settlement when the premises are returned. Counsel should verify whether the planned protocol schema, meter readings, photos, timestamps, and refusal/absence flows are strong enough to support damage and wear allocation later, especially if one party refuses to sign the move-out version. citeturn16view1
What product risk exists if the assumption is wrong. Deposit deductions and damage claims become evidence-poor. In practice, the app could do an excellent job of organizing a move-out process while still failing at the only question a dispute turns on: what exactly was the starting condition, and who can prove it. citeturn16view1turn20view5
Final settlement
What MamNajem plans to do. Produce a final settlement statement that is aware of the deposit, payment requests, receipts, and handover evidence, and allow confirm or decline flows.
What the lawyer should verify. Confirm that the settlement flow is anchored to the statutory protocol and repair rules rather than treated as a free-form accounting screen. Article 6e requires the tenant, after the end of lease and after vacating, to refresh the premises and perform tenant-borne repairs, and it sets the basis for certain value settlements. Article 6 and the special-lease provisions also impose a one-month deposit-return clock, while Civil Code article 677 gives the landlord one year from return of the premises for claims for deterioration or damage. Counsel should decide whether the product should separate immediate move-out settlement from later utility reconciliation, and how that interacts with the statutory refund timer. citeturn16view1turn16view0turn20view5
What product risk exists if the assumption is wrong. The app could encourage owners either to return deposits too late, to deduct items they cannot legally support, or to miss the one-year deadline for post-return damage claims because the UI never starts the clock. citeturn16view0turn20view5
Notices and defaults¶
Rent increase notices
What MamNajem plans to do. Generate rent-increase workflows and owner-facing notice templates from lease data and billing settings.
What the lawyer should verify. Confirm that the app uses the correct legal regime per lease type. For ordinary residential leases, article 8a says the owner raises rent or other charges by terminating the current amount, ordinarily with three months’ notice, and the notice must be in writing under pain of nullity. If the statutory threshold questions are engaged, the tenant can demand a written explanation and calculation, which the owner must provide within fourteen days or the increase becomes invalid. By contrast, occasional and institutional lease statutes say the owner may increase rent only in line with the contract. Counsel should also verify that the app does not accidentally use the generic Civil Code rent-increase rule for premises instead of the residential-protection rule. citeturn16view2turn17view0turn17view1turn33view1
What product risk exists if the assumption is wrong. The product could manufacture invalid increases at scale. That would then contaminate arrears calculations, automated reminders, and debt flags, because the “unpaid” sum may never have become legally due in the first place. citeturn16view2turn17view0turn17view1
Termination notices
What MamNajem plans to do. Support lease-end, early-termination, and vacate workflows, including generated reason codes, deadlines, and stored notice documents.
What the lawyer should verify. Confirm which termination events the app will generate and which party can use them. For ordinary residential tenancies, article 11 of the Tenants’ Rights Act says landlord termination may occur only for specified statutory reasons, the notice must be in writing under pain of nullity, and it must state the reason. For fixed-term leases more broadly, Civil Code article 673 § 3 says both parties may terminate only in the cases specified in the contract. For occasional and institutional leases, lease expiry or termination is only the first step: if the tenant does not leave voluntarily, the owner must follow the special vacate-demand procedure before seeking an enforcement clause on the notarial submission. citeturn17view3turn33view0turn18view1turn19view0
What product risk exists if the assumption is wrong. MamNajem could present a tenancy as “terminated” inside the app while the legal position is much messier. That creates reliance risk for owners and reputational risk for the product, especially if later copy suggests automatic or simplified eviction. citeturn17view3turn18view1turn19view0
Arrears warnings
What MamNajem plans to do. Detect overdue rent, send reminders and escalation warnings, and prepare the owner for later termination or collection steps.
What the lawyer should verify. Confirm that the arrears engine uses the correct residential threshold. For ordinary residential leases, article 11(2)(2) requires at least three full payment periods of arrears plus prior written warning of intended termination and an additional one-month period to pay both outstanding and current amounts. Civil Code article 687 contains a different rule for local leases—two full payment periods plus written warning—so counsel should verify that the product never shows the wrong rule for protected residential tenancies. Counsel should also confirm that occasional and institutional workflows inherit the correct article 11 grounds, because those lease types preserve article 11(2)(1)–(3), not the whole residential regime. citeturn18view0turn33view1turn18view1turn19view0
What product risk exists if the assumption is wrong. An owner could rely on an invalid escalation sequence, serve termination too early, and then discover that the app’s debt timeline is useless for court or negotiation purposes. citeturn18view0turn33view1
Signatures delivery and evidence¶
E-signature, QES, wet ink, and notary requirements
What MamNajem plans to do. Add signing and document-completion logic on top of document storage and templates, while still supporting uploads of externally signed or notarized documents.
What the lawyer should verify. Counsel should review the product around the Polish hierarchy of form. Under the Civil Code, documentary form is achieved by a document that lets the person making the declaration be identified; written form requires a handwritten signature; electronic form requires a qualified electronic signature and is equivalent to written form. That means in-app confirmation, email acknowledgement, or non-qualified e-sign may support documentary form, but they should not be assumed to preserve written form where Polish law demands writing. This is crucial because a lease longer than one year should be written or it is treated as indefinite, while occasional and institutional lease packages additionally require notarial deed or officially certified / notarized elements. In practice, the lawyer should decide which documents MamNajem can safely route through in-app confirmation, which require QES or wet ink, and which must stay hybrid or offline. citeturn36view0turn20view4turn35view0turn19view0
What product risk exists if the assumption is wrong. The app may blur three legally different things—evidence of consent, documentary form, and written form—and then market them as one. That is exactly how products end up with valid-looking PDFs that do not preserve fixed-term status or do not support a statutory notice. citeturn36view0turn20view4turn21view0
Proof of delivery and evidence storage
What MamNajem plans to do. Use document storage, audit logs, message history, and notifications as the evidence layer for notices, acknowledgements, and vacate steps.
What the lawyer should verify. Confirm the service model for each document family. Civil Code article 61 says a declaration of intent made to another person is effective when it reaches that person in a way that lets them become acquainted with its content; for electronic declarations, that happens when the declaration is introduced into electronic communication in a way that lets the recipient access it. But occasional and institutional vacate workflows go further: their court pack expressly requires proof of delivery to the tenant or proof of dispatch by registered mail. Counsel should therefore define, document by document, whether in-app delivery, email, QES delivery, paper service, courier, or registered mail is sufficient, and what metadata the product must preserve. For evidence storage, counsel should also set retention rules around claim periods, especially the one-year period in article 677 and the general three/six-year periods in article 118. citeturn20view0turn20view1turn18view1turn19view0turn20view5turn21view4
What product risk exists if the assumption is wrong. MamNajem could do everything right except the one thing litigation exposes first: proving that the notice actually reached the tenant in the legally relevant way and that the evidence was retained long enough to use. citeturn20view0turn18view1turn19view0turn20view5
Privacy screening and payments¶
GDPR and data retention
What MamNajem plans to do. Store lease documents, handover media, payment receipts, chat history, audit logs, user accounts, property data, and optional telemetry/consent state, while also offering data export and deletion requests.
What the lawyer should verify. Confirm the lawful basis and retention schedule for each data class rather than treating “rental operations” as one undifferentiated purpose. Under GDPR, personal data processing needs a lawful basis, and the core principles include data minimisation and storage limitation. Counsel should map contract-performance data, legal-obligation data, litigation-defense data, optional telemetry data, and identity/screening data separately. The retention model should also reflect Polish claim periods: one year for landlord/tenant claims tied to deterioration, outlays, or overpaid rent after return of the premises, and three or six years for broader claims depending on their nature. The current product stance that retention cleanup is future work should not survive legal review unchanged. citeturn26search3turn20view5turn21view4 fileciteturn0file10
What product risk exists if the assumption is wrong. The app may keep sensitive tenancy records for too long, fail to answer access/deletion requests correctly, or delete evidence too soon for a deposit or damage dispute. Both over-retention and premature deletion create avoidable legal exposure. citeturn26search3turn20view5turn21view4
Tenant screening and consent
What MamNajem plans to do. Add a pre-lease application layer, basic applicant intake, screening status, and possibly partner-result storage rather than building a full internal bureau-check product from day one. The attached Poland research explicitly points toward a screening handoff model rather than storing raw financial or bureau-source payloads inside the MVP. fileciteturn0file8 fileciteturn0file10
What the lawyer should verify. Confirm which applicant fields can be collected before contract, what lawful basis applies to each field, when explicit consent is required, and whether any BIG/KRD or similar debt-information checks must be run only via an authorized partner with a specific tenant authorization flow. The lawyer should also decide whether MamNajem should retain only screening invite state, result category, and certificate, while avoiding raw bureau, bank, or source-data payloads in MVP. citeturn26search3 fileciteturn0file8 fileciteturn0file10
What product risk exists if the assumption is wrong. Screening can silently turn the app from a lease-ops tool into a processor of highly sensitive third-party financial data it does not actually need. That raises consent, profiling, retention, and disclosure problems all at once. citeturn26search3 fileciteturn0file8
Payment and rent collection legal risks
What MamNajem plans to do. Use landlord bank-account data, payment requests, uploaded proof of payment, manual mark-paid flows, and also keep Stripe-based checkout/connect capabilities already present in the stack.
What the lawyer should verify. Confirm whether the Polish MVP should remain off-ledger or whether the business really wants to step into embedded fund flows. The attached Poland payments research recommends off-ledger rent management first—IBAN, payment request, reminder, receipt proof, landlord confirmation, and audit log—precisely because that avoids a more complex payment-services and marketplace-payout analysis in MVP. If the product does move to embedded collection, counsel should assess payment-services perimeter, terms of service, seller/submerchant structure, refund handling, and negative-balance allocation. Stripe’s own documentation says that with separate charges and transfers, the platform’s balance is debited for Stripe fees, refunds, and chargebacks, and that refunds do not automatically reverse associated transfers to connected accounts. fileciteturn0file9 citeturn31view2turn31view3
What product risk exists if the assumption is wrong. MamNajem could take on a much heavier legal and operational role than intended: liability for negative balances, refund reconciliation, chargebacks, and possibly a regulated-funds-flow analysis that was never part of the initial SaaS thesis. Even if regulation is ultimately manageable, it is expensive to discover that too late. fileciteturn0file9 citeturn31view2turn31view3
Product copy and priority questions¶
Product copy claims we should avoid
What MamNajem plans to do. Market itself as a Polish rental-operations platform covering leases, handovers, settlement, reminders, and possibly later signing, screening, and payments.
What the lawyer should verify. Review every public claim that implies legal effect, not just product functionality. In particular, counsel should scrutinize any wording close to: “legally binding e-signature for all Polish lease documents,” “fully digital occasional lease,” “automatic eviction,” “official proof of delivery,” “escrowed rent,” “GDPR-compliant,” “tenant background checks,” or “deposit deductions calculated automatically according to Polish law.” Safer framing is narrower: “supports document workflows,” “helps prepare notices,” “tracks delivery evidence,” “supports partner-led screening,” “supports payment requests and payment proof,” and “supports hybrid occasional-lease packs.” Those safer formulations matter because Polish law sharply separates documentary evidence from writing, and separates ordinary leases from special occasional/institutional enforcement packs. citeturn36view0turn35view0turn18view1turn19view0 fileciteturn0file8 fileciteturn0file9
What product risk exists if the assumption is wrong. Overclaiming is not just a marketing problem. It can convert a manageable product gap into a misrepresentation problem, invite reliance by landlords on workflows that are only partly compliant, and make refund, support, and dispute handling much harder as soon as the first contested notice or deposit deduction appears. citeturn36view0turn18view1turn19view0 fileciteturn0file9
The questions below are the highest-value items to ask the lawyer to answer in writing before Polish launch:
- Should the product permit a digitally “fixed-term” ordinary lease longer than one year unless both parties use wet ink or QES, and if not, how should the UI downgrade it to an indefinite-term workflow? citeturn20view4turn36view0
- Must the ordinary-lease deposit engine calculate the statutory indexed return amount under article 6(3), and how should the one-month refund deadline interact with still-pending utility reconciliations? citeturn16view0
- What exact document pack, timelines, and fallback logic are needed for occasional lease, including tax-office notice, alternative-premises substitution, and the certified-signature vacate demand? citeturn35view0turn18view1
- Which notice templates must follow the Tenants’ Rights Act rather than generic Civil Code defaults, especially for rent increase, arrears escalation, and residential termination? citeturn16view2turn18view0turn17view3turn33view1
- Which channels count as legally sufficient delivery for which documents, and what minimum evidence bundle must the platform store for service, receipt, and later dispute use? citeturn20view0turn20view1turn18view1turn19view0turn20view5
- Should the Polish MVP stay strictly off-ledger unless counsel separately approves a payment-services and marketplace-payout design for embedded rent collection? fileciteturn0file9 citeturn31view2turn31view3