Lenticular Privacy Policy

1. Who we are

Lenticular is made by MavenWright Studio ("we", "us"), Istanbul, Türkiye. We are the data controller for the personal data described here. Contact: [email protected].

2. What stays on your device

You can use Lenticular without an account. Your cards, their photos and depth maps, your lens profiles and your printer settings are then stored only on your device. Your photos, depth maps and print files are not sent to us unless you send something to the assistant (section 5). The error reports and usage statistics of section 7 describe how the app is used and what went wrong (for example a card's kind, the paper size or how many photos were added), and Clarity's recordings show the app's screens as you see them, your settings and the printer you chose included, with your photos, card names and lens profile names hidden. You can turn these off in Settings.

3D from a single photo is worked out on your device by an AI model that comes with the app. Your photos are not sent anywhere for it. The engine that runs the model (Microsoft's ONNX Runtime) can send usage statistics of its own to Microsoft; Lenticular switches that off.

When you print a card or share a preview, the file goes only where you send it: to your printer, or to the app you choose.

3. Signing in with Google or Apple

Signing in is optional. It lets you sync your cards between your devices and use your Plus or Pro plan on all of them. You sign in with Google or Apple; Lenticular has no passwords of its own.

Google or Apple tells us your email address, that it has confirmed that address, and an identifier for your account with them. With Apple this can be the relay address Apple gives you when you choose to hide your own. We ask for nothing else (no name, contacts or profile) and never see your Google or Apple password.

For your account we keep:

• an account id: a random identifier for your account;
• the email address and the Google or Apple identifier described above;
• the sign-in tokens that keep the app signed in, stored only as one-way hashes;
• if you sign in with Apple, a token Apple gives us, kept only so that we can revoke Lenticular's access at Apple when you delete the account;
• your plan (Free, Plus or Pro), where it came from and when it ends.

Like any server, ours sees the IP address of the device that connects to it. We use it to limit how many requests can come from one address and to keep the service safe.

4. Cloud sync

When you are signed in, Lenticular keeps a copy of the following on our servers and syncs it to your other signed-in devices. Cloud sync is part of every plan, Free included.

• your cards: each card's settings and layout, and its photos, depth maps and edit files;
• your lens profiles;
• the printer you chose and the lens you use with it.

Your theme, your language and the other preferences of each device are not synced, and neither are cards that have no photo yet.

Card records and settings are kept in our database. Photos and the other files of your cards are stored in Cloudflare R2, Cloudflare's storage service, in a space of your account's own; files are never shared between accounts. Cloudflare keeps them encrypted on its disks. They are not end-to-end encrypted: our server can read them, as it must to send them to your devices. We use your cards only to store and sync them for you.

When you delete a card, it moves to Recently deleted, where you can restore it for 30 days or delete it for good straight away. After 30 days it is deleted for good. When a card is deleted for good, its photos and files are removed from storage about a week later, unless another of your cards uses the same file. Deleting a lens profile is final at once. A small marker with no content (the card's id and when it was deleted) stays, so that a device that was offline also learns about the deletion.

5. The assistant

Lenticular has an assistant you can chat with: through the app it can make your cards, change them and get them ready to print. Nothing is sent to it until you agree, on the screen shown before your first message. When you send it a message, the following goes to our server and from there to OpenAI's API, which writes the answer:

• your message and the earlier messages of that conversation;
• a summary of the app and the open card: the screen you are on, your plan, your paper size and the app's language, your lens and printer settings, and the card's kind, size, number of photos and settings;
• photos you attach to a message, as a copy whose long side is at most 768 pixels;
• a small picture of the card, only when the assistant asks to look at it.

Your original photos, depth maps and print files are not sent.

You can send your first 5 messages without signing in. For them the app makes a random install id the first time it opens and sends it with your messages, so that our server can count them. The IP address your messages come from is also counted, in memory only, to limit how many messages one address can send in a day. After 5 messages the assistant asks you to sign in with Google or Apple.

Your conversations: when you are signed in, your conversations and the photos you attached are kept in your account and synced to your other signed-in devices, like your cards (section 4), so that you can carry on a conversation on another device. Without an account they stay on your device, and they are uploaded to your account when you sign in. Deleting a conversation is final at once; its attachments are removed from storage about a week later.

The product log: to find and fix the assistant's mistakes, our server keeps a log of each message for 90 days: what you wrote, the app summary, the attached photos as they were sent, what the assistant answered, which app actions it asked for and how they ended, and the app's version and language. We use it only to improve Lenticular. You can turn it off on the permission screen; your messages are then not kept in it. Messages sent before you signed in are logged under the install id, not under your account.

For costs and limits our server also keeps counts, with no words in them: how many messages you sent each day, how many model calls and tokens each one used, and which app actions were used and how they ended.

OpenAI processes the request for us under its API terms. At the time of writing, OpenAI does not use API data to train its models, and keeps requests and answers for up to 30 days to detect abuse, longer only where the law requires it.

6. Purchases

On iPhone, iPad, Mac and Android, payments are handled by Apple or Google. RevenueCat, Inc. tells the app and us which Plus or Pro subscription is active; it receives an app user id (a random id, or your Lenticular account id once you sign in) and the store's purchase history. We never see your card details.

7. Error reports, usage statistics and ad measurement

Lenticular shows no ads. To find bugs and see where the app is hard to use, it sends error reports and usage statistics to the three services below. Your photos, depth maps, print files, card names and lens profile names are never sent to them, and the app removes the file paths and file names it finds in error messages before sending them. The app does not use location services; the approximate locations below come from the IP address.

• Sentry (Functional Software, Inc.) receives crash and error reports and a log of the app's main steps (for example: a card was created, a print file was made, or it failed and why), with the device's model and system version, the connection type, the app's version and language, your plan, a random install id and, once you are signed in, your account id.
• Microsoft Clarity records how the app's screens are used (taps, scrolls and which screens are opened) as a replay, so that we can see where people get stuck. Your photos, card names and lens profile names are hidden in the recordings and are not sent to Clarity. Clarity receives the same random install id and, once you are signed in, your account id, with your plan, the app's language and version and the kind of device (for example an iPhone or a Mac), and works out an approximate location (country or region) from the IP address.
• Google Analytics for Firebase (Google LLC) receives which screens you open, the app's main steps and your purchases (product, price and currency), with the device's model and system version, the app's version and language, your plan, an identifier Firebase makes for the app on your device, an approximate location (country, region and city) that Google works out from the IP address after shortening it and, once you are signed in, your account id.

Ad measurement: we advertise Lenticular with Google Ads and want to know whether those ads bring people to the app and lead to purchases. So Google Analytics for Firebase also lets Google Ads count the installs and purchases that follow one of our ads. On Android this uses your device's advertising ID, which you can reset or delete in your device's settings. On iPhone and iPad, Lenticular asks once, with the system's tracking prompt, whether it may use your device's advertising identifier; if you do not allow it, the identifier is not used. The Mac app never asks and does not use it.

If your device's region is set to a country of the European Economic Area, the United Kingdom or Switzerland, Lenticular tells Google not to use your data for advertising (the ad storage, ad user data and ad personalization signals are off): our ads are not measured with your data, and the usage statistics are still sent. Elsewhere these signals are on, and Google may also use the data as described in “How Google uses information from sites or apps that use our services”: https://policies.google.com/technologies/partner-sites.

All of this is on from the first start. You can turn it off in Settings → Share usage and diagnostics: the app then stops sending to Sentry, Clarity and Google Analytics, crash reports included, at the latest from its next start. What was collected shortly before you turn it off may still be sent shortly after, because the app sends in batches, and what it kept while your device was offline goes once it is back online. What was already sent is deleted when its period in section 10 ends. This setting does not change the assistant's product log, which you turn off on the assistant's permission screen (section 5).

We do not sell your data.

The mavenwright.com website has its own privacy policy: https://mavenwright.com/en/legal/privacy.

8. Where your data is kept, and who processes it for us

Our servers are in the European Union (France). If you live in Türkiye, using Lenticular's account, cloud sync and assistant means your data is transferred to and stored outside Türkiye, and reaches the processors below, some of which are in the United States. What you send to the assistant goes from our server in the EU to OpenAI in the United States. The error reports and usage statistics of section 7 are transferred too: they go from the app straight to Sentry, Microsoft and Google in the United States.

• Hostinger International Ltd.: our servers (EU)
• Cloudflare, Inc.: network protection and delivery, and storage of your cards' photos and files and your conversations' attachments (Cloudflare R2)
• Google LLC: Sign in with Google, if you choose it; Google Analytics for Firebase and Google Ads measurement (USA)
• Apple Inc.: Sign in with Apple, if you choose it
• OpenAI, L.L.C.: the OpenAI API for the assistant
• RevenueCat, Inc.: App Store and Google Play purchases and subscriptions
• Functional Software, Inc. (Sentry): crash and error reports and the log of the app's steps (USA)
• Microsoft Corporation (Clarity): recordings of how the app's screens are used (USA)

9. Why we may use it (GDPR Art. 6 / KVKK Art. 5)

• To provide what you ask for (your account, cloud sync, your assistant conversations and your plan on all your devices, purchases): performance of a contract.
• Sending your messages, the app summary and the photos you attach to OpenAI for the assistant: your consent, asked before your first message.
• The assistant's product log: our legitimate interest in finding and fixing its mistakes; you can turn it off.
• Limiting requests and messages (counting messages sent without an account by the install id included) and keeping the service secure: our legitimate interest in a service that works and is safe.
• Error reports, the log of the app's steps, screen recordings and usage statistics (Sentry, Clarity, Google Analytics for Firebase): our legitimate interest in an app that works and is easy to use; you can turn them off in Settings.
• Ad measurement (section 7): on iPhone and iPad, your device's advertising identifier is used only with your consent, given in the system's tracking prompt. Otherwise, our legitimate interest in knowing whether our ads work; you can turn it off in Settings. On devices whose region is in the European Economic Area, the United Kingdom or Switzerland, your data is not used for ads.
• Purchase records: our legal obligations (tax and accounting).

10. How long we keep it

• Account data and synced cards, lens profiles and settings: while the account exists; all of it is deleted when you delete the account.
• Deleted cards: 30 days in Recently deleted, then deleted for good; their files are removed from storage about a week after that. Deleted lens profiles: at once.
• Assistant conversations and their attachments: until you delete them or the account; a deleted conversation's attachments are removed from storage about a week later.
• The assistant's product log: 90 days; what is logged under your account is deleted at once when you delete the account.
• Assistant usage counts (no words): while the account exists.
• The install id and how many messages it sent without an account: kept, so that the 5 messages without signing in are counted once.
• Sign-in tokens: they expire after at most 30 days unless the app renews them, and are deleted with the account.
• Sentry: crash and error reports at most 90 days, the log of the app's steps 30 days.
• Microsoft Clarity: screen recordings 30 days, or up to 9 months for a recording we mark to study; usage figures and heatmaps 9 months.
• Google Analytics for Firebase: event data 2 months; after that only reports that add many users together remain.
• Purchase records: as long as tax law requires.

11. Your rights (GDPR / KVKK Art. 11)

You can ask what we hold about you and have it corrected, deleted or sent to you, and object to processing. Write to [email protected]; we answer within 30 days. You can also complain to your data protection authority (in Türkiye, the KVK Kurumu at kvkk.gov.tr).

13. Children

Lenticular is not directed at children under 13, and we do not knowingly collect their data.

14. Changes

We post changes to this policy here and update the date at the top.