Privacy Policy

PDF Tools - Offline — Mobile App Privacy Addendum This Privacy Addendum details the specific data handling, storage, offline processing, and advertising practices for the mobile application PDF Tools - Offline (package name: com.effocess.pdftools.offline), developed by Skilltitute. 1. Local & Offline Processing PDF Tools - Offline operates as an entirely local, on-device utility tool. All PDF operations—including viewing, merging, splitting, compressing, extracting, and editing PDF files—are executed strictly offline on your mobile device. Your PDF documents, text, images, and file contents remain isolated on your local storage and are NEVER uploaded, transmitted, or saved to Skilltitute servers or any third-party cloud infrastructure. 2. Information Collection and Storage Skilltitute does not collect, store, sell, or track any personal information, user documents, file metadata, or account details from users of PDF Tools - Offline (com.effocess.pdftools.offline). No user registration or login account is required to use the application. 3. Advertising & Third-Party Service Providers (Google AdMob) PDF Tools - Offline uses Google AdMob (Google Mobile Ads SDK) to serve advertisements within the app. While Skilltitute does not collect personal data, Google AdMob may collect and process pseudonymous device data, including: - Advertising Identifiers (such as Google Advertising ID / GAID) - Device IP Address & Network Connection Type - General App Performance & Crash Logs - Coarse Location Data (for ad geographic targeting) AdMob uses this data to deliver relevant ads, prevent ad fraud, perform ad analytics, and manage ad frequency. For details on how Google handles advertising data, please review Google's Privacy Policy at https://policies.google.com/privacy. You can manage your ad preferences or opt out of personalized advertising at any time through your Android device settings (Settings > Google > Ads). 4. Device Permissions PDF Tools - Offline requests storage and file access permissions (such as READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, or MANAGE_EXTERNAL_STORAGE where applicable) strictly for the purpose of enabling you to browse, edit, merge, compress, and save PDF files on your device. These permissions are used exclusively for user-directed file operations on your local device storage. 5. Data Security Because all PDF processing occurs locally on your device without network transmission, your files and sensitive documents are naturally protected from network interception and external server breaches. 6. Contact Information & Data Rights If you have questions regarding this Privacy Addendum or the privacy practices of PDF Tools - Offline (com.effocess.pdftools.offline), please contact us at contact@skilltitute.in.

