E-signature Strategy for MamNajem in Poland¶
Legal baseline¶
Poland does not have a single “electronic is always enough” rule. The EU eIDAS Regulation expressly says it does not change national rules on how contracts are concluded or which legal form is required. eIDAS also says that an electronic signature cannot be rejected solely because it is electronic or not qualified, but only a qualified electronic signature has the same legal effect as a handwritten signature. An advanced electronic signature has stronger identity and integrity features, but it does not automatically become the equivalent of written form. citeturn18view0turn18view1turn19view0
Under the Polish Civil Code, a declaration of intent can be expressed by any conduct that sufficiently reveals intent, including electronically. For documentary form, it is enough to make the declaration in a document in a way that allows identification of the person making it; a “document” is simply an information carrier that lets someone read the content. By contrast, electronic form requires a qualified electronic signature, and the Code says that electronic form is equivalent to written form. That distinction is the core design rule for MamNajem: a strong in-app audit trail can support documentary form, but it does not replace written form where Polish law demands it. citeturn17view0turn34view0
For ordinary leases, the key lease-specific rule is Civil Code article 660: a real-estate or premises lease for a term longer than one year should be concluded in writing; if that form is not observed, the lease is treated as concluded for an indefinite term rather than void. The Civil Code also says amendments must preserve the form required for conclusion, while termination or rescission of agreements concluded in written, documentary, or electronic form generally requires at least documentary form, unless a statute or contract requires more. That means a simple or advanced e-signature can be enough for many lease-side documents, but not for a fixed-term lease over one year if you want to preserve that fixed term. citeturn5view3turn34view0
Residential-landlord notices are stricter. Under the Tenants’ Rights Act, a landlord’s termination notice must be made in writing under pain of nullity and must state the reason. Rent increases must also be made in writing under pain of nullity, and some pre-termination warnings must be given in writing as well, including prior written notice for arrears and written warnings for certain lease breaches. In digital practice, that pushes you to QES if you want an all-digital flow, because only QES is equivalent to written form. citeturn7view0turn7view1turn33view0turn34view0turn18view1
Occasional lease is the biggest exception and the strongest reason not to overgeneralize your e-signature flow. The statute requires the tenant’s submission to enforcement in the form of a notarial deed, requires the occasional-lease agreement and its amendments to be in writing under pain of nullity, and allows the landlord to require the alternate-premises owner’s consent with a notarized signature. After the lease ends, the landlord’s demand to vacate must be drawn up in writing with an officially certified signature. In other words, occasional lease is inherently a hybrid product: even if the main lease agreement is digitally signed with QES, the total pack still includes notarial or officially certified elements. citeturn8view0turn7view2turn7view3
One practical trap is Poland’s public-sector signing stack. The government signing service supports trusted profile, e-ID, and qualified certificates, but gov.pl clearly states that the trusted signature is equivalent to handwritten signature only in dealings with public authorities, not in private matters such as agreements or annexes with a private company or another person. MamNajem should therefore not build its private lease flow around “podpis zaufany” as a substitute for QES. citeturn27view1turn28search2
Provider comparison¶
The right comparison is not “which provider signs PDFs,” because all of them do that. The real question is which option best fits Poland’s three-lane reality: documentary-form operational records, written-form/QES documents, and hybrid occasional-lease packs. citeturn17view0turn34view0turn8view0turn7view3
| Provider or approach | What it gives MamNajem | Limits in the Polish rental context | MVP judgment |
|---|---|---|---|
| Simple in-app confirmation with PDF audit trail | Full UX control. If MamNajem renders an immutable document, identifies the signer, and preserves evidence, this can support documentary form and strong evidentiary value for many operational documents. citeturn17view0turn34view0turn18view1 | It does not satisfy written-form requirements by itself, so it is the wrong tool for fixed-term leases over one year, landlord statutory notices, or the special forms used in occasional lease. citeturn5view3turn7view0turn7view1turn8view0turn7view3 | Essential as your baseline evidence layer, but not sufficient as your only signature solution. |
| Autenti | Autenti’s standard e-signature is positioned for documentary form; its signature card includes signer data, IP numbers, roles, and identification methods. Its advanced signature adds online identity verification and SMS authorization. Its QES layer supports 20+ qualified-signature providers, can issue new QES certificates in-flow, and Autenti offers one-time qualified flows including selfie-based verification and mObywatel-based options. Autenti also offers callbacks and an API-based Sign Connector to embed the signing process. Signers do not need an account or software. citeturn21view0turn21view1turn25view1turn25view3turn14search0turn14search1 | QES still carries the normal friction of identity verification, and occasional lease still remains hybrid because the law requires notarial or officially certified elements outside any ordinary signing flow. citeturn25view1turn25view3turn8view0turn7view3 | Best primary provider for a Poland-first MVP because it spans documentary, advanced, and qualified tiers in one Polish-market workflow. |
| KIR mSzafir / Szafir / KIR | KIR is the strongest Poland-native QES option. mSzafir is a fully remote qualified signature available in one-off and long-term variants, with identity confirmation through mojeID or mObywatel; Szafir is a card-and-reader qualified signature with time-stamping and broad written-form legal coverage. KIR also positions integration of mSzafir, mojeID, and a durable medium with business processes, and its durable-medium product gives hash-based authenticity checks, document lifecycle visibility, and long-term access using blockchain/WORM-style architecture. citeturn21view3turn15search0turn21view4turn26search0turn26search1turn26search3 | KIR is excellent for QES and archiving, but it is not the best answer for every low-friction landlord-tenant interaction because many of those documents do not need QES and will suffer if every signer must pass a qualified-signature flow. citeturn21view3turn17view0turn34view0 | Best as a QES engine / fallback and as inspiration for your archival model; weaker than Autenti as the single front-door experience for all document types. |
| Docusign | Docusign supports SES, AES, and QES in Europe, explicitly documents Polish legality, offers embedded signing, Connect webhooks, and a Certificate of Completion that records identifying information and envelope events. Docusign also supports Polish identity documents for AES ID checks. citeturn2search7turn11search0turn20search9turn22search0turn22search1turn22search2turn11search16 | Its legal fit is fine, but its core advantage is international scale, not Poland-specific landlord workflows. It does not solve occasional-lease notarial edge cases better than local options, and its strongest differentiators matter more once you go multi-country or CLM-heavy. citeturn20search9turn8view0turn7view3turn22search0turn22search2 | Good later-stage vendor; not my first choice for a Poland-first rental MVP. |
| Adobe Acrobat Sign | Adobe works with every accredited provider on the EU Trusted List, automatically adds qualified timestamps to digital-signature documents in Europe, and can be configured with cloud-signature providers including Asseco SimplySign in Poland. Adobe also exposes APIs, embedded UI, webhooks, and downloadable audit reports that log participants and document events. citeturn21view7turn24view0turn24view1turn21view8turn24view2turn24view3turn21view9 | Adobe is very strong if your product becomes PDF-centric and enterprise-heavy, but for a Poland-first rental MVP it still externalizes much of the local identity/QES experience and does not remove the hybrid notarial reality of occasional lease. citeturn24view1turn21view7turn8view0turn7view3 | Strong enterprise alternative, but still behind Autenti for the first Polish launch. |
The bottom line is straightforward: if MamNajem needs one primary provider now, use Autenti; if it needs a direct national trust-service backbone for QES-heavy flows, use KIR mSzafir/Szafir as the qualified fallback; if it later becomes pan-European, re-open the Docusign vs Adobe question. citeturn21view0turn21view1turn25view1turn21view3turn22search0turn21view8
Document recommendations¶
The best way to operationalize this is to separate the legal floor from the recommended MVP default. The legal floor answers “what is likely sufficient under Polish form rules”; the product default answers “what should MamNajem actually do to keep disputes and support load low.” citeturn17view0turn34view0turn5view3turn7view0turn7view1turn8view0turn7view3
| Document or template | Legal floor in Poland | Recommended MVP channel | Why |
|---|---|---|---|
| Ordinary residential lease for up to 1 year | Documentary form is generally enough; an attributable electronic document can work. citeturn17view0turn34view0turn18view1 | External e-sign as default using Autenti SES/AES; allow strong in-app confirmation only as fallback. | The statute’s one-year writing rule is not triggered, but leases are core documents and worth stronger audit evidence than a bare in-app click. citeturn5view3turn21view0turn21view1 |
| Ordinary fixed-term lease for more than 1 year | Written form; digitally, that means QES. Without that form, the lease is treated as indefinite. citeturn5view3turn34view0turn18view1 | QES or wet ink only. Use Autenti QES or direct KIR mSzafir/Szafir. | This is the clearest hard rule in the ordinary-lease stack. citeturn5view3turn25view1turn21view3 |
| Renewal or annex that pushes the lease beyond 1 year, or amends a >1-year fixed-term lease | Same form as required for conclusion; practically QES or wet ink if digital. citeturn34view0turn5view3 | QES or wet ink. | Article 77 ties amendments to the form required for conclusion. citeturn34view0 |
| Mutual termination / surrender agreement for an ordinary lease | Usually documentary form is enough unless statute or contract requires more. citeturn34view0 | External e-sign by default; in-app only for low-risk cases. | This is not where Polish law is strictest, but it is a dispute-prone document and benefits from a better evidence bundle. citeturn34view0turn21view0turn22search1turn24view3 |
| Occasional lease agreement itself | Written form under pain of nullity; digitally, use QES if you want a fully electronic signature layer. citeturn7view2turn8view0turn34view0 | Treat as a hybrid pack: QES for the core agreement if feasible, but always with status tracking for the required offline attachments. | The main agreement can be digitized conservatively with QES, but the total pack is still not purely digital. citeturn7view2turn8view0 |
| Occasional lease tenant submission to enforcement | Notarial deed. citeturn8view0 | Notarial / offline process. | This is a statutory special form, outside an ordinary e-sign ceremony. citeturn8view0 |
| Occasional lease alternate-premises owner consent | Attachment; if demanded by the landlord, use a notarized signature. citeturn7view2turn8view0 | Operationally, standardize on offline notarized upload for this template family. | The statute makes notarization conditional on landlord demand; for a landlord-facing workflow, defaulting to the stronger version is safer. citeturn7view2turn8view0 |
| Occasional lease post-termination demand to vacate | Writing with an officially certified signature. citeturn7view3 | Offline / certified-signature process, with proof of delivery captured. | Ordinary e-sign platforms do not replace this special form. citeturn7view3 |
| Handover protocol, move-in / move-out inventory, condition report, meter readings, photo acknowledgements | Documentary/evidentiary record; no written-form requirement appears in the cited lease rules. The Tenants’ Rights Act itself uses a “protocol” as an operational record in article 10. citeturn17view0turn34view0turn35view0 | Simple in-app confirmation with immutable PDF, item-level photos, and robust evidence. | This is where MamNajem should fully lean into its mobile-first product. citeturn35view0turn21view0 |
| Final settlement, deposit calculation, deduction statement | Mostly evidentiary/documentary; the cited statutes regulate the deposit and return timing, but do not impose written form for the settlement statement itself. citeturn6view4turn7view2turn17view0turn34view0 | In-app confirmation by default; use external e-sign if the document includes a broader release/waiver or a contested debt acknowledgment. | Settlement is less about formal validity and more about proving exactly what was agreed and when. citeturn6view4turn7view2turn21view0turn22search1turn24view3 |
| Routine operational notices such as rent reminders, inspection scheduling, document receipt acknowledgements, maintenance-access confirmations | No written-form requirement appears in the cited lease/tenant rules for these operational communications. citeturn17view0turn34view0turn35view0 | In-app message center + email/push mirror. | These are communication flows, not written-form legal notices. |
| Landlord legal notices such as rent increase, termination, written warning before terminating for arrears or breach | Written form; digitally, use QES if you do not want paper. citeturn7view0turn7view1turn33view0turn34view0turn18view1 | QES plus delivery evidence, or wet ink/paper fallback. | Signature level is only half the problem; you also need to prove the notice reached the tenant. citeturn17view0turn7view3 |
That yields a clean answer to the first three user questions. Simple in-app confirmation is appropriate for handovers, inventories, meter/photo acknowledgements, final-settlement and deposit records, and routine operational notices; it can also support an ordinary lease up to one year, though I would not make that the default UX. External e-signature should be the default for short ordinary leases, mutual termination, and higher-stakes but non-written-form documents. QES or offline is mandatory or strongly preferred for >1-year fixed-term leases, their relevant annexes, statutory landlord notices, and the special occasional-lease artifacts that require notarial or officially certified forms. citeturn5view3turn34view0turn7view0turn7view1turn8view0turn7view3
MVP flow and integration roadmap¶
MamNajem should keep template ownership inside its own product, not inside the signature vendor. The product should own a controlled library of Polish rental templates: an ordinary short-term lease, an ordinary long-term lease, a lease-annex/renewal template, a mutual-termination template, a handover protocol, a final-settlement template, and a separate occasional-lease pack that includes checklisting for offline attachments. All of those should render to an immutable PDF snapshot before a signer confirms anything. That design is the safest fit for Polish documentary form, for provider portability, and for later evidence review. citeturn17view0turn34view0turn14search1turn21view8
The execution layer should be a simple policy engine. If the template is a handover or settlement record, route it to lane A: in-app documentary confirmation. If it is an ordinary lease up to one year or a mutual termination, route it to lane B: external SES/AES. If it is a >1-year lease or a statutory landlord notice, route it to lane C: QES. If it is an occasional-lease artifact with notarial or officially certified requirements, route it to lane D: hybrid offline task flow. That separation reduces both legal risk and UX friction because most landlord-tenant interactions do not need the heaviest possible signature level. citeturn5view3turn7view0turn7view1turn8view0turn7view3turn21view1turn21view3
For the first launch, my integration roadmap would be: first, build the internal PDF/evidence layer and integrate Autenti for standard and advanced flows; second, add a QES escalation path via Autenti QES for most qualifying documents and optionally a direct KIR mSzafir/Szafir fallback for Polish-local QES flows; third, add the occasional-lease hybrid pack with upload and checklist states for notarial deed, notarized consent, and later officially certified vacate demand; and only later evaluate Docusign or Adobe when MamNajem needs broader international agreement infrastructure. That sequence fits both the law and the likely MVP reality of a mobile-first rental app. citeturn21view0turn21view1turn25view1turn25view3turn21view3turn14search0turn14search1turn22search0turn22search2turn21view8turn24view2
For landlord legal notices, MamNajem must model delivery evidence as a first-class concern. Under the Civil Code, an electronic declaration to another person is made when it reaches that person in a way that lets them read it, and the occasional-lease enforcement pack expressly requires proof of delivery or dispatch of the vacate demand. So the product should never store only “signed/not signed” for notices; it needs sender, channel, dispatch timestamp, destination, open/download data where available, and paper tracking where used. citeturn17view0turn7view3
Data model and audit trail¶
Because Polish documentary form is ultimately about an identifiable person, an accessible document, and preserved evidence of intent, the minimum defensible model in MamNajem is broader than a typical “signature_status” column. Provider artifacts point in the same direction: Autenti exposes signer data, IPs, roles, and identification methods on its signature card; Docusign produces a Certificate of Completion with envelope-event history; Adobe stores agreement participants and milestone events in its audit reports; KIR’s durable medium uses hashes and lifecycle verification for authenticity and long-term access. citeturn34view0turn21view0turn22search1turn24view3turn26search0turn26search1
| Model element | What MamNajem should store |
|---|---|
| Template version | Template family, jurisdiction, lease mode, language, clause set, and exact version used to render the document. |
| Rendered document | Final PDF or equivalent immutable snapshot, SHA-256 hash, storage key, page count, and the exact bytes sent to the signer. |
| Signer identity | Full legal name, role in transaction, email, phone, user ID, and the identity-verification method used: account auth only, OTP, ID check, selfie, e-banking, QES provider, notary upload, or certified-signature offline. |
| Signature session | Provider name, signature level claimed by the flow, provider transaction ID, redirect/embed URL references, and final document artifact IDs. |
| Evidence events | Created, rendered, sent, viewed, OTP passed, signed, declined, canceled, downloaded, provider callback received, and internal status transitions—with timestamps, timezone, IP, and user agent where legally appropriate. |
| Attachments and media | For handovers and settlements: item-level photos, meter-reading photos, receipts, and hashes for each uploaded file so later disputes can tie media to the protocol version the user confirmed. |
| Notice delivery record | Dispatch channel, address/email/phone used, delivery proof, returned/bounced information, and proof of receipt or access where available. |
| Archival evidence bundle | Signed PDF, provider audit report / certificate of completion / signature card, certificate chain if QES is used, timestamp evidence, and a normalized internal JSON log for your own review tools. |
For higher-risk documents, I would also preserve qualified timestamp evidence wherever the provider gives it, or add it yourself through the qualified-signature toolchain. The Civil Code says an electronic document gains a “date certain” when it is marked with a qualified electronic timestamp, and both Adobe’s European digital-signature flows and KIR’s qualified-signature products emphasize time-stamping. That is useful for notices, lease start dates, and later courtroom chronology questions. citeturn34view0turn21view7turn26search4
On storage, MamNajem should mimic the functional properties of a durable medium even if it does not buy one immediately. KIR’s durable-medium design is built around authenticity, lifecycle traceability, hash verification, and WORM-like immutability. In AWS terms, the practical MVP translation is versioned object storage, retention locks for signed artifacts, immutable hashes stored in the relational model, and a clearly separated “evidence bundle” that is never silently re-written. citeturn26search0turn26search1turn26search3
Risk matrix¶
| Risk | Why it matters | Consequence | Mitigation |
|---|---|---|---|
| Using in-app or SES/AES for a fixed-term lease over one year | Civil Code article 660 requires writing for that fixed term. citeturn5view3 | The lease may be treated as indefinite, which changes termination economics and product assumptions. | Policy-engine rule: anything creating or extending a fixed term beyond one year must route to QES or wet ink. |
| Using non-QES for landlord statutory notices | Landlord termination and rent-increase notices must be in writing under pain of nullity; certain warnings must be in writing too. citeturn7view0turn7view1turn33view0turn34view0 | The notice can be invalid, which can break eviction or rent-adjustment workflows. | Force QES for digital notices; offer a paper fallback. |
| Treating occasional lease as a normal e-sign flow | The statute requires a notarial deed and later an officially certified signature for the vacate demand, with optional notarized owner consent. citeturn8view0turn7view2turn7view3 | The occasional-lease pack may be unenforceable when the landlord actually needs it. | Model occasional lease as a hybrid pack with offline task states and mandatory uploads. |
| Confusing trusted public signatures with private-contract signatures | Gov.pl states trusted signature is equivalent only in public matters, not private agreements or annexes. citeturn27view1turn28search2 | Wrong signature choice and false sense of compliance. | Do not offer “podpis zaufany” as MamNajem’s private-lease solution. |
| Weak proof of delivery for legal notices | A declaration must reach the recipient so they can read it; occasional lease enforcement expressly requires proof of delivery or dispatch. citeturn17view0turn7view3 | The signature may be valid, but the notice effectiveness can still be challenged. | Capture delivery metadata as a first-class evidence object; support paper tracking where needed. |
| Foreign-tenant friction on QES flows | Local QES onboarding often leans on Polish methods such as mojeID or mObywatel; Autenti’s foreigner materials also flag identity-workflow complexity and PESEL-related practicalities. citeturn21view3turn10search2 | Drop-off during signing for international tenants. | Keep QES only for documents that truly require it; keep ordinary documentary-form flows low-friction. |
| Mutable templates or post-sign document regeneration | Documentary form and provider audit evidence depend on the exact document content being preserved and attributable. citeturn34view0turn24view3turn22search1 | Evidence problems in disputes because the signed content cannot be reproduced byte-for-byte. | Render once, hash once, archive once; never “rebuild” the signed PDF from mutable database state. |
| No durable archive after tenancy ends | KIR’s durable-medium model exists precisely to preserve authenticity and access after the relationship ends. citeturn26search0turn26search1 | Support burden and weaker post-tenancy dispute position. | Keep a durable evidence bundle with retention and tenant/landlord access rules. |
Final recommendation¶
Which document types can use simple in-app confirmation? Use simple in-app confirmation for handover protocols, condition and inventory reports, meter readings, photo acknowledgements, final-settlement and deposit-deduction records, and routine operational notices. You can also support an ordinary lease of up to one year this way as a matter of legal floor, because documentary form can be enough if the signer is identifiable and the document is preserved, but I would treat that as a fallback rather than the default lease-signing UX. citeturn17view0turn34view0turn35view0turn6view4turn7view2
Which documents should use external e-signature? Use an external provider by default for ordinary leases up to one year, ordinary annexes that do not trigger the >1-year rule, mutual termination agreements, and higher-stakes settlement documents where you want better identity proof and cleaner audit artifacts than a native in-app flow. In practice, Autenti is the best fit for this layer because it covers documentary, advanced, and qualified variants while keeping the signer experience light. citeturn21view0turn21view1turn25view1turn34view0
Which documents require qualified signature or notarial/offline process? Require QES or paper/wet ink for fixed-term ordinary leases longer than one year, renewals or annexes that preserve or create those longer fixed terms, and landlord notices that statute requires to be in writing, such as rent increases, termination notices, and written pre-termination warnings. Require notarial or offline special-form handling for the occasional-lease tenant deed, any alternate-premises consent that you standardize as notarized, and the occasional-lease post-termination demand to vacate with an officially certified signature. citeturn5view3turn7view0turn7view1turn33view0turn8view0turn7view2turn7view3turn34view0turn18view1
Which provider is best for a Poland-first MVP? Use Autenti as the primary provider. It best matches the Polish rental use case because MamNajem does not only need QES; it needs a spectrum of documentary, advanced, and qualified flows with mobile-friendly, account-free signing and good API/callback support. Use KIR mSzafir/Szafir as the direct local QES fallback where you want a national qualified-signature backbone or a stronger long-term trust/archival story. Treat Docusign and Adobe Acrobat Sign as later-stage options when internationalization or enterprise agreement tooling matters more than Poland-native consumer UX. citeturn21view0turn21view1turn25view1turn25view3turn21view3turn26search0turn22search0turn22search2turn21view8
What data model and audit trail are required? At minimum, MamNajem should own template versioning, render an immutable pre-sign PDF, hash every signed artifact, record the signer and identity-verification method, store a detailed event log, keep provider artifacts such as signature cards, certificates of completion, and audit reports, preserve delivery evidence for notices, and archive the full evidence bundle in immutable storage. For higher-risk documents, preserve qualified timestamps where available because Polish law recognizes qualified timestamps as giving an electronic document a “date certain.” citeturn34view0turn21view0turn22search1turn24view3turn21view7turn26search0turn26search1
The safest MVP architecture for MamNajem is therefore three layers, not one: MamNajem’s own in-app documentary evidence layer for operational records, Autenti as the default external execution layer for core lease documents, and QES / notarial hybrid handling for the subset of Polish rental documents where the law genuinely requires it. citeturn17view0turn34view0turn21view0turn21view1turn25view1turn21view3turn8view0turn7view3