{"id":37717,"date":"2026-04-26T21:20:34","date_gmt":"2026-04-26T18:20:34","guid":{"rendered":"https:\/\/tet.lt\/?page_id=37717"},"modified":"2026-10-09T15:54:20","modified_gmt":"2026-10-09T12:54:20","slug":"salygos-privatumas","status":"publish","type":"page","link":"https:\/\/tet.lt\/lt\/industries\/saas\/terms-privacy\/","title":{"rendered":"SaaS paslaug\u0173 teikimo s\u0105lyg\u0173 ir privatumo politikos rengimas"},"content":{"rendered":"<section class=\"l-section wpb_row height_custom\"><div class=\"l-section-h i-cf\"><div class=\"g-cols via_flex valign_top type_default\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><h1>SaaS paslaug\u0173 teikimo s\u0105lyg\u0173 ir privatumo politikos rengimas<\/h1>\n<div class=\"at-a-glance\">\n<h2>TRUMPAI<\/h2>\n<ol>\n<li>SaaS paslaug\u0173 teikimo s\u0105lygos n\u0117ra svetain\u0117s s\u0105lygos ir nuostatos \u2013 jos reglamentuoja nuolatinius programin\u0117s \u012frangos prenumeratos santykius, apiman\u010dius veikimo laik\u0105, funkcij\u0173 pakeitimus, duomen\u0173 nuosavyb\u0119, nutraukim\u0105 ir atsakomyb\u0119. Bendrosios svetain\u0117s s\u0105lygos neaptaria n\u0117 vieno i\u0161 \u0161i\u0173 punkt\u0173.<\/li>\n<li>SaaS produkto privatumo politikoje turi b\u016bti apra\u0161yta, kaip produktas konkre\u010diai apdoroja duomenis \u2013 paskyros duomenis, naudojimo \u017eurnalus, programos duomenis \u2013 ne tik tai, kaip \u012fmon\u0117s svetain\u0117 naudoja slapukus.<\/li>\n<li>Verslo klientai reguliariai per\u017ei\u016bri paslaug\u0173 teikimo s\u0105lygas ir privatumo politik\u0105 atlikdami tiek\u0117jo patikrinim\u0105 \u2013 nei\u0161sam\u016bs, nestandartine kalba vartojami arba DPA prie\u0161taraujantys dokumentai sukelia trint\u012f pardavimo cikle.<\/li>\n<li>Visus SaaS teisinius dokumentus rengiame specialiai produktui, o ne pagal bendr\u0105 \u0161ablon\u0105 \u2013 s\u0105lygos atspindi, kaip programin\u0117 \u012franga i\u0161 tikr\u0173j\u0173 pristatoma, \u012fkainojama ir nutraukiama.<\/li>\n<li>I\u0161samus SaaS dokumentacijos paketas \u2013 paslaug\u0173 teikimo s\u0105lygos, privatumo politika, slapuk\u0173 politika, priimtino naudojimo politika ir duomen\u0173 tvarkymo priedas \u2013 si\u016blomas kaip fiksuoto mokes\u010dio paketas.<\/li>\n<\/ol>\n<\/div>\n<div class=\"highlight-box\">\n<p>SaaS paslaug\u0173 teikimo s\u0105lyg\u0173 ir privatumo politikos rengimas rei\u0161kia, kad vartotojams skirti teisiniai dokumentai, reglamentuojantys prenumeratos santykius ir apra\u0161antys duomen\u0173 tvarkym\u0105 ai\u0161kia, tikslia ir \u012fgyvendinama kalba, yra parengti. SaaS \u012fmon\u0117ms \u0161ie dokumentai vienu metu skirti dviem auditorijoms: galutiniams vartotojams, kurie turi suprasti, su kuo sutinka, ir \u012fmon\u0117s pirkim\u0173 komandoms, kurios juos per\u017ei\u016bri, ar jie atitinka teisinius reikalavimus, atsakomyb\u0117s prisi\u0117mimo rizik\u0105 ir BDAR tinkamum\u0105. Visus dokumentus, skirtus SaaS produktui, rengiame angl\u0173 kalba, o prireikus pateikiame ir lietuvi\u0173 kalba.<\/p>\n<\/div>\n<h2>Kod\u0117l SaaS s\u0105lygos ir privatumo politika skiriasi<\/h2>\n<p>Da\u017eniausia SaaS \u012fmoni\u0173 daroma klaida rengiant teisinius dokumentus yra bendro pob\u016bd\u017eio \u0161ablono naudojimas \u2013 arba programinei \u012frangai pritaikyto svetain\u0117s termin\u0173 \u0161ablono, arba i\u0161 termin\u0173 generavimo \u012frankio atsisi\u0173sto \u0161ablono. Bendriniai \u0161ablonai sukuria dokumentus, kurie yra arba per plat\u016bs (apima veikl\u0105, kuria \u012fmon\u0117 neu\u017esiima), arba per siauri (tr\u016bksta SaaS specifini\u0173 nuostat\u0173, kurios svarbios, kai kas nors nutinka ne taip).<\/p>\n<h3>Paslaug\u0173 teikimo s\u0105lygos: sutartis, reglamentuojanti nuolatin\u0119 prieig\u0105<\/h3>\n<p>SaaS paslaug\u0173 teikimo s\u0105lygos i\u0161 esm\u0117s skiriasi nuo el. prekybos s\u0105lyg\u0173 ir nuostat\u0173. El. prekybos s\u0105lygos reglamentuoja vienkartin\u012f sandor\u012f: klientas nusiperka produkt\u0105, j\u012f gauna ir santykiai i\u0161 esm\u0117s u\u017ebaigiami. SaaS s\u0105lygos reglamentuoja nuolatinius santykius: klientas moka u\u017e nuolatin\u0119 prieig\u0105 prie programin\u0117s \u012frangos, \u012fmon\u0117 nuolat teikia programin\u0119 \u012frang\u0105, o santykiai apima nuolatinius abiej\u0173 pusi\u0173 \u012fsipareigojimus \u2013 veikimo laik\u0105, palaikym\u0105, funkcij\u0173 keitim\u0105, duomen\u0173 tvarkym\u0105 ir galiausiai nutraukim\u0105. S\u0105lyg\u0173 dokumentas, kuriame neaptariami \u0161ie nuolatiniai aspektai \u2013 kas nutinka, kai programin\u0117 \u012franga nepasiekiama, ar \u012fmon\u0117 gali viena\u0161ali\u0161kai keisti funkcijas, kam priklauso kliento \u012fvedami duomenys, kiek laiko reikia prane\u0161ti apie nutraukim\u0105 \u2013 neatitinka savo pagrindinio komercinio tikslo.<\/p>\n<h3>Privatumo politika: taikoma konkre\u010diam produktui, o ne svetainei<\/h3>\n<p>SaaS produkto privatumo politikoje turi b\u016bti apra\u0161yta, kaip pats produktas tvarko asmens duomenis, o ne tik svetain\u0117. Daugumoje bendr\u0173j\u0173 privatumo politik\u0173 apra\u0161omas slapuk\u0173 steb\u0117jimas, kontaktini\u0173 form\u0173 pateikimas ir el. pa\u0161to rinkodara. SaaS produktas apdoroja daug daugiau: paskyros registracijos duomenis, profilio informacij\u0105, naudotoj\u0173 veikl\u0105 platformoje, naudotoj\u0173 \u012fkeltus dokumentus ar \u012fra\u0161us, bendravim\u0105 per produkt\u0105, integracijos duomenis i\u0161 prijungt\u0173 tre\u010di\u0173j\u0173 \u0161ali\u0173 \u012franki\u0173 ir analiz\u0117s duomenis apie produkto naudojim\u0105. Privatumo politika, kuri netiksliai apra\u0161o \u0161i\u0105 tvarkymo veikl\u0105, neatitinka BDAR 13 straipsnio (kuris reikalauja skaidrumo d\u0117l viso tvarkymo duomen\u0173 rinkimo metu) ir sukuria klaiding\u0105 \u012fsp\u016bd\u012f apie tai, k\u0105 \u012fmon\u0117 i\u0161 tikr\u0173j\u0173 daro su naudotoj\u0173 duomenimis.<\/p>\n<h3>\u012emon\u0117s ap\u017evalga: komercinis aspektas<\/h3>\n<p>\u012emoni\u0173 pirkim\u0173 komandos per\u017ei\u016bri SaaS s\u0105lygas ir privatumo politik\u0105 kaip standartin\u0119 tiek\u0117j\u0173 \u012ftraukimo \u012f rink\u0105 dal\u012f. Jos ie\u0161ko konkre\u010di\u0173 nuostat\u0173: ai\u0161kaus atsakomyb\u0117s apribojimo (ir jo dyd\u017eio), garantijos atsisakymo, duomen\u0173 nuosavyb\u0117s s\u0105lyg\u0173, patvirtinan\u010di\u0173, kad klientas yra savo duomen\u0173 savininkas, duomen\u0173 perkeliamumo s\u0105lygos, patvirtinan\u010dios, kad duomenis galima eksportuoti papra\u0161ius, sutarties nutraukimo s\u0105lygos su tinkamais \u012fsp\u0117jimo laikotarpiais ir s\u0105lyg\u0173 keitimo nuostatos, kuri neleid\u017eia \u012fmonei viena\u0161ali\u0161kai keisti esmini\u0173 s\u0105lyg\u0173. \u012emon\u0117s duomen\u0173 apsaugos pareig\u016bno per\u017ei\u016brimoje privatumo politikoje turi b\u016bti tiksliai apra\u0161yti visi subtvarkytojai ir pateikta nuoroda \u012f duomen\u0173 tvarkymo sutart\u012f. Dokumentai, kurie neatitinka \u0161i\u0173 patikrinim\u0173 \u2013 d\u0117l nebuvimo, dviprasmyb\u0117s ar prie\u0161taravim\u0173 \u2013 gr\u0105\u017einami su komentarais, pridedant dien\u0173 ar savai\u010di\u0173 prie pardavimo ciklo.<\/p>\n<\/div><\/div>\n\t<div class=\"wpb_raw_code wpb_content_element wpb_raw_html\" >\n\t\t<div class=\"wpb_wrapper\">\n\t\t\t<h2>Dokumentai, kuriuos rengiame SaaS \u012fmon\u0117ms<\/h2>\n<p>Mes parengiame vis\u0105 vartotojams skirt\u0173 teisini\u0173 dokument\u0173 rinkin\u012f, skirt\u0105 SaaS produktams. Kiekvienas dokumentas yra parengtas specialiai produktui, o ne pagal bendr\u0105 \u0161ablon\u0105, ir atnaujinamas atsi\u017evelgiant \u012f produkto ir reguliavimo aplinkos poky\u010dius.<\/p>\n\n<div class=\"service-card\">\n  <div class=\"service-icon\">\n    <i class=\"fas fa-file-alt\" style=\"color: #bfa161; font-size: 2rem;\"><\/i>\n  <\/div>\n  <div class=\"service-content\">\n    <strong>SaaS paslaug\u0173 teikimo s\u0105lygos<\/strong>\n    <p><em>K\u0105 tai apima:<\/em> Sutartis, reglamentuojanti prieig\u0105 prie programin\u0117s \u012frangos \u2013 k\u0105 \u012fmon\u0117 pateikia, u\u017e k\u0105 ji atsakinga, kam priklauso duomenys ir kaip bet kuri \u0161alis gali nutraukti sutart\u012f.<\/p>\n    <ul class=\"checkmark\">\n      <li>Licencijos suteikimas \u2013 programin\u0117s \u012frangos licencijos apimtis (pagal darbo vietas, pagal naudojim\u0105 ar visoje \u012fmon\u0117je); leid\u017eiami naudojimo b\u016bdai; apribojimai.<\/li>\n      <li>Priimtinas naudojimas \u2013 k\u0105 vartotojai gali ir ko negali daryti su programine \u012franga; pa\u017eeidimo pasekm\u0117s<\/li>\n      <li>Paslaug\u0173 lygiai \u2013 veikimo laiko \u012fsipareigojimai (jei toki\u0173 yra); kas laikoma prastova; suplanuoti technin\u0117s prie\u017ei\u016bros langai<\/li>\n      <li>Palaikymo s\u0105lygos \u2013 palaikymo lygiai, reagavimo laikas, palaikymo apimtis, i\u0161imtys<\/li>\n      <li>Mokes\u010diai ir mok\u0117jimas \u2013 prenumeratos kainos, atsiskaitymo ciklas, mok\u0117jimo b\u016bdai, pav\u0117luotas mok\u0117jimas, kain\u0173 keitimo nuostatos<\/li>\n      <li>Duomen\u0173 nuosavyb\u0117 \u2013 kam priklauso duomenys, kuriuos klientas \u012fveda \u012f platform\u0105; k\u0105 \u012fmon\u0117 gali ir ko negali su jais daryti.<\/li>\n      <li>Duomen\u0173 perkeliamumas \u2013 kliento teis\u0117 eksportuoti savo duomenis; formatas ir terminai<\/li>\n      <li>Intelektin\u0117 nuosavyb\u0117 \u2013 \u012fmon\u0117s nuosavyb\u0117s teis\u0117 \u012f programin\u0119 \u012frang\u0105; kliento nuosavyb\u0117s teis\u0117 \u012f j\u0173 turin\u012f<\/li>\n      <li>Atsakomyb\u0117s riba \u2013 maksimali bendra \u012fmon\u0117s atsakomyb\u0117; netiesiogini\u0173 ir pasekmini\u0173 nuostoli\u0173 i\u0161imtys<\/li>\n      <li>Garantijos atsisakymas \u2013 k\u0105 \u012fmon\u0117 teikia ir ko negarantuoja d\u0117l programin\u0117s \u012frangos<\/li>\n      <li>Modifikacijos \u2013 \u012fmon\u0117s teis\u0117 keisti programin\u0119 \u012frang\u0105 ir s\u0105lygas; \u012fsp\u0117jimo laikotarpis; kliento teis\u0117 nutraukti sutart\u012f, jei pakeitimai yra esminiai.<\/li>\n      <li>Nutraukimas \u2013 bet kurios \u0161alies nutraukimo pagrindai; \u012fsp\u0117jimo laikotarpis; nutraukimo poveikis; duomen\u0173 tvarkymas po nutraukimo<\/li>\n      <li>Taikoma teis\u0117 \u2014 Lietuvos teis\u0117; Lietuvos teismai; ES vartotoj\u0173 apsaugos minimal\u016bs reikalavimai, jei taikoma<\/li>\n    <\/ul>\n  <\/div>\n<\/div>\n\n<div class=\"highlight-box\">\n  <strong>Atsakomyb\u0117s apribojimas \u2013 svarbiausia s\u0105lyga<\/strong>\n  <p>SaaS \u012fmonei atsakomyb\u0117s riba paslaug\u0173 teikimo s\u0105lygose yra svarbiausia komercin\u0117 teisin\u0117 s\u0105lyga. Nesant ribos, klientas, kurio versl\u0105 sutrikd\u0117 platformos sutrikimas, gali reikalauti neribotos \u017ealos atlyginimo \u2013 potencialiai didesn\u0117s nei metin\u0117 prenumeratos vert\u0117. Standartin\u0117 riba apriboja bendr\u0105 atsakomyb\u0119 iki 12 m\u0117nesi\u0173 sumok\u0117t\u0173 prenumeratos mokes\u010di\u0173. Kai kurie verslo klientai derasi d\u0117l didesni\u0173 rib\u0173 konkre\u010dioms rizikos kategorijoms; pradin\u0117 pozicija visada tur\u0117t\u0173 b\u016bti riba, niekada neribota atsakomyb\u0117. Mes \u012ftraukiame atsakomyb\u0117s rib\u0105 \u012f kiekvienas m\u016bs\u0173 parengtas SaaS paslaug\u0173 teikimo s\u0105lygas ir patariame, koks ribos lygis yra komerci\u0161kai tinkamas atsi\u017evelgiant \u012f produkto rizikos profil\u012f.<\/p>\n<\/div>\n\n<div class=\"service-card\">\n  <div class=\"service-icon\">\n    <i class=\"fas fa-lock\" style=\"color: #bfa161; font-size: 2rem;\"><\/i>\n  <\/div>\n  <div class=\"service-content\">\n    <strong>SaaS privatumo politika<\/strong>\n    <p><em>K\u0105 tai apima:<\/em> BDAR reikalaujamas skaidrumo dokumentas, kuriame apra\u0161oma visa SaaS produkto asmens duomen\u0173 tvarkymo veikla \u2013 tai konkre\u010diam produktui b\u016bdinga, o ne bendra svetain\u0117s politika.<\/p>\n    <ul class=\"checkmark\">\n      <li>Duomen\u0173 valdytojo tapatyb\u0117 ir kontaktiniai duomenys \u2013 \u012fmon\u0117s pavadinimas, registracijos numeris, registruotas adresas, duomen\u0173 apsaugos kontaktinis asmuo<\/li>\n      <li>Tvarkom\u0173 asmens duomen\u0173 kategorijos \u2013 paskyros duomenys, naudojimo duomenys, produkto duomenys, integracijos duomenys, palaikymo komunikacijos<\/li>\n      <li>Tikslai ir teisinis pagrindas \u2013 kam duomenys naudojami; kiekvienos tvarkymo veiklos teisinis pagrindas (sutartis, teis\u0117tas interesas, sutikimas, teisin\u0117 prievol\u0117)<\/li>\n      <li>Duomen\u0173 saugojimo laikotarpiai \u2013 kiek laiko saugoma kiekviena duomen\u0173 kategorija; saugojimo nustatymo kriterijai, kai netaikomas fiksuotas laikotarpis<\/li>\n      <li>Bendrinimas su tre\u010diosiomis \u0161alimis \u2013 su kuo bendrinami duomenys; subtvarkytojai (AWS, \u201eStripe\u201c, analiz\u0117s \u012frankiai); bendrinimo pagrindas<\/li>\n      <li>Tarptautinis duomen\u0173 perdavimas \u2013 kai duomenys tvarkomi geografiniu po\u017ei\u016briu; perdavimo mechanizmai, skirti tvarkymui ne EEE \u0161alyse<\/li>\n      <li>Duomen\u0173 subjekto teis\u0117s \u2013 teisi\u0173 s\u0105ra\u0161as; kaip jas \u012fgyvendinti; atsakymo pateikimo terminai; teis\u0117 pateikti skund\u0105 VDPI<\/li>\n      <li>Automatizuotas sprendim\u0173 pri\u0117mimas \u2013 ar automatizuotas tvarkymas daro didel\u012f poveik\u012f vartotojams; 22 straipsnyje reikalaujama informacija<\/li>\n      <li>Slapuk\u0173 ir sekimo informacija \u2013 nustatyt\u0173 slapuk\u0173 tipai; tikslai; nuoroda \u012f slapuk\u0173 politik\u0105, kurioje pateikiama i\u0161sami informacija<\/li>\n      <li>Kontaktin\u0117 informacija duomen\u0173 apsaugos klausimams ir duomen\u0173 apsaugos pareig\u016bnui (jei paskirtas)<\/li>\n    <\/ul>\n  <\/div>\n<\/div>\n\n<div class=\"highlight-box\">\n  <strong>Produktui skirta privatumo politika, palyginti su bendrine<\/strong>\n  <p>SaaS \u012fmon\u0117s privatumo prane\u0161ime turi b\u016bti tiksliai apra\u0161yta asmens duomen\u0173 tvarkymo veikla, kuri\u0105 \u012fmon\u0117 vykdo kaip duomen\u0173 valdytoja, pagal BDAR 13 ir 14 straipsnius. Kai SaaS teik\u0117jas tvarko klient\u0173 \u012fkeltus asmens duomenis tik verslo kliento vardu, tas klientas paprastai veikia kaip valdytojas ir yra atsakingas u\u017e reikiamos privatumo informacijos pateikim\u0105 duomen\u0173 subjektams. SaaS teik\u0117jo tvarkymo \u012fsipareigojimai turi b\u016bti dokumentuoti atitinkamoje duomen\u0173 tvarkymo sutartyje (DPA). Teik\u0117jo privatumo prane\u0161ime tur\u0117t\u0173 b\u016bti atskirtas tvarkymas, atliekamas kaip valdytojui, ir tvarkymas, atliekamas klient\u0173 vardu kaip tvarkytojui. \u012emoni\u0173 duomen\u0173 apsaugos pareig\u016bnai, per\u017ei\u016brintys tiek\u0117j\u0173 privatumo politik\u0105, tikrina, ar apra\u0161yta tvarkymo veikla atitinka faktinius duomen\u0173 srautus. Neatitikimai tarp politikos ir faktinio tvarkymo yra BDAR i\u0161vada ir komercinis raudonas \u017eenklas. Mes rengiame privatumo politik\u0105 remdamiesi faktini\u0173 produkt\u0173 duomen\u0173 sraut\u0173 analize, o ne bendriniu \u0161ablonu.<\/p>\n<\/div>\n\n<div class=\"service-card\">\n  <div class=\"service-icon\">\n    <i class=\"fas fa-cookie-bite\" style=\"color: #bfa161; font-size: 2rem;\"><\/i>\n  <\/div>\n  <div class=\"service-content\">\n    <strong>Slapuk\u0173 politika ir sutikimo juostos specifikacija<\/strong>\n    <p><em>K\u0105 tai apima:<\/em> Slapuk\u0173 ir sekimo technologij\u0173 atskleidimas bei techniniai reikalavimai galiojan\u010diam sutikimui gauti, kai to reikalaujama pagal taikomus Lietuvos teis\u0117s aktus, \u012fgyvendinan\u010dius ES e. privatumo direktyv\u0105 ir BDAR. Neb\u016btiniems slapukams ir pana\u0161ioms sekimo technologijoms paprastai reikalingas i\u0161ankstinis informuotas sutikimas, o technologijoms, kurios yra grie\u017etai b\u016btinos norint teikti paslaug\u0105, kurios ai\u0161kiai pra\u0161o vartotojas, gali b\u016bti taikoma sutikimo i\u0161imtis. Slapuk\u0173 reikalavimai netur\u0117t\u0173 b\u016bti apib\u016bdinami kaip kylantys tik i\u0161 BDAR, o atskira slapuk\u0173 politika n\u0117ra visuotinai privaloma, kai visa reikiama informacija pateikiama per kit\u0105 prieinam\u0105 ir reikalavimus atitinkant\u012f mechanizm\u0105.<\/p>\n    <ul class=\"checkmark\">\n      <li>Slapuk\u0173 kategorijos \u2013 grie\u017etai b\u016btini, funkciniai, analitiniai, rinkodaros ir tre\u010di\u0173j\u0173 \u0161ali\u0173 slapukai; i\u0161vardyti nurodant tiksl\u0105 ir trukm\u0119<\/li>\n      <li>Konkretus slapuk\u0173 s\u0105ra\u0161as \u2013 \u012fvardyti slapukai su kiekvieno i\u0161dav\u0117jo, kategorijos, paskirties ir galiojimo pabaigos data<\/li>\n      <li>Sutikimo mechanizmo apra\u0161ymas \u2013 kaip gaunamas sutikimas d\u0117l neb\u016btin\u0173 slapuk\u0173; kaip pakeisti arba at\u0161aukti sutikim\u0105<\/li>\n      <li>Tre\u010di\u0173j\u0173 \u0161ali\u0173 slapuk\u0173 i\u0161dav\u0117jai \u2013 analiz\u0117s, reklamos ir palaikymo \u012franki\u0173, kurie nustato slapukus, pavadinimai<\/li>\n      <li>Sutikimo reklamjuost\u0117s technin\u0117 specifikacija \u2013 k\u016br\u0117jui keliami BDAR reikalavimus atitinkantys sutikimo \u012fgyvendinimo reikalavimai<\/li>\n      <li>N\u0117ra i\u0161 anksto pa\u017eym\u0117t\u0173 langeli\u0173 \u2013 specifikacija, patvirtinanti, kad sutikimo reklamjuost\u0117se nenaudojamos i\u0161 anksto pasirinktos parinktys<\/li>\n      <li>Vienodo matomumo reikalavimas \u2013 atmetimo mygtukas turi b\u016bti taip pat lengvai pasiekiamas kaip ir pri\u0117mimo mygtukas<\/li>\n      <li>Sutikimo \u012fra\u0161\u0173 reikalavimai \u2013 kokie sutikimo duomenys turi b\u016bti saugomi ir kiek laiko<\/li>\n    <\/ul>\n  <\/div>\n<\/div>\n\n<div class=\"service-card\">\n  <div class=\"service-icon\">\n    <i class=\"fas fa-ban\" style=\"color: #bfa161; font-size: 2rem;\"><\/i>\n  <\/div>\n  <div class=\"service-content\">\n    <strong>Priimtino naudojimo politika (PNA)<\/strong>\n    <p><em>K\u0105 tai apima:<\/em> Apibr\u0117\u017eia, k\u0105 vartotojai gali ir ko negali daryti su SaaS platforma \u2013 apsaugo \u012fmon\u0119 nuo atsakomyb\u0117s u\u017e vartotoj\u0173 sukurt\u0105 turin\u012f ir draud\u017eiam\u0105 veikl\u0105, kartu nustatant ai\u0161kius pagrindus paskyros sustabdymui.<\/p>\n    <ul class=\"checkmark\">\n      <li>Leid\u017eiami naudojimo b\u016bdai \u2013 teis\u0117to, numatyto programin\u0117s \u012frangos naudojimo kategorijos<\/li>\n      <li>Draud\u017eiama veikla \u2013 konkretus draud\u017eiam\u0173 naudojimo b\u016bd\u0173 s\u0105ra\u0161as: neteis\u0117tas turinys, priekabiavimas, \u0161lam\u0161tas, intelektin\u0117s nuosavyb\u0117s pa\u017eeidimai, atvirk\u0161tin\u0117 in\u017einerija, saugumo testavimas be leidimo.<\/li>\n      <li>Saugumo \u012fsipareigojimai \u2013 k\u0105 vartotojai turi daryti, kad apsaugot\u0173 savo paskyros kredencialus ir u\u017ekirst\u0173 keli\u0105 neteis\u0117tai prieigai<\/li>\n      <li>Turinio standartai \u2013 reikalavimai vartotoj\u0173 kuriamam turiniui, kai platforma tai leid\u017eia.<\/li>\n      <li>Prane\u0161im\u0173 teikimo \u012fsipareigojimai \u2013 kaip vartotojai tur\u0117t\u0173 prane\u0161ti apie kit\u0173 vartotoj\u0173 padarytus pa\u017eeidimus ar saugumo incidentus<\/li>\n      <li>Pa\u017eeidimo pasekm\u0117s \u2013 \u012fmon\u0117s teis\u0117s pa\u017eeidimo atveju: \u012fsp\u0117jimas, veiklos sustabdymas, nutraukimas; teisini\u0173 reikalavim\u0173 i\u0161saugojimas<\/li>\n      <li>Vykdymo u\u017etikrinimo nuostatos \u2013 \u012fmon\u0117s teis\u0117 tirti \u012ftariamus pa\u017eeidimus ir bendradarbiauti su teisin\u0117mis institucijomis<\/li>\n    <\/ul>\n  <\/div>\n<\/div>\n\n<div class=\"service-card\">\n  <div class=\"service-icon\">\n    <i class=\"fas fa-file-signature\" style=\"color: #bfa161; font-size: 2rem;\"><\/i>\n  <\/div>\n  <div class=\"service-content\">\n    <strong>Duomen\u0173 apdorojimo priedas (DPA) B2B s\u0105lygoms<\/strong>\n    <p><em>K\u0105 tai apima:<\/em> Duomen\u0173 tvarkymo sutartis (DTS), atitinkanti BDAR 28 straipsnio reikalavimus, \u012ftraukta \u012f SaaS prenumeratos s\u0105lygas arba prie j\u0173 prid\u0117ta, kai SaaS teik\u0117jas tvarko asmens duomenis verslo kliento vardu. DTS reikalinga, kai \u0161alys yra susijusios su duomen\u0173 valdytojo ir tvarkytojo santykiais. Ji n\u0117ra automati\u0161kai privaloma kiekvienam B2B SaaS klientui, nes \u0161alys gali veikti kaip nepriklausomi duomen\u0173 valdytojai arba bendri duomen\u0173 valdytojai tam tikroje tvarkymo veikloje. J\u0173 atitinkami BDAR vaidmenys turi b\u016bti nustatyti atsi\u017evelgiant \u012f faktinius tvarkymo tikslus ir priemones.<\/p>\n    <ul class=\"checkmark\">\n      <li>Dalykas ir trukm\u0117 \u2013 kokie duomenys tvarkomi ir kiek laiko<\/li>\n      <li>Tvarkymo pob\u016bdis ir tikslas \u2013 konkreti tvarkymo veikla, kuri\u0105 SaaS platforma atlieka kliento vardu.<\/li>\n      <li>Asmens duomen\u0173 tipas ir duomen\u0173 subjekt\u0173 kategorijos \u2013 platformos tvarkom\u0173 duomen\u0173 kategorij\u0173 nustatymas<\/li>\n      <li>Duomen\u0173 tvarkytojo \u012fsipareigojimai \u2013 visas 28(3) straipsnio s\u0105ra\u0161as: tvarkyti tik pagal nurodymus; konfidencialumas; saugumo priemon\u0117s; subtvarkytojo valdymas; pagalba u\u017etikrinant duomen\u0173 subjekto teises; prane\u0161imas apie pa\u017eeidim\u0105; i\u0161trynimas arba gr\u0105\u017einimas; bendradarbiavimas atliekant audit\u0105.<\/li>\n      <li>Saugumo priedas (technin\u0117s ir organizacin\u0117s priemon\u0117s) \u2013 klient\u0173 duomenims taikoma saugumo sistema<\/li>\n      <li>Nuostatos d\u0117l subrangov\u0173 \u2013 dabartinis subrangov\u0173 s\u0105ra\u0161as; prane\u0161im\u0173 apie papildymus tvarka; kliento prie\u0161taravim\u0173 mechanizmas<\/li>\n      <li>Tarptautinio duomen\u0173 perdavimo nuostatos \u2013 asmens duomen\u0173 perdavimo \u012f tre\u010di\u0105sias \u0161alis nustatymas ir tinkamo perdavimo mechanizmo \u012fdiegimas pagal BDAR V skyri\u0173, kai to reikalaujama. Tai gali apimti taikytin\u0105 Europos Komisijos sprendim\u0105 d\u0117l tinkamumo, standartines sutar\u010di\u0173 s\u0105lygas (SSS) arba kit\u0105 teisi\u0161kai pripa\u017eint\u0105 perdavimo mechanizm\u0105. SSS neb\u016btinai reikalingos kiekvienai duomen\u0173 tvarkymo veiklai u\u017e EEE rib\u0173, ypa\u010d kai taikomas sprendimas d\u0117l tinkamumo taikomas gav\u0117jui ir perdavimui.<\/li>\n      <li>Duomen\u0173 gr\u0105\u017einimo ir i\u0161trynimo grafikas \u2013 kliento duomen\u0173 gr\u0105\u017einimo arba i\u0161trynimo terminas ir formatas nutraukus sutart\u012f<\/li>\n    <\/ul>\n  <\/div>\n<\/div>\n\n<div class=\"service-card\">\n  <div class=\"service-icon\">\n    <i class=\"fas fa-download\" style=\"color: #bfa161; font-size: 2rem;\"><\/i>\n  <\/div>\n  <div class=\"service-content\">\n    <strong>Galutinio vartotojo licencijos sutartis (EULA)<\/strong>\n    <p><em>K\u0105 tai apima:<\/em> SaaS produktams su atsisiun\u010diamu arba \u012fdiegiamu komponentu \u2013 darbalaukio programa, mobili\u0105ja program\u0117le, nar\u0161ykl\u0117s pl\u0117tiniu arba vietoje \u012fdiegta programine \u012franga \u2013 EULA reglamentuoja licencij\u0105 naudoti t\u0105 konkret\u0173 programin\u0117s \u012frangos element\u0105 kartu su \u017einiatinklio prenumerata.<\/p>\n    <ul class=\"checkmark\">\n      <li>Programin\u0117s \u012frangos licencija \u2013 konkreti atsisiun\u010diamo \/ \u012fdiegiamo komponento licencija; leid\u017eiamos platformos ir \u012frenginiai.<\/li>\n      <li>Diegimo ir sistemos reikalavimai \u2013 k\u0105 vartotojas turi tur\u0117ti nor\u0117damas \u012fdiegti programin\u0119 \u012frang\u0105<\/li>\n      <li>Naudojimo apribojimai \u2013 nuostatos, susijusios su neteis\u0117tu programin\u0117s \u012frangos kopijavimu, modifikavimu, atvirk\u0161tine in\u017einerija ir dekompiliavimu, laikantis privalom\u0173 i\u0161im\u010di\u0173 pagal taikomus autori\u0173 teisi\u0173 \u012fstatymus. Pagal Direktyv\u0105 2009\/24\/EB ir jos \u012fgyvendinim\u0105 Lietuvos teis\u0117je tam tikra veikla, susijusi su steb\u0117jimu, tyrimu, bandymu, atsargini\u0173 kopij\u0173 k\u016brimu ir dekompiliavimu s\u0105veikumo tikslais, gali b\u016bti leid\u017eiama be teisi\u0173 tur\u0117tojo leidimo, jei tenkinamos \u012fstatym\u0173 nustatytos s\u0105lygos. Sutartiniai apribojimai neturi neteis\u0117tai panaikinti privalom\u0173 teisi\u0173, suteikiam\u0173 teis\u0117tiems naudotojams.<\/li>\n      <li>Atnaujinimai ir versijos \u2013 \u012fmon\u0117s teis\u0117 i\u0161leisti atnaujinimus; automatini\u0173 atnaujinim\u0173 nuostatos; versij\u0173 palaikymo gyvavimo ciklas<\/li>\n      <li>Nutraukimas \u2013 kaip licencija nutraukiama; \u012fsipareigojimas i\u0161trinti programin\u0119 \u012frang\u0105 nutraukus licencij\u0105<\/li>\n      <li>Ry\u0161ys su prenumeratos s\u0105lygomis \u2013 kaip EULA s\u0105veikauja su visa apiman\u010dia SaaS prenumeratos sutartimi.<\/li>\n      <li>Garantija ir atsakomyb\u0117 \u2013 ribota programin\u0117s \u012frangos garantija; atitinka pagrindines atsakomyb\u0117s ribas<\/li>\n    <\/ul>\n  <\/div>\n<\/div>\n\t\t<\/div>\n\t<\/div>\n<div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><h2>\u012e k\u0105 \u012fmon\u0117s klientai atkreipia d\u0117mes\u012f j\u016bs\u0173 s\u0105lygose ir privatumo politikoje<\/h2>\n<p>\u012emoni\u0173 pirkim\u0173 komandos ir j\u0173 teisiniai patar\u0117jai, vertindami naujo SaaS tiek\u0117jo teisin\u0119 dokumentacij\u0105, vadovaujasi nuoseklia per\u017ei\u016bros schema. Supratimas, k\u0105 jie tikrina, ir u\u017etikrinimas, kad ji b\u016bt\u0173 pateikta ir ai\u0161kiai suformuluota, sutrumpina teisin\u0117s per\u017ei\u016bros laik\u0105 ir pagreitina sutarties sudarym\u0105.<\/p>\n<table class=\"services-table\">\n<thead>\n<tr>\n<th width=\"173\">K\u0105 jie tikrina<\/th>\n<th width=\"225\">Paslaug\u0173 teikimo s\u0105lygose<\/th>\n<th width=\"225\">Privatumo politikoje<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td width=\"173\"><strong>Atsakomyb\u0117s riba<\/strong><\/td>\n<td width=\"225\">Ar yra riba? Kokia suma? Ar yra koki\u0173 nors neribojam\u0173 kategorij\u0173?<\/td>\n<td width=\"225\">N\/A<\/td>\n<\/tr>\n<tr>\n<td width=\"173\"><strong>Duomen\u0173 nuosavyb\u0117<\/strong><\/td>\n<td width=\"225\">Ar \u012fmon\u0117 turi koki\u0173 nors teisi\u0173 \u012f klient\u0173 duomenis? Ar ji gali naudoti duomenis savo tikslais?<\/td>\n<td width=\"225\">Ar klient\u0173 duomenys naudojami modeli\u0173 mokymui, analizei ar produkt\u0173 tobulinimui?<\/td>\n<\/tr>\n<tr>\n<td width=\"173\"><strong>Duomen\u0173 perkeliamumas<\/strong><\/td>\n<td width=\"225\">Ar klientas gali eksportuoti savo duomenis? Kokiu formatu? Per kok\u012f laikotarp\u012f?<\/td>\n<td width=\"225\">Kokiu formatu teikiami duomenys perk\u0117limo pra\u0161ymams?<\/td>\n<\/tr>\n<tr>\n<td width=\"173\"><strong>Nutraukimas<\/strong><\/td>\n<td width=\"225\">Kok\u012f prane\u0161im\u0105 reikia pateikti? Kas nutinka duomenims po nutraukimo? Ar yra lengvatinis laikotarpis?<\/td>\n<td width=\"225\">Koks yra duomen\u0173 saugojimo laikotarpis po paskyros u\u017edarymo?<\/td>\n<\/tr>\n<tr>\n<td width=\"173\"><strong>Aptarnavimo lygis<\/strong><\/td>\n<td width=\"225\">Ar yra \u012fsipareigojimas d\u0117l veikimo laiko? Kokia yra prastov\u0173 sprendimo priemon\u0117?<\/td>\n<td width=\"225\">N\/A<\/td>\n<\/tr>\n<tr>\n<td width=\"173\"><strong>S\u0105lyg\u0173 pakeitimas<\/strong><\/td>\n<td width=\"225\">Ar \u012fmon\u0117 gali viena\u0161ali\u0161kai keisti s\u0105lygas? Koks \u012fsp\u0117jimas apie tai? Ar klientas gali nutraukti sutart\u012f?<\/td>\n<td width=\"225\">Ar \u012fmon\u0117 atnaujina privatumo politik\u0105? Kaip apie tai prane\u0161ama?<\/td>\n<\/tr>\n<tr>\n<td width=\"173\"><strong>Subtvarkytojai<\/strong><\/td>\n<td width=\"225\">N\/A<\/td>\n<td width=\"225\">Ar i\u0161vardyti subrangov\u0173 duomen\u0173 tvarkytojai? Ar standartin\u0117s sutarties s\u0105lygos taikomos tarptautiniams duomen\u0173 perdavimams?<\/td>\n<\/tr>\n<tr>\n<td width=\"173\"><strong>DPA kry\u017emin\u0117 nuoroda<\/strong><\/td>\n<td width=\"225\">Ar s\u0105lygose yra nuoroda \u012f DPA arba DPA pried\u0105?<\/td>\n<td width=\"225\">Ar privatumo politikoje yra nuoroda \u012f Duomen\u0173 apsaugos \u012fstatym\u0105 (DPA), skirt\u0105 B2B duomen\u0173 tvarkymui?<\/td>\n<\/tr>\n<tr>\n<td width=\"173\"><strong>Taikoma teis\u0117<\/strong><\/td>\n<td width=\"225\">Koks \u012fstatymas? Kurie teismai? Ar i\u0161saugomi ES vartotoj\u0173 minimal\u016bs \u012fkainiai?<\/td>\n<td width=\"225\">Kuri prie\u017ei\u016bros institucija? VDPI nurodyta?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Kokie bendrieji \u0161ablonai yra neteisingi SaaS atveju?<\/h2>\n<p>Bendrieji terminai ir privatumo politikos \u0161ablonai \u2013 nesvarbu, ar i\u0161 generatoriaus \u012frankio, teisini\u0173 \u0161ablon\u0173 bibliotekos, ar pasiskolinti i\u0161 kitos \u012fmon\u0117s svetain\u0117s \u2013 nuolat nusp\u0117jamai nuvilia SaaS \u012fmones. \u010cia pateikiamos da\u017eniausios problemos, su kuriomis susiduriame per\u017ei\u016br\u0117dami esam\u0105 dokumentacij\u0105.<\/p>\n<h3>N\u0117ra atsakomyb\u0117s ribos<\/h3>\n<p>Da\u017eniausias bendr\u0173j\u0173 SaaS s\u0105lyg\u0173 tr\u016bkumas. Daugumoje svetaini\u0173 s\u0105lyg\u0173 \u0161ablon\u0173 n\u0117ra atsakomyb\u0117s ribos, nes jie buvo para\u0161yti ma\u017eiau rizikingiems komerciniams santykiams. SaaS \u012fmon\u0117, veikianti pagal s\u0105lygas be atsakomyb\u0117s ribos, gali kelti neribotas pretenzijas prenumeratos verte, o tai gali b\u016bti katastrofi\u0161ka reik\u0161mingo incidento atveju. \u0160i\u0105 nuostat\u0105 pridedame arba pakei\u010diame kiekvienoje s\u0105lyg\u0173 per\u017ei\u016bros u\u017eduotyje.<\/p>\n<h3>Neteisinga arba tr\u016bkstama duomen\u0173 nuosavyb\u0117s s\u0105lyga<\/h3>\n<p>Bendruose \u0161ablonuose da\u017enai vartojama miglota informacija apie duomenis, pvz., \u2018mes galime naudoti j\u016bs\u0173 duomenis savo paslaugoms tobulinti\u2019, ta\u010diau konkre\u010diai nenurodoma, ar tai rei\u0161kia, kad kliento duomenys naudojami modeliams mokyti, na\u0161umui lyginti ar apibendrintoms \u012f\u017evalgoms kurti. Verslo klientai atid\u017eiai perskaito \u0161ias s\u0105lygas. Dviprasmi\u0161ka kalba sukelia pra\u0161ymus paai\u0161kinti, kurie vilkina sutartis. Ai\u0161ki, konkreti duomen\u0173 nuosavyb\u0117s s\u0105lyga, patvirtinanti, kad kliento duomenys priklauso klientui, ir tiksliai apra\u0161anti, k\u0105 \u012fmon\u0117 su jais daro ir ko nedaro, pa\u0161alina \u0161i\u0105 trint\u012f.<\/p>\n<h3>N\u0117ra duomen\u0173 perkeliamumo nuostatos<\/h3>\n<p>Pagal BDAR 20 straipsn\u012f asmenys turi teis\u0119 \u012f duomen\u0173 perkeliamum\u0105, kai tvarkymas grind\u017eiamas sutikimu arba sutartimi ir atliekamas automatizuotomis priemon\u0117mis, laikantis kit\u0173 \u012fstatymini\u0173 s\u0105lyg\u0173. \u0160i teis\u0117 paprastai apima asmens duomenis, kuriuos asmuo pateik\u0117 duomen\u0173 valdytojui, ir nesukuria neribotos teis\u0117s eksportuoti vis\u0105 SaaS platformoje saugom\u0105 informacij\u0105. Verslo kliento sutartin\u0117 teis\u0117 eksportuoti savo \u012fmon\u0117s duomenis yra atskiras klausimas, reglamentuojamas prenumeratos sutarties ir, jei taikoma, ES teis\u0117s akt\u0173, toki\u0173 kaip Duomen\u0173 apsaugos \u012fstatymas. SaaS s\u0105lygose tur\u0117t\u0173 b\u016bti ai\u0161kiai aptartas kliento duomen\u0173 eksportas, galimi formatai, taikomi terminai ir pagalba perk\u0117limo metu, kartu atskiriant sutartines perkeliamumo teises nuo BDAR duomen\u0173 subjekto teisi\u0173.<\/p>\n<h3>Privatumo politika apib\u016bdina svetain\u0119, o ne produkt\u0105<\/h3>\n<p>Da\u017eniausia SaaS \u012fmoni\u0173 privatumo politikos problema. Privatumo politika buvo para\u0161yta siekiant apra\u0161yti \u012fmon\u0117s svetain\u0119 \u2013 slapukus, kontaktines formas, el. pa\u0161to rinkodar\u0105 \u2013 o v\u0117liau pertvarkyta \u012f produkto privatumo politik\u0105 neatnaujinus, kad atspind\u0117t\u0173 tai, k\u0105 produktas i\u0161 tikr\u0173j\u0173 daro. \u012emon\u0117s duomen\u0173 apsaugos pareig\u016bnas, per\u017ei\u016br\u0117j\u0119s politik\u0105 pagal faktinius produkto duomen\u0173 srautus, nedelsdamas nustatys neatitikim\u0105. Mes rengiame privatumo politik\u0105, remdamiesi faktin\u0117s produkto duomen\u0173 tvarkymo veiklos analize.<\/p>\n<h3>S\u0105lygos ir privatumo politika prie\u0161tarauja DPA<\/h3>\n<p>B2B SaaS \u012fmon\u0117ms, turin\u010dioms atskir\u0105 duomen\u0173 apdorojimo sutart\u012f (DPA), s\u0105lygos ir privatumo politika turi atitikti j\u0105. Jei s\u0105lygose nurodoma, kad \u012fmon\u0117 gali naudoti klient\u0173 duomenis analizei, ta\u010diau DPA nurodoma, kad \u012fmon\u0117 tvarko duomenis tik pagal kliento nurodymus, dokumentai prie\u0161tarauja vienas kitam. \u012emoni\u0173 teisinink\u0173 komandos pa\u017eymi prie\u0161taravimus, nes jie sukelia neai\u0161kum\u0173 d\u0117l to, kuris dokumentas yra svarbiausias. Visus dokumentus rengiame kaip integruot\u0105 rinkin\u012f, u\u017etikrindami, kad s\u0105lygos, privatumo politika ir DPA b\u016bt\u0173 nuosekl\u016bs.<\/p>\n<h2>Dokument\u0173 rengimo kainos<\/h2>\n<p>Visiems dokumentams taikoma fiksuota kaina \u2013 jie pateikiami angl\u0173 kalba, redaguojamu formatu, paruo\u0161ti per\u017ei\u016brai ir publikavimui. Visiems dokumentams, kurie pagal Lietuvos \u012fstatymus turi b\u016bti pateikti lietuvi\u0173 kalba, pateikiamos angli\u0161kos versijos. Dokumentai rengiami specialiai SaaS produktui, o ne pagal bendr\u0105 \u0161ablon\u0105.<\/p>\n<table class=\"services-table\">\n<thead>\n<tr>\n<th width=\"360\">Dokumentas \/ paslauga<\/th>\n<th width=\"264\">Kaina<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td width=\"360\"><strong>SaaS paslaug\u0173 teikimo s\u0105lygos \u2013 standartin\u0117s (B2B)<\/strong><br \/>\n<em>Full subscription terms including licence, SLA, liability cap, data ownership, termination; English + Lithuanian<\/em><\/td>\n<td width=\"264\"><strong>\u20ac900<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>SaaS terms of service \u2014 B2C (consumer-facing)<\/strong><br \/>\n<em>Standard terms plus EU Consumer Rights Directive mandatory provisions; withdrawal rights and consumer protections<\/em><\/td>\n<td width=\"264\"><strong>\u20ac1,250<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>SaaS terms of service \u2014 freemium model<\/strong><br \/>\n<em>Covering both free and paid tiers; upgrade and conversion provisions; feature restrictions between tiers<\/em><\/td>\n<td width=\"264\"><strong>\u20ac1,200<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Privacy policy \u2014 SaaS product-specific<\/strong><br \/>\n<em>Full product data mapping input; GDPR Articles 13\/14 compliant; sub-processor list referenced; English + Lithuanian<\/em><\/td>\n<td width=\"264\"><strong>\u20ac700<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Slapuk\u0173 politika + sutikimo juostos specifikacija<\/strong><br \/>\n<em>Named cookie list; consent banner technical requirements for compliant GDPR implementation<\/em><\/td>\n<td width=\"264\"><strong>\u20ac550<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Acceptable use policy (AUP)<\/strong><br \/>\n<em>Prohibited activities, content standards, security obligations, enforcement rights<\/em><\/td>\n<td width=\"264\"><strong>\u20ac650<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Data Processing Addendum (DPA) \u2014 B2B embedded<\/strong><br \/>\n<em>Article 28-compliant; security annex; sub-processor provisions; SCC clause \u2014 as schedule to subscription terms<\/em><\/td>\n<td width=\"264\"><strong>\u20ac600<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Galutinio vartotojo licencijos sutartis (EULA)<\/strong><br \/>\n<em>For SaaS products with downloadable or installable components<\/em><\/td>\n<td width=\"264\"><strong>\u20ac700<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Existing terms review and gap report<\/strong><br \/>\n<em>Written analysis identifying missing provisions, template problems, and priority amendments<\/em><\/td>\n<td width=\"264\"><strong>\u20ac700<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Terms amendment \u2014 adding liability cap and data ownership<\/strong><br \/>\n<em>Adding the two highest-priority missing provisions to existing terms<\/em><\/td>\n<td width=\"264\"><strong>\u20ac600<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Annual document review and update<\/strong><br \/>\n<em>Reviewing existing documents against current regulatory guidance and product changes<\/em><\/td>\n<td width=\"264\"><strong>\u20ac200\u2013\u20ac350 per document<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Enterprise terms redline response<\/strong><br \/>\n<em>Reviewing and responding to client-proposed changes to the standard terms; written commentary<\/em><\/td>\n<td width=\"264\"><strong>\u20ac650<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>SaaS standard documentation package (ToS + privacy policy + cookie policy + AUP + DPA)<\/strong><br \/>\n<em>Five core documents for a B2B SaaS product launch. The individual prices are EUR 900 for the Terms of Service, EUR 700 for the Privacy Policy, EUR 550 for the Cookie Policy, EUR 650 for the Acceptable Use Policy and EUR 600 for the Data Processing Addendum. The combined standalone price is EUR 3,400. Package price: EUR 3,100, representing a saving of EUR 300.<\/em><\/td>\n<td width=\"264\"><strong>\u20ac3,100<\/strong><\/td>\n<\/tr>\n<tr>\n<td width=\"360\"><strong>Full SaaS documentation suite (all 6 documents including EULA)<\/strong><br \/>\n<em>Six-document package including the standard SaaS Terms of Service, Privacy Policy, Cookie Policy, Acceptable Use Policy, Data Processing Addendum and End-User Licence Agreement (EULA). The combined standalone price of these documents is EUR 4,100. Package price: EUR 3,500, representing a saving of EUR 600.<\/em><\/td>\n<td width=\"264\"><strong>\u20ac3,500<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"highlight-box\">\n<p><strong>SaaS standard documentation package \u2014 what&#8217;s included<br \/>\n<\/strong>The \u20ac3,100 package delivers the five documents every B2B SaaS company needs before onboarding clients: terms of service with liability cap and data ownership clause, a product-specific privacy policy, a cookie policy with consent banner specification, an acceptable use policy, and a data processing addendum. All five are drafted as an integrated set \u2014 internally consistent, specifically tailored to the product&#8217;s actual data processing, and formatted for immediate publication. Commissioning the five documents separately costs EUR 3,400, based on the individual prices published in the Document Drafting Prices table. The package price is EUR 3,100, providing a saving of EUR 300.<\/p>\n<\/div>\n<h2 style=\"text-align: center;\">Da\u017enai u\u017eduodami klausimai<\/h2>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section><section class=\"l-section wpb_row height_custom\"><div class=\"l-section-h i-cf\"><div class=\"g-cols via_flex valign_top type_default\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\"><div class=\"w-tabs style_default switch_click accordion has_scrolling\" style=\"--sections-title-size:inherit\"><div class=\"w-tabs-sections titles-align_none icon_chevron cpos_right\"><div class=\"w-tabs-section\" id=\"i884\"><button aria-controls=\"content-i884\" class=\"w-tabs-section-header\"><div class=\"w-tabs-section-title\">Can we use one set of terms for both free and paid users?<\/div><div class=\"w-tabs-section-control\"><\/div><\/button><div class=\"w-tabs-section-content\" id=\"content-i884\" aria-expanded=\"false\"><div class=\"w-tabs-section-content-h i-cf\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p>You can \u2014 but the terms must address both tiers clearly. The most common approach is a single terms document with provisions that distinguish between free plan users and paid subscribers: the licence grant section defines what features are available on each tier; the payment section applies only to paid plans; the SLA section confirms that free plans have no uptime guarantee while paid plans do (if applicable); and the support section specifies that free users have community support only. Alternatively, separate terms for free and paid tiers are cleaner but require maintenance of two documents. We draft freemium terms as a single document with clearly delineated tier-specific provisions \u2014 which is the most transparent approach for users and the most practical to maintain.<\/p>\n<\/div><\/div><\/div><\/div><\/div><div class=\"w-tabs-section\" id=\"w8fd\"><button aria-controls=\"content-w8fd\" class=\"w-tabs-section-header\"><div class=\"w-tabs-section-title\">Do our terms need to be in Lithuanian if we primarily sell internationally?<\/div><div class=\"w-tabs-section-control\"><\/div><\/button><div class=\"w-tabs-section-content\" id=\"content-w8fd\" aria-expanded=\"false\"><div class=\"w-tabs-section-content-h i-cf\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p>For international B2B SaaS transactions, English-language terms may generally be used where the parties agree and no mandatory language requirement applies. However, Lithuanian legislation may impose language requirements on particular contracts, transactions or documentation, including certain employment, consumer-facing and regulated activities. The applicable requirements should be assessed according to the parties, governing law and nature of the transaction. A universal exemption from Lithuanian-language requirements should not be assumed for all B2B contracts. However, if Lithuanian businesses are among your clients (even a minority), Lithuanian-language terms reduce friction in those relationships. For B2C sales \u2014 if your SaaS product has any consumer-facing tier available to Lithuanian residents \u2014 Lithuanian consumer protection law requires that material terms be accessible in a language the consumer understands. We provide all documents in English as the primary version and in Lithuanian where required, at no additional charge for the Lithuanian version.<\/p>\n<\/div><\/div><\/div><\/div><\/div><div class=\"w-tabs-section\" id=\"w968\"><button aria-controls=\"content-w968\" class=\"w-tabs-section-header\"><div class=\"w-tabs-section-title\">What is the difference between a DPA addendum in the terms and a standalone DPA?<\/div><div class=\"w-tabs-section-control\"><\/div><\/button><div class=\"w-tabs-section-content\" id=\"content-w968\" aria-expanded=\"false\"><div class=\"w-tabs-section-content-h i-cf\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p>A DPA addendum is a schedule or exhibit appended to or embedded in the subscription terms \u2014 every client who accepts the subscription terms simultaneously accepts the DPA. This is the most efficient approach for standard SaaS B2B sales: one document, one acceptance, everything covered. A standalone DPA is a separate document \u2014 clients who require their own separate signed DPA (which most large enterprises do) can use this. Most SaaS companies need both: a DPA addendum embedded in the standard terms for SME and mid-market clients who accept terms online, and a standalone DPA template for enterprise clients who require a separately signed version. We provide both as part of the standard documentation package.<\/p>\n<\/div><\/div><\/div><\/div><\/div><div class=\"w-tabs-section\" id=\"b9cf\"><button aria-controls=\"content-b9cf\" class=\"w-tabs-section-header\"><div class=\"w-tabs-section-title\">How often should we update our terms of service and privacy policy?<\/div><div class=\"w-tabs-section-control\"><\/div><\/button><div class=\"w-tabs-section-content\" id=\"content-b9cf\" aria-expanded=\"false\"><div class=\"w-tabs-section-content-h i-cf\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p>Terms of service should be reviewed and updated when: the product adds material new features that affect the commercial relationship (new data processing, new pricing model, new SLA obligations); when the company&#8217;s liability exposure changes; or when significant new legislation comes into force. Privacy policies must be updated when the actual data processing activities change \u2014 adding a new analytics tool, a new integration, or a new category of data collection requires an update before the processing begins. We recommend an annual review of all documentation as standard practice, and proactive updates when product or regulatory changes occur. We provide an annual document review service at \u20ac200\u2013\u20ac350 per document.<\/p>\n<\/div><\/div><\/div><\/div><\/div><div class=\"w-tabs-section\" id=\"fa2b\"><button aria-controls=\"content-fa2b\" class=\"w-tabs-section-header\"><div class=\"w-tabs-section-title\">Can enterprise clients require us to sign their own version of our terms rather than ours?<\/div><div class=\"w-tabs-section-control\"><\/div><\/button><div class=\"w-tabs-section-content\" id=\"content-fa2b\" aria-expanded=\"false\"><div class=\"w-tabs-section-content-h i-cf\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p>Enterprise clients frequently propose their own vendor agreement rather than accepting the SaaS company&#8217;s standard terms. This is a commercial negotiation, not a legal requirement \u2014 the SaaS company is not obligated to accept the client&#8217;s terms. The practical question is whether the client&#8217;s proposed terms are acceptable, and if not, which provisions require negotiation. Common enterprise-proposed terms that are commercially problematic for SaaS companies include: unlimited liability clauses, indemnification obligations for third-party IP claims, audit rights that are too broad, and source code escrow requirements. We review enterprise-proposed terms, identify the material concerns, and provide a negotiating strategy \u2014 with a marked-up version for response.<\/p>\n<\/div><\/div><\/div><\/div><\/div><div class=\"w-tabs-section\" id=\"la85\"><button aria-controls=\"content-la85\" class=\"w-tabs-section-header\"><div class=\"w-tabs-section-title\">What is a change-of-terms provision and why does it matter?<\/div><div class=\"w-tabs-section-control\"><\/div><\/button><div class=\"w-tabs-section-content\" id=\"content-la85\" aria-expanded=\"false\"><div class=\"w-tabs-section-content-h i-cf\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p>A change-of-terms provision defines the process by which the SaaS company can modify the terms of service. Without one, changing the terms requires agreement from every existing customer \u2014 commercially impractical for a SaaS company with hundreds of clients. With a well-drafted change-of-terms provision, the company can update the terms by giving advance notice (typically 30 days) and allowing customers who object to material changes to terminate without penalty. The enterprise review concern is that a change-of-terms provision that allows the company to change material terms unilaterally without adequate notice or exit rights is unfair to customers. The standard approach \u2014 30 days notice, material changes flagged specifically, right to terminate if customer objects \u2014 satisfies both the company&#8217;s commercial need for flexibility and the customer&#8217;s expectation of fair treatment.<\/p>\n<\/div><\/div><\/div><\/div><\/div><div class=\"w-tabs-section\" id=\"zadb\"><button aria-controls=\"content-zadb\" class=\"w-tabs-section-header\"><div class=\"w-tabs-section-title\">We have been operating for two years without a proper terms of service \u2014 how urgent is it to fix this?<\/div><div class=\"w-tabs-section-control\"><\/div><\/button><div class=\"w-tabs-section-content\" id=\"content-zadb\" aria-expanded=\"false\"><div class=\"w-tabs-section-content-h i-cf\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><p>Urgent \u2014 though the specific priority depends on your current situation. If you have enterprise clients reviewing or asking about your terms, the gap is creating active sales friction and should be addressed immediately. If you are pre-fundraising, investor due diligence will include a legal documentation review and inadequate terms will be flagged. If you are operating without any terms at all, every customer relationship is governed entirely by implied terms and applicable law \u2014 which leaves the company without the liability cap, warranty disclaimers, and data ownership provisions that protect it in disputes. The cost of drafting proper terms now is fixed and predictable. The cost of operating without them becomes visible only when something goes wrong \u2014 at which point the remedy is significantly more expensive.<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section><section class=\"l-section wpb_row height_custom\"><div class=\"l-section-h i-cf\"><div class=\"g-cols via_flex valign_top type_default\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\"><div class=\"wpb_text_column\"><div class=\"wpb_wrapper\"><div class=\"highlight-box\">\n<p><strong class=\"golden\">Ready to get your SaaS documentation in order?<\/strong><\/p>\n<p><a href=\"https:\/\/tet.lt\/lt\/kontaktas\/\">Susisiekite su mumis<\/a> to discuss your product, current documentation status, and immediate priorities. We will confirm which documents are most urgent, provide fixed-fee quotes, and begin drafting within 24 hours of your instruction. The SaaS standard documentation package \u2014 five core documents \u2014 is available at \u20ac3,100.<\/p>\n<\/div>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>","protected":false},"excerpt":{"rendered":"Terms of Service and Privacy Policy Drafting for SaaS AT A GLANCE SaaS terms of service are not website terms and conditions \u2014 they govern an ongoing software subscription relationship covering uptime, feature changes, data ownership, termination, and liability. Generic website terms do not address any of these. A privacy policy for a SaaS product...","protected":false},"author":1,"featured_media":0,"parent":37685,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"class_list":["post-37717","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/tet.lt\/lt\/wp-json\/wp\/v2\/pages\/37717","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tet.lt\/lt\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tet.lt\/lt\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tet.lt\/lt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tet.lt\/lt\/wp-json\/wp\/v2\/comments?post=37717"}],"version-history":[{"count":5,"href":"https:\/\/tet.lt\/lt\/wp-json\/wp\/v2\/pages\/37717\/revisions"}],"predecessor-version":[{"id":37757,"href":"https:\/\/tet.lt\/lt\/wp-json\/wp\/v2\/pages\/37717\/revisions\/37757"}],"up":[{"embeddable":true,"href":"https:\/\/tet.lt\/lt\/wp-json\/wp\/v2\/pages\/37685"}],"wp:attachment":[{"href":"https:\/\/tet.lt\/lt\/wp-json\/wp\/v2\/media?parent=37717"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}