Iris – Art & Drawing Reference: Privacy policy
Effective and last updated: 9 November 2026.
Iris is a reference library for drawing and painting. The data controller is Gjessing AS,
organisation number 937 651 414, Slyngveien 27, 1385 Asker, Norway. Lars Gjessing is the
contact for privacy and support at the address below. This policy covers the device-only
Android build distributed through Google Play, package
io.gjessing.iris, including its test tracks and optional hosted sync. It does
not describe a separately operated, self-hosted Iris server.
Your library stays on your device
References, original pictures and videos, thumbnails, source links, titles, creators, notes, tags, collections, favourites, library searches and viewing history are stored in Iris’s private storage on your device. Study tools process your pictures locally. A photo you choose for Compare is used for that comparison and is not saved in your library or uploaded. Library uploads are off by default. If you enable cloud sync, Iris encrypts your library on this device before sending it to the service described below.
The app needs no account and contains no advertising, analytics, tracking or automatic crash-reporting service. It does not sell your data, use advertising identifiers or send your installed-app list to anyone. Already imported references work offline.
When Iris connects to the internet
Online features make these requests directly from your device:
- Link preview and capture: when you paste or share a link for capture, Iris requests that URL and may follow redirects, request page metadata or an oEmbed endpoint, and download selected media from the source’s image or video hosts. These sites receive the requested URLs, including query parameters. Do not submit private links or links containing access tokens. Queued captures can continue in the background or resume after a restart; cancel them in Captures to stop further attempts.
-
Explore: searches and filters go to the collection you choose: Wikimedia
Commons (
commons.wikimedia.org), the Cleveland Museum of Art (openaccess-api.clevelandart.org), the Art Institute of Chicago (api.artic.edu) or SMK, the National Gallery of Denmark (api.smk.dk). Result thumbnails and selected originals come from Wikimedia’s image hosts (upload.wikimedia.organdthumb.wikimedia.org), Cleveland’sopenaccess-cdn.clevelandart.org, Chicago’s image server (www.artic.edu) or SMK’s image servers (iip.smk.dk,iip-thumb.smk.dkandapi.smk.dk). Artwork capture can also request the collection’s artwork metadata. Searching your own library stays on your device.
As with any internet request, the receiving site and its hosting providers can see your network IP address, request time and requested resource. Iris’s download client sends a general Iris User-Agent; it does not attach a unique installation identifier, browser login cookies or your library contents. It reads page metadata without running the source page’s scripts. Providers may keep request logs, infer approximate location from IP addresses and use requests to operate, secure and improve their services. Their retention and processing are governed by their own policies, including the Wikimedia privacy policy and the Cleveland privacy policy and API terms, the Art Institute of Chicago privacy policy and terms, and the SMK privacy policy.
Online downloads use HTTPS in the Play build. Android blocks unencrypted HTTP requests, including redirects to HTTP, so those sources cannot be fetched by this build. You can use local imports and study your library without using online capture or Explore.
Google Play billing
Iris checks Google Play purchases when the app opens or returns to the foreground. The Iris Pro page lets you buy or restore a one-time study-tool unlock using your Play account. Google processes the payment. Iris acknowledges completed Pro purchases through Google Play and saves the resulting access on this device, outside library backups, so established Pro access works offline. Pro purchase tokens stay transient in the app and are not sent to an Iris service. Reinstalling requires restoring through the same Play account. A successful store refresh can remove access after a refund; an unavailable store keeps previously acknowledged access.
Settings → Cloud sync opens the sync page. Opening this page creates a random cloud-library identity, protected by Android Keystore and kept outside library backups. Connecting a new cloud library requires a verified subscription and contacts Iris’s production service, hosted by Cloudflare. It sends the library’s public key and signed requests. After you verify your subscription and explicitly enable library sync, Sync now uploads encrypted originals and reference, collection, smart-list and canvas metadata. Only your devices hold the decryption and signing keys. The service cannot read library contents. Your recovery code contains these keys: keep it private and save it before resetting or replacing your phone. It can recover the same library and subscription binding on another installation without another purchase.
The sync page queries Google Play for subscription offers and existing purchases. Google processes purchases under its own terms and privacy policy, using your Play account and chosen payment method. Iris receives the product and offer details, purchase state, purchase token and an app-generated opaque account identifier. Iris does not receive your payment-card details, Google password or email address from this billing integration.
When you request sync purchase verification, Iris sends the purchase token and signed library identity to the hosted service. The service verifies it directly with Google, acknowledges a completed purchase, and stores its hashed purchase reference, plan, verified state, verification and payment-pause timestamps, and an encrypted copy of the purchase token. A runtime-only encryption key protects that token so scheduled checks can follow renewals, cancellations and payment recovery without your phone remaining open. Plain purchase tokens are not stored or logged. Production service metadata and encrypted library data use Cloudflare D1 and R2 resources in the EU jurisdiction. This constrains storage of those resources; it does not confine Workers request handling or operational logs to the EU. The separate staging resources used for owner tests have only a Western Europe location hint, which is best-effort placement, not an EU residency guarantee; the runtime-only encryption key is not a library decryption key. These checks support the subscription and prevent purchase reuse.
Verification and retention continue on the service after the sync page closes. Closing it does not cancel Google Play renewal or delete the existing cloud copy. You can request cloud-copy and service-record deletion on the sync page, and cancel renewal separately in Google Play. After a confirmed payment pause, downloads are retained for 30 days before scheduled cloud deletion. A verification failure alone starts no deletion timer. Local libraries and backups are unaffected. The service can see ordinary network-request information such as IP address, time and User-Agent; Cloudflare may process operational and security logs under its privacy policy. Iris does not add purchase tokens, signing keys or library contents to application logs.
When enabled, hosted sync runs in the background as well as through Sync now. Local copies remain available if the service is unavailable. Pausing sync does not cancel your subscription; deleting the cloud copy does not delete local originals. Details of the app, its paid features and what happens if hosted sync shuts down are in the terms of use.
Files, camera, sharing and backups
Android’s picker or share sheet grants access to the files you choose. Iris does not ask for broad access to your photos or storage. Taking a reference photo uses your chosen camera app. QR pairing requests camera access only when you choose to scan another device’s pairing code. QR decoding runs on your device; camera frames are neither stored nor uploaded. Iris does not request microphone access. It checks for supported drawing apps locally so you can send a picture to one. Sending a reference grants the chosen app access to that exported picture; the receiving app then handles it under its own policy.
A manual backup contains your library metadata and originals. You choose its destination with Android’s file picker; a cloud-backed destination may upload it through that storage provider. Backup files are not encrypted by Iris. Keep them somewhere you trust. Iris disables Android’s automatic app backup and keeps library files in private storage excluded from that backup. Device manufacturers may handle device-to-device transfers differently.
Permissions
Internet access enables capture and Explore. Network-state access lets capture wait for a suitable connection, such as Wi-Fi. The boot-completed permission lets Android reschedule unfinished imports and captures after a reboot. These permissions do not grant access to your location, contacts or personal accounts. Optional camera permission is used only by the QR scanner. Temporary file grants cover only files you select or send.
Feedback and privacy requests
Settings → Send feedback opens a draft in your email app addressed to lars@gjessing.io. The draft includes the Iris version and Android version, with space for your message. It attaches no library records or pictures and sends nothing automatically. You decide what to include and whether to send it.
If you send an email, we receive your sender address, any sender name, message and anything you choose to attach. We use it to answer you and investigate your request. Do not email recovery codes, signing keys or purchase tokens.
Purposes and legal bases
- Hosted sync, library identity, quota accounting and subscription verification are processed to perform the service contract you request (GDPR Article 6(1)(b)). Keys, identifiers and purchase verification are necessary to provide encrypted sync; you can use the local library without providing them, but cannot use hosted sync without them.
- Request security, replay prevention, service error logs and purchase-reuse prevention rely on legitimate interests in protecting the service and its users against abuse and fraud (Article 6(1)(f)). We minimise those records and do not use them for advertising.
- Support correspondence relies on our legitimate interest in answering questions and resolving problems (Article 6(1)(f)); service-contract requests may also be necessary to perform that contract.
Recipients and international processing
Cloudflare, Inc. processes hosted service data and website requests on our behalf as our infrastructure processor. Its published processor terms are in the Data Processing Addendum. Cloudflare is a US company. Its global edge network handles requests, and operational and security metadata may be processed outside the EEA even when production D1 and R2 storage uses the EU jurisdiction. Cloudflare’s DPA provides the EU–US Data Privacy Framework for covered US transfers and Standard Contractual Clauses where applicable; it also lists its subprocessors. You may request information about the applicable safeguards using our contact.
Google is an independent controller for Google Play accounts, payments and store records, under Google’s privacy policy. Iris sends sync purchase tokens to Google for verification through Cloudflare; it receives no card details. Source websites, museum services and apps you choose for sharing, backup or email operate under their own policies as described above. Support email is processed by mailbox.org (Heinlein Hosting GmbH, Germany) as our processor for support correspondence, using German data centres. See its data protection information. Email delivery can also involve the sender’s chosen provider outside the EEA.
Retention and deletion
Your on-device library remains until you delete its contents, replace it through a confirmed restore, clear app storage or uninstall Iris. Local cleanup can retain temporary files or recovery copies until it is safe to remove them. Clearing app storage or uninstalling removes Iris’s private local data; export a backup first if you want to keep it. Copies you exported, backups saved elsewhere, and pictures sent to other apps must be deleted separately. I cannot access or remotely delete your device library or a source provider’s logs.
- Encrypted originals, metadata and sync history, the public library key, byte counts and subscription records remain while the cloud library is in use. Cancellation retains them through the paid period. A confirmed payment hold or expiry starts the 30-day recovery period described above; store outages can postpone deletion, never bring it forward. Explicit cloud deletion is available without waiting for payment expiry.
- Historical hashed purchase references prevent another library reusing a purchase while this cloud library exists. They are deleted with its service records, including encrypted receipts, when cloud deletion finishes; they are not kept indefinitely after deletion.
- Replay-prevention nonces expire after ten minutes and are removed on a later authenticated request or with cloud deletion. Abandoned uploads become eligible for cleanup after 24 hours; incomplete multipart uploads have a one-day abort rule. Bounded scheduled cleanup can take several passes.
- The app no longer sends diagnostic reports. Reports from earlier test builds are removed by scheduled cleanup at most seven days after their upload, and updating the app deletes their local diagnostic files.
- Cloudflare Workers observability logs retain request and error metadata for up to seven days. We do not export them to a separate log archive. Other Cloudflare security records follow its own published retention policy.
- D1 Time Travel can restore deleted service rows for up to 30 days. Live deletion is not complete removal from recoverable database history until that window has passed. A disaster restore must reapply deletion requests before the service resumes.
- Support correspondence is deleted within 12 months after the request is resolved, unless a specific legal obligation or dispute requires longer retention; in that case it is kept only for that obligation or dispute.
Your privacy rights
You may request access, rectification, erasure, restriction of processing and portability, object to processing based on legitimate interests. We respond without undue delay and normally within one month. If a complex request needs an extension permitted by law, we explain why within that first month. Contact us at the address above. You may complain to your supervisory authority, including Datatilsynet in Norway.
Because there is no Iris account, a cloud-library request needs proof that you control its signing key. In Cloud sync → Cloud data & devices → Privacy request, create a signed request and send that text with your email. We verify it against the library’s registered public key. It contains no recovery code or private key. Never send either of those to us. Manual library export provides your local originals and metadata; the service cannot decrypt a cloud library for you. We cannot access or erase other providers’ independent records.
Iris performs no automated decision-making with legal or similarly significant effects and does not profile you.
This policy page and changes
Opening this policy contacts gjessing.io and its hosting/network providers, which receive ordinary web-request information such as your IP address and browser User-Agent. This page has no scripts, cookies, analytics or external fonts. It does not send your Iris library. External links open services with their own privacy practices.
Changes will be published here with an updated date. New data flows will need an updated policy and Play disclosures before they ship.