Privacy Policy for GridCraft

Effective date and last updated: October 28, 2026

This policy explains how GridCraft: Photo Collage (also called GridCraft AI or GridCraft; Android package com.appsbracket.gridcraftai), provided by Ahsan Ijaz / AppsBracket, handles information. It covers the Android app and its caption service hosted at ahsanijazhere.com. No account or profile is required.

1. Photos, projects and information on your device

You choose photos using the Android system file picker. The app accesses the files you select rather than requesting access to your entire photo library. Selected files may come from device storage or a document/cloud provider that you choose; that provider handles downloads under its own terms.

Collage layouts, photo positions, crop and zoom settings, text layers, colors, local effects, project timestamps and preferences are stored in private app storage. Drafts reference selected photos rather than creating a server photo library. Original photos must remain available for drafts to reopen correctly. Caption input, selected tone and recent generated captions are also saved locally so you can continue your work.

GridCraft does not upload your collage photos through its caption service. Photo editing and collage rendering run on your device. Exported PNGs are saved to the location you select. If you later share a file, the receiving app or service handles that copy.

2. AI caption requests

When you choose to generate AI captions, your typed description and selected tone are sent over HTTPS to our caption server, which forwards them to the xAI API to create caption and hashtag suggestions. The caption service does not send your selected photos to xAI. Avoid entering passwords, financial details, health information or other information you do not want processed by an external AI provider.

Our caption controllers process descriptions and responses to fulfill the request; they do not intentionally save them in a server caption-history database or write them to application logs. Your device stores the recent results. xAI processes and may retain API inputs and outputs under the terms, data-processing arrangements and settings applicable to our API account. We do not promise zero retention by xAI. See xAI's Data Processing Addendum and API data-handling information.

AI suggestions can be inaccurate or inappropriate. Review them before copying, posting or sharing. You can use collage editing without submitting a caption request.

Caption requests and generated text are checked in separate safety-classification calls to the same xAI API before results are displayed. Content flagged as unsafe is withheld; unavailable checks stop the request. These model-based checks can make mistakes and do not guarantee that every harmful result is detected.

Reporting a caption

The Report caption action lets you choose a reason and submit a report without leaving the app. Submission sends the selected caption, its hashtags, a server-issued reporting receipt and the reason to our server for developer safety review. It does not include your original description or photo. Our server also receives your IP address and stores a keyed hash for abuse limits. Do not submit unnecessary personal information.

Reports are stored privately for safety review. They become eligible for removal after 30 days and are removed when a later report submission is processed; if the reporting service is inactive, stored reports may remain longer. Hosting backups and security logs may retain copies separately. Contact us to request earlier deletion where applicable. Reporting receipts expire after 30 days. We review reports to improve safeguards; submission does not guarantee a particular review time or automatic removal of other copies.

3. App verification and abuse prevention

Public caption requests use Google Play Integrity to check the app, its Play installation/licensing status and device integrity. Google processes information needed to generate these signals under its policies. Our server receives the integrity token and decoded verdict, together with the request information needed to verify that the token belongs to the submitted request.

The app creates a random installation identifier for caption usage limits, and each request includes a one-time request identifier. Our server also receives your network IP address when you connect. Private usage counters store keyed hashes of the installation identifier and IP address, request/token hashes, counts and timestamps to limit abuse, prevent replay and control service costs. These keyed identifiers are pseudonymous, not a guarantee of anonymity or a permanent personal identity.

Daily installation and network counters reset at the next UTC-day rollover when another request is processed. Replay records are pruned after approximately five minutes during later requests. Records may remain in the private ledger while the service is inactive. Aggregate lifetime usage counts remain for spending controls. Hosting/security logs and backups may separately contain network addresses, request paths, timestamps and error information under the hosting provider's retention arrangements.

4. Advertising and third-party services

The app uses Google AdMob for banner, interstitial and rewarded ads. The Google Mobile Ads SDK collects and shares information such as IP addresses, advertising or app/device identifiers, ad interactions and diagnostic information for ad delivery, measurement and fraud prevention. IP addresses may be used to estimate approximate location; the app does not request GPS location permission. Advertising personalization and available privacy choices depend on region, consent requirements, device settings and the ad service's configuration.