FlowGen Automator — Chrome Extension Privacy Addendum This Privacy Addendum details the specific data handling, storage, authentication, and processing practices for the FlowGen Automator Chrome extension ("FlowGen Automator"), developed by Skilltitute. 1. Information Accessed and Stored FlowGen Automator accesses and/or stores the following user data to provide its core functionality: - Google Account Information: Email address, display name, and profile photo URL. - Firebase Account Identifiers: Firebase User ID (UID), Firebase ID token, and Firebase refresh token. - User Inputs & Generation Assets: Text prompts, reference image data, and required Google Flow project identifiers. - Account Quotas & Subscriptions: Generation usage counters (usedGenerations, remainingGenerations) and subscription status (isPro). - Extension Configuration & State: Extension settings (flowGen_settings), local batch history (flowGen_history), active batch state (flowGen_batch_state), and API configuration (flowApiConfig). 2. Google Account Authentication & Token Storage FlowGen Automator uses chrome.identity.getAuthToken() to obtain a temporary Google OAuth access token. This temporary Google OAuth access token is used strictly in-memory during sign-in and is NOT persisted in local storage or stored in flowgen_auth_user. The temporary OAuth token is exchanged via Firebase Identity Toolkit to authenticate the user and establish a Firebase session. The resulting user identity data stored in Chrome local extension storage (chrome.storage.local) includes: - Firebase UID - Email address - Display name - Profile photo URL - Firebase ID token - Firebase refresh token Note: Firebase ID tokens and refresh tokens are distinct authentication tokens generated by Firebase Identity Toolkit and are not the temporary Google OAuth access token. 3. Google Flow / Google AI Services Processing When you initiate an image generation batch, user-supplied text prompts, reference image data, and required Google Flow project identifiers are transmitted directly to Google Flow / Google AI infrastructure via service endpoints such as aisandbox-pa.googleapis.com to execute the requested generation. 4. Generated Image Files Generated images are rendered on Google Cloud infrastructure and downloaded directly from Google infrastructure/CDN to your local device. FlowGen Automator does not upload or store generated images on Skilltitute servers. 5. Firebase & Google Cloud Infrastructure FlowGen Automator relies on Google Cloud and Firebase infrastructure for authentication, subscription tracking, and remote configuration: - Authentication: Token exchange via Firebase Identity Toolkit. - Quotas & Subscriptions: Firestore maintains quota records under quotas/{uid}, tracking fields including usedGenerations, remainingGenerations, and isPro. - Configuration: API configuration parameters are fetched from config_private/default. 6. Local Storage Usage FlowGen Automator uses Chrome extension storage APIs to save state locally on your device: - chrome.storage.local contains: • flowgen_auth_user (User profile data, Firebase UID, email, display name, photo URL, Firebase ID token, and Firebase refresh token) • flowGen_settings (User preferences and extension options) • flowGen_history (Local generation history, capped at approximately 100 batches / 4 MB) • flowGen_batch_state (Active batch engine execution state) - chrome.storage.session contains: • flowApiConfig (Session-level API configuration settings) 7. Raw CSV and Text Source Files Raw CSV or TXT source files selected by the user remain locally on the user's device. FlowGen Automator processes the contents of these files locally on your machine. Prompt text and reference image data derived from source files for batch execution are transmitted to Google Flow / Google AI endpoints as required to perform image generation. 8. Explicit Third-Party Recipients FlowGen Automator transmits user data only to specified third-party service infrastructures essential for core functionality: - Google Identity Services: Receives authentication requests to verify Google user accounts. - Google Flow / Google AI Services: Receives prompts, reference images, and project identifiers to process image generation requests. - Google Cloud / Firebase: Processes authentication exchanges, retrieves extension configuration, and tracks user quota records in Firestore. FlowGen Automator does not share user data with unspecified or generic third parties. 9. Skilltitute Application Servers FlowGen Automator does not send user prompts, reference images, generated images, or authentication credentials to Skilltitute application servers. Skilltitute does not collect, view, or retain user content processed by FlowGen Automator. 10. Analytics, Advertising, and Data Sales Specifically for FlowGen Automator: - No third-party analytics services are used. - No advertising networks receive FlowGen user data. - FlowGen user data is NEVER sold, rented, or traded. - FlowGen user data is NOT used for advertising, marketing, or data brokerage. 11. Data Retention Data retention practices distinguish between local storage, remote quota records, and provider infrastructure: - Local Storage: Data stored in chrome.storage.local remains on your device until you sign out, clear batch history, clear browser extension storage, or remove the extension. (Note: Uninstalling the extension does not automatically erase remote Firebase quota records). - Firebase Quota Records: Account quota and subscription data (quotas/{uid}) are stored remotely in Firestore. - Google Infrastructure: Processing and retention of data submitted to Google Flow / Google AI services are governed by Google's applicable terms of service and privacy policies. 12. User Data Controls & Deletion Rights Users have full control over local and remote extension data: - Local Sign-Out & Clearing: You can sign out, clear local batch history, or purge extension storage via extension and browser settings. - Remote Quota Data Deletion: Users can request deletion of FlowGen-related remote quota data stored in Firebase by contacting contact@skilltitute.in. Note: Requesting deletion of remote quota records or clearing local data does not automatically delete provider-side data stored on Google infrastructure. 13. Provider-Side Practices Provider-side processing (such as server-side retention periods, internal system logs, human content review, or model training by Google) is governed strictly by applicable Google service policies and terms of service. Skilltitute makes no independent claims regarding provider-side internal operations. 14. Chrome Web Store Limited Use Disclosure FlowGen Automator's use and transfer of information received from Google APIs to any other app will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. User data accessed by FlowGen Automator is used exclusively to provide and improve the extension's user-facing features. FlowGen Automator does not sell, rent, or transfer user data to third parties for advertising or unrelated purposes.