RetroLens Privacy Policy
Effective: June 1, 2026 · Updated: October 17, 2026
Banana Apps LLC ("Banana Apps," "we," "us," or "our") operates RetroLens. This Privacy Policy explains what personal information we handle, why we use it, who can receive it, how retention and deletion work, and the choices and rights available to you. It covers RetroLens and related support, and describes this website's practices below.
How to read this policy
Personal information means information that identifies you, relates to you, or can reasonably be linked to you. The information involved depends on which features you use. Taking or importing a photo is different from saving a cloud memory, posting to friends, or asking for an AI edit. Each choice can involve a different audience and different processing.
We receive information directly from you, automatically when our services handle your requests, and from people or services you interact with. For example, a sign-in provider supplies account information, a store confirms a purchase, and another user may send you a message or friend request. We use this information for the purposes described here rather than treating all features as having the same data needs.
A category in this policy does not mean every item in that category is collected from every person. For example, someone who does not submit an AI request does not provide an AI source photo through that feature. Optional information can still be personal information when you choose to provide it. Read the relevant information, audience, retention, and choice sections together to understand the consequences of a particular action.
Account and profile information
When you create or use an account, we process account identifiers, your email address, sign-in information, and profile details you provide, such as a name, username, biography, or avatar. Apple, Google, or another available sign-in method may supply basic identity details according to the method you choose. We also maintain information needed to keep you signed in and associate your content and purchases with the appropriate account.
RetroLens also stores information on your device, including sign-in information, preferences, and local photo records used to restore your experience between launches. App-held information is distinct from photos you export to your device's photo library. Keeping information locally does not mean a cloud-backed memory or shared post exists only on that device. Account controls, device settings, and separately exported copies can therefore require different actions.
Your profile can be found by other signed-in RetroLens users through in-app search. Profile information and activity-derived statistics can therefore be visible outside your accepted friends. Avoid putting information in your profile that you do not want other app users to see. An email address used for sign-in is handled as account information; it is not permission for unrelated use of your private content.
Account information supports sign-in, account recovery, ownership checks, and association of content with the right person. Profile information supports discovery and the identity people see when you interact. You can use available profile-editing controls to change details. A change in RetroLens does not necessarily change the details held independently by Apple, Google, or an email provider; those accounts have their own controls and correction processes.
Changing a current profile detail is different from changing an independent record of an earlier interaction. A recipient may already have a screenshot showing a previous name or avatar, and a store may need to keep the original transaction details. If a concern involves one of those records, identify it in your request so the current profile and the separate record can be considered appropriately.
Information visible on a device can come from different places. Signing in to the correct account can provide access to its available cloud-backed content, while a photo kept only on a previous device depends on that device or a separate copy you retained. A local record or preview does not establish that every original image is stored in your cloud account. If a request concerns a missing photo, describe whether you had kept it locally, saved a private memory, posted it, or exported it, to the extent you know.
Purchases and service records
App stores and purchase-support services provide transaction references, subscription and entitlement status, restore results, and information needed to validate purchases and manage access. We maintain AI credit balances and records of credits granted or used. These records help us deliver paid benefits, investigate errors, prevent misuse, and meet transaction-related obligations.
The store processes your payment information under its own terms and policy. We do not receive your full payment card details. Paywall and purchase services can receive account or device identifiers, purchase events, and information about the offer or purchase flow. This is separate from the photos, notes, or messages you choose to store or share in RetroLens.
When our services handle requests, technical and operational information can include network and device details, request times, errors, and records needed to secure and troubleshoot accounts, uploads, AI, and billing. Collection varies with the service and app version. App and service diagnostics, where collected, can include account identifiers and error context. The services supporting accounts, content, and purchases also maintain operational records. We receive the information you include when you contact support, such as your email address, message, and attachments.
Transaction information is used to determine which paid benefits belong to the account and resolve purchase or credit discrepancies. It is not a substitute for the store's full payment record. If you ask for purchase support, provide only the relevant product, date, account, and receipt reference, and remove unrelated information from attachments. Technical records help distinguish a billing issue from a sign-in, upload, or processing failure without requiring your entire photo library or private conversations.
Records can describe different stages of the same issue. A store receipt confirms a transaction, an entitlement record concerns access, and a support conversation explains the problem reported. Canceling renewal does not necessarily erase those records, and correcting access does not alter an independent store receipt. If you question a record's accuracy, identify which stage or record concerns you rather than assuming that all purchase-related information is held in one place.
Why we use personal information
We use the information relevant to each purpose to:
- Create and secure accounts, maintain sessions, and provide profile and account controls.
- Save, organize, display, and deliver the photos, memories, messages, and social features you choose to use.
- Carry out a requested AI edit, return results, and manage related usage and credits.
- Confirm purchases, restore supported benefits, manage access, and investigate billing issues.
- Respond to support and privacy requests, investigate reports and abuse, and protect users and the service.
- Identify and fix operational problems, meet legal duties, and resolve disputes.
Some information is necessary for a feature to work. You can choose not to provide optional information or use optional features, but a feature that depends on an account, photo upload, purchase confirmation, or AI submission may then be unavailable. We do not use your private photos in advertising or marketing without your permission.
The same information can support more than one relevant purpose. An account identifier can connect your content to your account and help investigate an access problem; a transaction reference can support both delivery of a benefit and a later dispute. Those connections do not turn private content into advertising material. Ask us if you need to understand a particular use, its purpose, or the choices that apply to it.
Information needed for a particular transaction is different from optional content you choose to add. For example, the selected sign-in method needs its required account information, a cloud memory needs the image you ask us to store, and a purchase investigation may need a relevant transaction reference. If you decline information necessary for that action, we may be unable to complete the action or establish the related benefit. This does not require you to provide unrelated personal content. You can describe a concern first and ask which details are relevant before sending an attachment.
Who can see your content
RetroLens does not offer a public photo feed. Your Circle is your set of accepted friends. Circle posts and direct messages are intended for accepted friends, while private cloud memories are available through your own account. Signed-in users can discover profiles, and members of an existing shared collection can continue to see the content available to that collection.
There are important limits. Avatars and some older media use public links; a person who has a link may be able to open the image outside the normal in-app audience. Temporary media links can remain usable until they expire, and already downloaded or cached copies may remain after an access change. Removing a friend or blocking an account does not recall content they already received.
Recipients can take screenshots, save content, or share it elsewhere. Messages are stored as account-linked content and are not represented as end-to-end encrypted. Our service providers process content as needed to provide the service; privacy settings govern the intended user audience, not a guarantee that no service processing occurs. Choose your audience and what you upload with these limits in mind.
Your choice to save something privately, post it, or send a message determines how that particular copy is used. Posting a copy of a private memory does not make every memory in your account part of the post. However, people may infer personal details from what you share, and we cannot prevent a recipient from recognizing a location or person in an image. Removing information later cannot make a recipient forget something already seen.
People depicted or discussed in content can have their own rights even when they are not the account holder or intended recipient. A limited audience does not remove those rights. If content involves your image or personal information and you need assistance, describe the relevant account or content and your connection to it. We must consider account security and the privacy of other people when evaluating that request.
Your current friendships can affect the audience for earlier Circle posts. A person you newly accept as a friend can become able to view posts you shared before that friendship began, as well as later posts that are available to friends. Consider existing posts when accepting a request or changing a friendship. The date an image was taken or posted does not necessarily fix its audience permanently.
Removing a friendship or blocking an account can restrict access to an existing direct-message conversation without deleting the underlying conversation records. Being unable to open an older thread therefore does not establish that its contents have been erased. To address retained records, use account deletion or make a specific privacy request as appropriate. Independent copies already obtained by either participant remain subject to the separate limits explained here.
Optional AI and photo processing
G7X AI Look operates when you select or capture a photo and request an AI edit. The selected image and editing instructions are shared with OpenAI, the AI provider, to produce the result. Ordinary camera use does not by itself request an AI edit. Photos can include faces and other personal or sensitive details, so only submit images you have the right to provide for this processing.
We process the submitted image, returned result, and related processing and credit records to deliver the edit, display or recover a result, and manage usage. Saving or posting a result creates content subject to the relevant device, memory, or sharing rules. Closing the AI screen or choosing not to make further requests cannot recall information already sent to the provider.
OpenAI states that information sent through its API is not used to train its models by default. Its security, abuse-prevention, and legal retention rules can still apply. See OpenAI's data controls. We do not promise zero provider retention or that deleting an image from RetroLens instantly removes every provider record. Banana Apps does not use your private photos to train its own public AI models.
An AI edit can change or misrepresent details in a photo. Review results before saving or sharing them. You can avoid further AI processing by not submitting another image. Requests concerning earlier submissions can be made by emailing us and remain subject to applicable law and the provider's processing obligations.
Choosing an image for one AI request does not request AI analysis of your whole photo library. The submitted photo can still contain information that is not necessary for the look you want, so review it before submitting. You can choose a different image or avoid the feature. If you save an AI result to a memory, your device, or a post, those retained copies have their own controls; discarding one result or stopping further AI use does not automatically delete every copy you chose to keep.
Requesting an edit involves the submitted image, not merely the result you later decide to save. Choosing not to keep the output therefore does not undo the earlier processing. Settings in a separate personal AI account do not necessarily control processing requested through RetroLens. The provider's applicable terms and the rights described here remain relevant, including where a provider must retain limited information for safety or legal reasons.
Service providers and other disclosures
We use service providers for account authentication, hosting and storage, communications, purchases and paywalls, AI processing, and service security and reliability. They receive information relevant to their role. For example, an authentication provider handles sign-in information, a storage provider holds uploaded content, and a purchase provider handles purchase context. Providers processing information on our behalf must provide equivalent privacy protection.
Information is also disclosed to the people you choose to interact with, according to the sharing rules described above, or to an external destination you choose when exporting or sharing. Services such as Apple, Google, app stores, and external sharing destinations may separately process information under their own policies. Review those policies when deciding whether to use their services.
We may disclose information when required by law or valid legal process, to address fraud or security threats, to protect people or legal rights, or in connection with a business transfer such as a merger or sale, subject to applicable protections. These circumstances do not mean your private content is routinely made public. We do not sell personal information or share it for cross-context behavioral advertising.
The reason for a disclosure determines the information needed. Delivering a message involves its intended participants; verifying a purchase involves purchase and account context; responding to a lawful request may involve records relevant to that request. This policy describes recipient categories so you can understand those roles. It does not mean every provider receives every category of personal information or that the people viewing a post receive your sign-in credentials or payment details.
A provider can process some information for us and hold other information under its own relationship with you, such as a store's payment account. Those roles can lead to different retention and request procedures. A lawful business transfer likewise does not eliminate existing privacy rights or, by itself, supply a consent required for an unrelated new use. Any disclosure remains subject to the purpose and protections that apply to it.
Device permissions and everyday choices
Camera and photo-library permissions support taking, importing, and saving photos. Contacts access is optional and helps you select people to invite. Contact names, phone numbers, and address-book information are handled locally for this purpose rather than uploaded to RetroLens. Local invitation state or limited action counts can still be used to support the invitation experience. When you choose to send an invitation through another app, that app handles the communication under its own rules.
You can manage permissions in your device settings and use the app's available profile, friend, block, and content controls. Revoking a device permission stops access governed by that permission; it does not erase content already uploaded or cancel an earlier transmission. Device copies, cloud content, purchases, and account deletion therefore require their respective controls.
Permission choices can have practical consequences. Without camera access you may be unable to take a photo in the app; without the relevant photo access, import or saving may not work. Declining contacts access does not itself delete friendships or prevent use of other available invitation methods. Giving photo access is not a choice to publish an entire library. The upload, AI, and sharing actions you choose remain separate from the operating system's permission to access a device feature.
Phone notification delivery is currently disabled, although permission and Settings screens may remain available. In-app Inbox and activity records are separate and can still be created. Historical notification-related records may remain until cleanup or account deletion. A device's permission status alone does not mean that phone alerts are being sent.
Device permissions usually apply to the particular device and operating-system setting involved. If you use more than one device, review the relevant settings on each. Your account's stored content and existing sharing relationships have their own lifecycle and controls. A permission change on one device should not be treated as proof that uploaded information, another device's copies, or previously shared material has been removed.
How long information is retained
We retain information for as long as reasonably needed for the purposes described in this policy, including providing the service, preserving the content you keep in your account, managing purchases and credits, preventing misuse, handling disputes, and meeting legal obligations. Different categories can have different lifecycles; there is no single retention period for every account record, image, transaction, support message, or security log.
Retention depends on the type and sensitivity of the information, whether your account or content remains active, the purpose it serves, and applicable legal requirements. Temporary uploads and AI results can require cleanup, and records of an AI request or credit use may have a different lifecycle from the image itself. Deletion and cleanup can take time and can require retries. We do not promise immediate erasure from every system.
- Account and profile records: maintained to support the account and its identity, with deletion subject to ownership verification and any lawful need for limited continuing records.
- Photos, memories, and social content: retained to provide the storage or sharing feature you chose, until removed through the relevant controls or account deletion, subject to cleanup and recipient-copy limits.
- AI information: submitted images, results, and processing records can have different lifecycles. A result saved as a post or memory follows that feature's lifecycle as well as the limits on earlier provider processing.
- Purchase and credit records: kept as needed to manage benefits, resolve transactions, address misuse, and meet applicable recordkeeping obligations. Stores may retain independent payment records.
- Support, safety, and technical records: retained according to the issue involved, investigation or troubleshooting needs, and applicable legal or dispute requirements, rather than necessarily disappearing when a photo is removed.
Limited information can remain in backups, transaction or legal records, security records, or service-provider systems where needed or permitted by law. Copies saved by recipients or exported to other services are outside our account-deletion controls. We do not represent that ending an account removes every trace of earlier processing or overrides another party's independent legal duties.
Simply stopping use does not serve as an instruction to delete your information. If you no longer want an account or particular content retained for its normal service purpose, use the relevant controls or make a request. You can ask about the category and reason for information that remains. We assess that question against the applicable purpose and legal requirements rather than assuming that every retained record must have the same deletion date.
A continuing retention reason must relate to the information and purpose involved. For example, keeping a transaction record to meet a legal obligation does not by itself justify keeping every private photo associated with the same account. Likewise, a record needed to investigate a particular report can have a different purpose from displaying the reported content to other users. When an exception applies to some information, a request concerning the remaining information still needs to be assessed under the applicable law.
Account deletion and its effects
You can request deletion in RetroLens Settings or by emailing us. We may verify account ownership before acting. Account deletion removes linked account records and media, including profiles, posts, private memories, and associated activity, subject to the retention limits above. Uninstalling the app or signing out does not submit a deletion request and does not remove your cloud account.
Available content controls can address a particular post, your own comment, or a private memory without closing your entire account. Use the control that matches the information you want removed. Removing one item does not itself request deletion of your profile, other content, or purchase records. If the same image was separately retained or shared elsewhere, identify those copies when making a request rather than assuming one action removes every instance.
Deleting your own post can also remove comments, reactions, and saved references attached to that post. This can affect other people's interactions with it as well as the photo itself. Removing your saved reference to someone else's post has a narrower effect because the original belongs to that person's account. A separate private memory or exported image is a separate copy even where it depicts the same scene; identify the relevant feature and copy when seeking help with removal.
Deleting an account removes whole direct-message conversations involving that account, including messages sent by other participants in those conversations. It also removes shared collections the account owns and can affect other members' access to those collections. Other people may still have screenshots, downloads, exports, or other independent copies. Save anything you need before requesting deletion.
Account deletion does not cancel a store subscription. Manage cancellation through the store separately. Unused AI credits may be forfeited, subject to applicable law, and the store or purchase provider may retain transaction information under its own obligations. If deletion fails or you remain concerned about retained information, email us so we can address the request rather than assuming that uninstalling completed it.
You do not have to request closure of your whole account to ask a privacy question or exercise a right concerning particular information. Tell us if your request concerns a specific record, content item, or earlier disclosure. Some information relates to more than one person, and we must consider their rights too. Removing your account from our services does not give us control of another person's device, email account, photo library, or independent online post.
Submitting a request and completing deletion are different stages. If the app reports an error, you cannot access the relevant account, or the outcome is unclear, contact us with the account and request details. Avoid creating new accounts or sending additional private content merely to demonstrate the issue. Where some information must lawfully remain, the deletion request still needs to be considered for the information to which the right applies.
Your privacy rights and requests
Depending on where you live and which laws apply, you may have rights to know about or access your personal information, obtain a copy in a portable format, correct inaccurate information, request deletion, restrict processing, or object to certain uses. Where processing relies on consent, you may withdraw that consent for future processing. Withdrawal does not make earlier lawful processing unlawful, and some information may still be needed for another lawful purpose.
- Access and information: you may be able to ask whether we hold personal information about you, obtain a copy, and understand its sources, uses, recipients, and retention. A copy may need to protect other people's information, confidential material, or security information that the law permits us to withhold.
- Correction: identify the information you believe is inaccurate or incomplete and explain the correction requested. You can also use available profile controls. Correcting a current detail may not require erasing an accurate historical transaction or a record that a change occurred.
- Deletion: you may request removal of information where the right applies. Account deletion has the effects explained above. Legal recordkeeping, security, dispute requirements, or another person's rights may justify retaining some information; a deletion request does not automatically override those exceptions.
- Portability: where the right applies, you may request eligible information in a structured, commonly used, machine-readable form. The right's scope depends on the applicable law and processing involved; it does not mean every internal record must be transferred or that another app can import your account, friendships, or content.
- Restriction, objection, and withdrawal: you may be able to ask us to limit a disputed use, object to processing based on legitimate interests, or withdraw consent. Explain the use involved and your request. A restriction may limit use while some information remains stored, and a right to object is subject to the conditions and exceptions of applicable law.
Access can concern information about you that another person supplied, including relevant information in shared interactions. It does not give you general access to that person's account or unrelated private conversations. Where records concern several people, we consider what can lawfully be provided, including whether other people's details can be protected while supplying your information. The presence of another person's information is not, by itself, a reason to refuse all relevant information. Describe your connection to the record so we can identify the personal information and rights involved.
Under the GDPR, portability is a narrower right than access: it concerns eligible personal information you provided where processing is automated and based on your consent or a contract. Depending on the circumstances, information provided can include information observed through your use, alongside details you actively supplied. It does not automatically include every assessment or inference created about that information. You can request direct transmission to another controller where technically feasible. Portability must respect other people's rights and does not itself delete the information remaining with us.
Where the GDPR right to restriction applies, you can seek limited use while an accuracy dispute or an objection is assessed. It can also apply where processing is unlawful and you prefer restriction to erasure, or where we no longer need information but you need it for a legal claim. Restricted information may remain stored, with further use limited to consent or another exception the law permits, such as legal claims or protecting another person's rights. Where required, we inform you before lifting the restriction. Explain which information and use you want restricted; a request to preserve a disputed record can have a different purpose from a request to delete it.
For a GDPR objection to processing based on legitimate interests, explain how your particular situation relates to the use you challenge. We must stop that processing unless we demonstrate compelling legitimate grounds that override your interests, rights, and freedoms, or the processing is needed for legal claims. The rules for direct marketing are different: where information is processed for that purpose, an objection requires that use to stop, including related profiling.
Email us to exercise a right, ask about a request, or appeal a refusal where an appeal is available. Tell us what you are requesting and enough account information to locate the relevant records. Do not send your password, payment card details, or unnecessary identity documents. We may ask for proportionate information to verify your identity and, where relevant, an authorized representative's authority before disclosing or changing account information.
If someone acts for you, we may need evidence that you authorized them and may need to confirm the request with you, to the extent permitted by law. Merely knowing a username or possessing a photo does not establish authority to obtain that account's private records. If you cannot use your usual sign-in, explain that situation so we can consider an appropriate verification method. Do not send an identity document unless we explain why it is needed and how to provide it.
Requests are handled according to applicable deadlines and lawful exceptions. We may need to retain information for a legal obligation or protect another person's privacy, and some requests may affect the features we can provide. Where required, we explain a refusal and available appeal options. We do not unlawfully discriminate against you for exercising a privacy right. You may also complain to the privacy or data-protection regulator responsible for your location.
Where the EU General Data Protection Regulation (GDPR) applies to your request, we respond without undue delay, normally within one month of receipt. When permitted because of the complexity or number of requests, we may extend that period by up to two further months and explain the extension and reasons within the first month. Requests are generally free. A reasonable administrative fee or refusal is allowed only under the law's narrow conditions, such as when we can demonstrate that a request is manifestly unfounded or excessive; we must justify the exception. See the EDPB's guidance on individual rights.
Where applicable law requires, we take the necessary steps with service providers processing information for us and communicate corrections, deletion, or processing restrictions to recipients who received the information. Under the GDPR, recipient notification is subject to the exception for impossibility or disproportionate effort, and you can ask us to identify those recipients. Independent copies and external accounts may limit what we can directly erase, but those limits do not remove applicable duties to notify recipients or act with our service providers.
Access, deletion, or portability rights are not limited to the controls currently built into the app. An email request can address a right even where there is no complete-account export screen. Rights concerning records held independently by a sign-in provider, store, or sharing destination may also need to be exercised with that service.
To appeal or challenge a response, identify the earlier request or response and explain what you believe was missed or decided incorrectly. We assess the request under the law that applies, including any required appeal procedure. A complaint to a regulator remains available where provided by law; contacting us first does not remove that right or require you to accept our explanation.
A clear request can cover more than one right. For example, you can ask to see an account detail, correct it if inaccurate, and understand why a related transaction record remains. Explain the result you want in ordinary language; legal terminology is not required. Applicable law determines the scope, response period, permitted extensions, and any lawful exception. We may seek clarification to identify the relevant information without asking you to restate unrelated parts of the request.
A record's absence from an app screen does not settle whether we still hold personal information about it. A request may concern relevant support, transaction, or retained legal records as well as the content currently displayed. Conversely, access and portability do not generally require recreation of information that is no longer held. If a requested record cannot be found, or only part remains, that circumstance is considered alongside the applicable duty to explain the response; it does not turn a request for existing records into a promise of permanent photo recovery.
Legal bases for processing
Where a legal basis is required, we rely on providing the service you request, consent where required, compliance with legal obligations, and legitimate interests where permitted. Providing an account or requested photo feature can be necessary to perform our agreement with you. Protecting accounts, investigating abuse, and resolving technical or purchase problems can serve legitimate interests, subject to your rights and the protections required by law.
We do not treat agreement to this policy as a substitute for a separate permission or consent that applicable law requires. Optional feature choices and device permissions have the scope explained in the relevant feature and this policy. If you have questions about the basis for a particular use, or wish to object or withdraw consent where available, email us.
A feature choice and a legal basis answer different questions: the choice tells us which service you requested, while the legal basis explains why particular processing is permitted. Withdrawing consent to an optional use does not necessarily require deletion of a transaction needed to meet a legal obligation. Conversely, retaining a transaction does not authorize continued optional use of a photo. We consider the particular information, purpose, and right involved.
Security and international processing
We use safeguards intended to protect personal information, including account and access controls and restrictions appropriate to private content. No storage system, internet transmission, or account is perfectly secure. Protect your sign-in details and devices, and tell us if you suspect unauthorized access. Avoid sending sensitive information in a support message unless it is needed to resolve the issue.
Where applicable law requires notice of a personal-information breach, we will notify affected people and relevant authorities in the manner and within the time the law requires.
Banana Apps is based in the United States. Information can be processed in the United States and other countries where our providers operate, which may have different privacy laws from those where you live. Where applicable law requires protections for an international transfer, the transfer must be subject to the appropriate legal safeguards or another permitted basis. Email us for information about the safeguards relevant to your request. Using the app does not waive rights that apply to international processing.
Content audience controls, account security, and international-transfer protections address different risks. A photo intended for friends still needs service processing and security protections, and those protections do not prevent a friend from independently saving it. If you have a concern about unauthorized access or an international disclosure, identify the issue when contacting us. Do not include a password or additional sensitive material just to establish that a security concern exists.
Children and younger users
RetroLens is intended for people aged 13 and older, or the higher minimum age required where they live. A user below legal adulthood must have parental or guardian permission. G7X AI Look is for ages 17 and older, with parental or guardian permission under 18. Age and parental permission are not independently verified, and an app store rating is not proof that those conditions have been met.
If you believe a child below the applicable minimum has provided personal information, or have a concern about a younger user's account or images, email us with enough detail to investigate. We will address the information and account in accordance with applicable law. Do not send additional images or sensitive details about a child unless needed for the request.
A child may appear in information submitted by an adult even if the child does not have an account. Consider that person's privacy before sharing or requesting an AI edit. A parent or guardian raising a concern can explain their relationship and the information involved, while avoiding unnecessary copies of the child's images. We may need to verify authority before disclosing another person's account information or making an account change.
This website and external links
When you visit getbananaapps.com, the providers that deliver and protect the website and serve its fonts receive information needed to respond to your browser. This includes your IP address, browser and device information, the requested page, and basic request details. We use this information to make the website available, keep it secure, and investigate delivery problems. Those providers may also process request information under their own privacy terms, including when their services are used on other websites.
Essential security cookies may be used to protect the website. We do not use advertising cookies, advertising pixels, or marketing analytics on this site. Browser settings let you restrict cookies and other stored website information, although blocking essential functions may affect access. We do not change website behavior in response to a browser's Do Not Track signal. This does not limit any applicable privacy rights described in this policy.
The company website does not offer an app account or process purchases. Following an app link opens that app's website, policy, or store listing; the relevant service's own terms and privacy practices apply there. When you email us, we receive your email address, message, and any attachments through our email service. We use these to answer your request, provide support, and keep a record of the issue. Please include only information needed for your request.
Links to outside websites do not give us control over their content or data practices. Review the destination's privacy information before providing personal information. The app-specific collection, sharing, retention, and rights described in the other sections of this policy are separate from simply browsing this company website.
These website practices are separate from the photos and other information you provide inside RetroLens. Opening an external link or choosing to contact us brings the relevant browser, destination, or email service into the interaction. Their policies explain information they process independently. You can use browser and device controls for the choices they offer; those controls do not delete your RetroLens account or previously uploaded app content.
You can read these policies without creating a RetroLens account. Sending a support or privacy email is a separate interaction that provides us with the information in that message. A general question usually does not require a photo, receipt, or private conversation. If an attachment is relevant, consider removing unrelated information before sending it. Reading a policy or following a link does not itself submit an account-deletion request.
Policy updates and contact
We may revise this policy when the app, our processing, or applicable requirements change. Revisions are published here. We provide notice of material changes through this website, the app, or email where required, and seek new permission where the law requires it. A revised policy does not by itself authorize a use that requires separate consent.
The dates on this page help identify the version you are reading. A later publication date does not by itself mean every user has provided new consent or that previously retained information can be used for any new purpose. If your question concerns an earlier interaction or policy version, describe that interaction and approximate date so the relevant processing and rights can be considered.
Email us with privacy questions, rights requests, appeals, or concerns about how RetroLens handles information. Banana Apps LLC is located in Florida, United States; a mailing address is available on request. Include enough information to help us understand the issue while avoiding unnecessary sensitive information.
Contact email: team@getbananaapps.com.