Brikal
This notice explains how Brikal handles information when you transform everyday photos into digital artwork on your device. It is written for the photo studio experience you actually use: selecting images, applying curated looks, adjusting tones, and saving or sharing finished pieces.
Brikal is a lightweight iOS application for turning photographs into styled digital art. You browse curated looks, open a photo from your library or camera, edit with studio tools such as portrait-focused treatment, colorful frames, background swaps, and tonal adjustments, then save or share the result.
This Creative Data Stewardship Notice describes the kinds of information that may arise from those flows, why that information exists, and the boundaries we set around it. It applies to the Brikal mobile application and related in-app legal pages presented through the app.
Brikal does not require you to create a user profile, sign in, or maintain credentials before you explore styles or open the editor. You may use the core creative tools without an account-based identity inside the app.
Because there is no mandatory account layer, Brikal does not operate a central user directory for names, passwords, or profile pages. Preferences and creations described below are handled as on-device materials tied to your installation, not as a remote membership record.
Depending on how you use Brikal, the following categories of information may be involved. We describe them by how they appear in the product, rather than as abstract categories alone.
When you choose a photo from the library or capture a new frame with the camera, Brikal accesses that media so you can apply styles, segment subject and background where available, place frames, replace backgrounds with templates or another album image, and tune exposure, contrast, vibrance, temperature, vignette, and related adjustments. Those images are used to render your edit session.
If you save a creation, Brikal may write the finished image into the on-device history shelf and, when you allow it, into the Photos library. History entries exist so you can revisit earlier looks on the same device.
Brikal may store lightweight flags such as whether onboarding has been completed and which style identifiers you marked as favorites. These values help the home, styles, and more areas feel continuous between launches.
Where permitted by the operating system and your choices, Brikal may receive limited cross-app measurement signals connected to which art styles you open, how often you edit, and which studio tools you complete. Those patterns help refine the style rail, polish editing flows, and shape features that make transforming photos into art clearer. Such signals are not a substitute for a personal biography and are subject to platform controls described below.
The app may rely on ordinary device and system interfaces (such as storage paths, permission states, and app version metadata) that are necessary for local file handling, presenting system dialogs, and displaying accurate about information.
iOS may ask you to allow specific capabilities. Brikal requests them only in connection with the related feature:
Declining a permission typically limits the matching feature while leaving other parts of the studio available. You can revisit permissions in iOS Settings for Brikal.
Editing is oriented around on-device presentation: filters, frames, segmentation views, background templates, and tonal controls operate so you can preview and finalize artwork within the app session. Brikal uses the media you provide for that creative purpose and for optional save or share actions you initiate.
Sharing hands content to the destination you select through the system share sheet. Once material leaves Brikal for another app or service you choose, that destination applies its own practices. Brikal does not control how those third destinations store or further transmit what you send.
We do not treat your photo library as a remote archive managed by Brikal staff. Studio history and preference values described here are designed as local materials for your installation.
Typical local materials may include:
Clearing history items inside the app, removing favorites, or uninstalling Brikal will remove corresponding local materials according to how the operating system handles app data. Photos already exported to the system Photos library remain under your library management unless you delete them there.
Brikal is primarily an on-device creative tool. Network activity may still occur when the operating system or embedded views retrieve content you open (for example, legal documents loaded in an in-app browser view), when platform commerce frameworks communicate with Apple services as part of ordinary app commerce infrastructure, or when measurement frameworks operate subject to your tracking choice.
Transmission that does occur is expected to use the secure channels provided by iOS and the relevant platform frameworks. Absolute immunity from interception or failure cannot be promised; we aim for careful, conventional protections consistent with a mobile creative utility.
Brikal relies on Apple platform components (such as photo pickers, camera interfaces, share sheet, permission dialogs, and StoreKit-related system services) and may present remote documents through a web view. Those components process information under Apple policies and your device settings.
If you grant tracking-related permission, measurement partners or platform advertising frameworks associated with that permission may receive the limited style and editing pattern signals described earlier. If you deny tracking, Brikal respects the platform restriction for that pathway.
We do not sell your photo library as a commercial list. When information must be disclosed to comply with applicable laws, respond to lawful process, or protect the integrity and safety of the app and its users, we may do so to the extent reasonably required.
Because Brikal does not run a mandatory remote account, many privacy actions are completed through device controls and in-app history tools rather than through a web profile portal.
On-device history and preference values generally remain for as long as they are useful to your studio session or until you delete them or uninstall the app. Photos saved to the system library follow the retention rules of your Photos app.
Limited measurement or diagnostic signals, where collected under platform rules, are retained only as long as needed for the improvement purposes described above or as required by applicable laws and platform obligations, then discarded or aggregated in the ordinary course of operations.
We apply reasonable administrative and technical measures appropriate to a mobile photo editor: sandbox storage for app materials, reliance on iOS permission gates, and careful handling of media within the editing pipeline. No method of electronic storage or transmission is free from all risk. You should keep your device passcode and operating system updates current as part of protecting local creative files.
Brikal is intended for a general audience and is not directed at children seeking to create remote profiles. We do not knowingly solicit personal contact details from children through an account signup flow, because such a flow is not part of the product. If you believe a child has provided personal information to us in a manner inconsistent with applicable child-protection requirements, contact jovett@brikalstudio.com so we can review and take appropriate steps.
As Brikal evolves, we may revise this notice to reflect new studio tools, permission needs, or legal requirements. The updated text will be made available through the app or the same distribution channel used for this document. Continued use after an update means you have had an opportunity to review the revised notice.
Questions about this Creative Data Stewardship Notice, device permissions, or how Brikal handles studio materials may be sent to:
We will review inquiries in a reasonable time and respond through the same email channel when a reply is appropriate.