Rewarded ads are optional and can unlock creation of an additional project, subject to the project limit, or one extra caption generation after the daily caption allowance is exhausted. Caption rewards are limited to two extra generations per installation per UTC day, expire at UTC midnight and remain subject to service spending and availability limits. Closing an ad without earning its reward does not grant a caption credit.

For caption rewards, our server issues a random, short-lived reward ticket. The app passes this ticket to AdMob as custom data; it does not include your prompt, photo, name or raw installation identifier. Google sends a signed reward event to our server containing the ticket, ad-unit and reward information, a transaction identifier and timestamp. We verify this event before granting credit and store the ticket with a keyed installation identifier, issue date, grant status and transaction hash to prevent duplicate rewards. Reward records are retained for approximately 48 hours and pruned during subsequent caption-service requests; they may remain longer while the service is inactive or in hosting backups.

We use Google's User Messaging Platform (UMP) to request advertising privacy choices where required. Before initializing or requesting ads, the app checks UMP's advertising eligibility. Where applicable, you can revisit the form through Settings > Ad privacy choices. The option appears when UMP requires it for your region or configuration. If privacy setup cannot be resolved and UMP does not allow ad requests, ads remain unavailable; collage editing remains available. Changing choices does not remove records already held by independent providers, and declining personalization does not necessarily remove all advertising.

Existing photo editing does not require sending photos to advertisers through our caption backend. Advertising SDKs communicate independently with their providers. For callback troubleshooting, we keep one overwritten private diagnostic record with a check time, validation result, field lengths and match flags, without the full callback URL, signature, reward ticket, user identifier or transaction value. Hosting access logs may separately record request URLs under the hosting provider's logging arrangements.

We do not sell your photo projects or caption descriptions. Information is disclosed to the service providers described here to operate captions, advertising, hosting and security. These providers may process information in countries other than your own. We may also disclose information where required by law or reasonably necessary to protect the service and its users.

5. Permissions and Android backup

The app uses internet access and network-state access for online services and connection checks. Its advertising SDK declares advertising-ID access. The app does not request camera, microphone, contacts, SMS, precise location or broad photo/storage runtime permissions. Access to selected documents and export locations is granted through the system picker.

Android backup/device transfer is enabled for eligible app data. Depending on your device, settings and backup provider, local preferences, project records or caption history may be backed up or transferred. The installation identifier and private debug-test credentials are kept outside Android app backup. A restored project may still require access to its original photos. Control device backups through Android's settings.

6. Retention, deletion and your choices

For access, correction or deletion requests concerning information we hold, email the contact below. Describe the request and approximate dates; do not send API keys, passwords or identity documents unless separately and securely requested. We will explain any proportionate verification needed, what information can be located and any security, legal or record-keeping reason that requires retention. We do not need you to create an app account. Rights vary with your location. Requests about independent Google or xAI records may also need to be directed to those providers.

Contact emails are used to respond to your request and may be retained as needed to handle the matter and meet legal obligations. We do not promise a fixed deletion period for hosting logs or provider data that is not governed by our app's local storage controls.

7. Security

We use HTTPS for the caption service, Android private app storage and server access controls. Provider API keys and service-account credentials are kept on the server rather than bundled in the public app. No storage or transmission method can be guaranteed completely secure.

8. Age eligibility

GridCraft is intended for adults aged 18 and over and is not directed to children or teenagers under 18. We do not knowingly seek personal information from anyone under 18. If you believe someone under 18 has provided personal information through our service, contact us so we can investigate and take appropriate action. This audience statement does not mean the app verifies every user's age. Eligibility for online AI services may also depend on applicable provider requirements and local law.

9. Policy changes

We may update this policy when the app or its data practices change. The revised policy will be posted at this URL with an updated date. Where required, we will provide additional notice or obtain consent for relevant changes.

10. Contact

Ahsan Ijaz / AppsBracket
Email: [email protected]
Website: ahsanijazhere.com