Version 1.4 — dem update am and e start to apply from 29 October 2026.
1. Operator and scope
Na Francesco Paparo, project Omnipal, dey run di website omnipal.app, for Via Giovanni della Rocca 279, 80041 Boscoreale (Naples), Italy. Data requests: privacy@omnipal.app; support: support@omnipal.app.
Dis policy explain cookies, browser storage, and choices wey you get for website and extension. To know wetin dem use data do, di legal reasons, providers and your rights, read di Privacy Policy. Di Legal notice tell you who dey run di service.
Technical cookies wey di service you request strictly need dey separate from optional measurement. Di rules also cover storage wey no be cookies, as di Garante guidelines explain.
2. Sign-in cookies
| Name and scope | Purpose | Duration |
|---|---|---|
| omnipal_session — Omnipal account services | E dey maintain di authenticated session wey di user request. | Until expiry or revocation, up to 60 days. |
| omnipal_otp — Omnipal sign-in services | E dey link di email code request to di browser. | 15 minutes; di code wey we email fit work for 10 minutes. |
These na technical cookies; dem no be advertising tools. How long dem last no depend on whether you accept statistics. When cookie expire, e no instantly delete every server record; di Privacy Policy explain di cleanup rules.
3. Website storage
| Storage and name | Purpose | Duration or removal |
|---|---|---|
| localStorage — omnipal_privacy_v1 | E dey store separate choices for statistics and diagnostics, plus version and expiry. | Di choice dey valid for 180 days; after dat you need new choice. Local record wey don expire fit remain until you replace or remove am. |
| localStorage — omnipal-theme | Remembers the selected visual theme. | Until you change am or remove website data. |
| IndexedDB — omnipal-web-chat | E dey keep web chat history for de device. Na technical storage, e no dey use am for measurement or profiling. | Until dem delete de chats or remove website data. |
| sessionStorage — omnipal-native-client | E dey keep di desktop/mobile app context while you dey navigate. | Tab or WebView session, unless you remove am earlier. |
| sessionStorage — omnipal-referral | Temporarily keep invitation reference during account flow. | For di tab session, or until dem remove am while dem dey handle di referral. |
Preferences wey requested functions need no dey activate measurement. Di website no use dis storage for advertising wey follow person behaviour.
De web BYOK API key and text wey you never send dey stay for page memory: if you reload or close de page, dem go lost, and if you change provider, de key go clear. Conversations dey save for de browser (IndexedDB) unless you choose make dem no save. Native apps fit keep storage separate from de outside browser.
4. Optional statistics and diagnostics
“Privacy and measurement” get two independent choices, and both dey off for start:
- Statistics: combined counts by day, product surface, page category and event on Omnipal server. Dem no record visitor/session identifiers or free text. Retention threshold na 400 days, with periodic cleanup.
- Diagnostics: after you give separate consent, di client dey send categories wey dem don set beforehand go Omnipal API; na only di API dey forward dem go di EU Sentry project omnipal-diagnostics. Di event get error category, product surface, time and event identifier; e no carry user content, identity, email or di browser IP address. Sentry dey see di server IP and add technical metadata, including di server approximate location; dem disable storage of IP addresses inside events. Dem no load Sentry SDK for browser. How long dem keep events follow di plan: 90 days during di current free Business trial, then 30 days for di free Developer plan if no upgrade happen; dem no set custom retention. Combined issue records fit remain after individual events don go.
Dem no dey send optional events before you choose, after you reject, or after consent expire. If you withdraw consent, later submissions and ones wey still dey move go stop; data wey dem don receive no go return. Optional requests no carry session credentials. Dem no use visitor-identification cookies for dis measurement.
Choices dey last 180 days inside di browser wey save dem, and you fit change dem before then. Dem no enter account or extension settings backups automatically.
5. Google and external services
Google Sign-In dey load only after you choose “Use Google to sign in”. Before you choose am, di sign-in component no connect to Google. Di connection wey follow na for di authentication wey you request; e separate from statistics and diagnostics consent.
Inside di sign-in context wey you select, Google fit use im own cookies, identifiers and storage, also depending on your Google account session and browser settings. Google Privacy Policy describe these tools. You fit use email code without selecting Google. Google sign-in alone no authorize Gmail OAuth access.
| Component after choosing Google | Purpose | Observed duration |
|---|---|---|
| g_state — cookie for di website domain wey Google Sign-In dey write | E dey remember interaction state and preferences for Google sign-in. | Up to 180 days for di check wey dem do with browser wey no get Google session; later interactions fit update am. |
Before you choose Google, di clean-profile check no find dis cookie or connections from di component to Google. Cookies for di external Google account context also depend on earlier choices and di session wey Google dey manage.
Di website no dey load advertising tools, Google Analytics, session replay or Sentry SDK. Cloudflare dey provide DNS and mail forwarding; dis setup no add Cloudflare analytics banner to di website.
You fit buy through Polar. Polar checkout and di customer portal na external services with their own terms and Privacy Policy; when you open dem, you dey enter context wey separate from di Omnipal website.
6. Extension and device data
Di extension fit keep settings, keys, chats, Memo and research inside browser storage wey dem reserve for extensions and local archives. Dem no be advertising cookies, and no be all of dem dey expire automatically. Keys no get extra encryption for application level; JSON export go include dem only if you choose di explicit option, wey dey off by default.
Consent for extension different from consent for website. Firefox still dey apply browser permissions for technical and interaction data. If you delete account, device data no disappear automatically.
Even if dem store content locally, e fit still go provider when you ask for indexing, translation, transcription, AI processing or other remote features. Di Privacy Policy explain how data dey move.
7. Managing preferences and updates
Open “Privacy and measurement” again for bottom of pages, choose “Necessary only” or save each preference separately. For di extension, use settings. If you reject measurement, you still fit use di Service.
Browser tools fit remove cookies and storage. You fit need sign in again and lose preferences or local content; dis no automatically delete cloud data or copies wey providers get.
When big changes happen to di tools, we go update di information and give new choice where e necessary. Di Italian version dey for Cookie e archivi locali.