Privacy
Privacy Policy
Prepared 13 October 2026. Last updated 13 October 2026. Draft for company and legal review.
Draft for company and legal review. This is not the final policy.
Who operates Fliqa Spot
Fliqa Spot is operated by FliqaIndia Pvt. Ltd. Questions about this draft can be sent to support@fliqaindia.com.
This page describes the app behaviour reviewed in the Fliqa Spot source. It is a draft for company and legal review. It is not a final privacy policy.
Accounts
You can browse published locations as a guest. An account is required to save locations, create collections, keep shoot plans, receive in-app notices, or submit a location suggestion.
Account sign-in uses Firebase Authentication. The account-deletion path in the app runs only for an authenticated Firebase session, and an email account must enter the current password before that path continues.
Profile information
A signed-in profile can hold a display name, full name, bio, email, home city, preferred city, interests, preferred language, and notification preferences. Empty fields stay empty until the account sets them.
Location
Nearby discovery can request location while the app is open. The permission text says: “Fliqa Spot uses your location while the app is open to find nearby photography locations. It does not track you in the background.”
Search can also use a city, region, or radius you choose. Choosing a city in search is not the same as granting device location.
Saved places and shoot plans
Saved locations and custom collections are stored for the signed-in account. Shoot plans can include saved spots and notes. Guests do not have these records.
Suggestions and photos
A signed-in person can prepare a location suggestion, including photos. Guests cannot submit. The app states that a draft saved on the account is not public. This draft does not claim that a suggestion is published automatically.
Notices
Signed-in accounts have an in-app notices list. This draft does not claim that push notifications are sent to the phone, because that delivery was not confirmed for this page.
Analytics and error monitoring
The mobile analytics client is created with consent turned off. This page does not claim that analytics events are collected.
The API can start Sentry error monitoring only when a DSN is configured. Without a DSN, that monitoring stays disabled. When it is configured, the code shown for it turns off user information, cookies, request headers, request bodies, and query parameters. This website does not state whether a production DSN is currently set.
Where information is stored
Account profiles, saved collections, shoot plans, notices, and catalogue records are stored through the Fliqa Spot backend and its database. This corporate website does not read that user database.
A support or account-deletion form on this website, when storage is connected, is saved in the corporate FliqaIndia website database. That record is a request. It is not a copy of the app account and it does not delete the app account.
Sharing
Published location pages are visible to people using the app, including guests. Draft suggestions are not described as public.
Firebase Authentication processes sign-in. If Sentry is configured, it processes the limited error data described above. Map tiles can be requested from Google when a maps key is configured in the app. This page does not list other processors, because none were confirmed for this draft.
Deletion
Inside the app, Profile → Privacy → Delete account asks you to type DELETE MY ACCOUNT and confirm again. An email account also asks for the current password. The API then removes the Firebase sign-in for that same user and marks the profile, collections, shoot plans, and in-app notices with a deletion time. Published catalogue locations are not removed with the account.
The public form at /spots/delete-account records a review request for support@fliqaindia.com to handle. Submitting an email on that form does not delete the Fliqa Spot account. No retention period beyond that app process is stated here, because the source reviewed for this draft does not publish one.
Security and your requests
Sign-in deletion checks that the Firebase session belongs to the same user and, for email accounts, that the current password matches. This website does not collect that password.
To ask a question about this draft, email support@fliqaindia.com. Access, correction, and deletion requests that need a decision from the company can use that address or the forms on the support and account-deletion pages. A form confirms success only after the corporate site stores the request.
Status of this draft
Draft for company and legal review. The date prepared for review is 13 October 2026. It should not be treated as approved until the company publishes a final version.
