Pullhub is provided by debutt studio. Contact: support@debutt.studio.
What Pullhub does
Pullhub is a visual reference collection and Google Slides productivity tool. It helps users collect visual references, organize them into local boards, capture screenshots, export backups, share boards when enabled, and push selected images into Google Slides.
Pullhub only accesses webpage content after explicit user actions such as Save to Pullhub, Screenshot/Capture, Push to Google Slides, or export workflows. Otherwise, Pullhub does not continuously inspect, collect, or analyze webpage content in the background, or monitor browsing history, visited websites, browser sessions, or background traffic, except when necessary for explicit user-initiated Pullhub features.
Google data Pullhub may access
When a user connects Google, Pullhub may access the Google account email address, a profile image if Google returns one, and OAuth access tokens. The email and profile image show the connected account and support optional sharing ownership. OAuth tokens authorize only the Google functionality requested by the user.
For Slides workflows, Pullhub may access the presentation ID, current slide ID, presentation and slide structure, page dimensions, slide titles, and related Slides response data needed to identify a target slide and arrange content. Pullhub uses this information to read the structure of the active presentation, identify the current or chosen target slide, insert images, create slides, position elements, and add source hyperlinks.
Pullhub detects the Google Slides presentation currently open in the user's active browser tab. It reads the presentation ID and current slide ID from that tab's Google Slides URL. Google Picker is not currently used. Detecting an open tab does not itself cause Pullhub to access or modify the presentation: Google API access and changes occur only after an explicit user action such as Push to Slides or another user-triggered Slides operation.
For Drive fallback, Pullhub may access the identifier of the Pullhub-created Pullhub Uploads folder and Pullhub-created fallback image files. Pullhub accesses the raw Google data categories described above only as needed for requested features. The current production extension contains no analytics system and does not create, transmit, or use aggregated or anonymized Google user data for analytics.
Other data Pullhub may process
Website content. Pullhub may access image URLs, page URLs, selected page areas, screenshots, and related page metadata only when the user explicitly saves, captures, or pushes references through Pullhub.
Browser storage. Pullhub stores boards, saved references, notes, settings, and workflow state in browser storage.
How information is used
Information is used only to provide Pullhub features: saving boards, showing saved references, creating backups, sharing boards, authenticating Google access, pushing images to Google Slides, and managing subscription access.
Where information is stored
Pullhub follows a local-first storage model. Boards are primarily stored locally in the browser using Chrome extension storage. Cloud storage is used only when users intentionally enable Public Share or use supported Google integration features. If board sharing is used, shared-board data may be stored in Firebase/Firestore. Images pushed to Google Slides may be uploaded to Google Drive when required so Google Slides can access them.
OAuth tokens and sign-out
OAuth access tokens may be cached temporarily in extension local storage, in memory, or in Chrome Identity's token cache. Pullhub uses these tokens only for requested Google functionality. Pullhub sign-out revokes available OAuth tokens and clears locally stored connected-account email, profile image, and token state. Sign-out does not delete local boards, Drive fallback files, Firebase Authentication records, or Firestore sharing records. Users may also revoke Pullhub's Google access from their Google Account.
Google Drive image fallback
When an image cannot be inserted directly into Google Slides, Pullhub may upload that specific image to the user's own Google Drive. The drive.file permission is used only for Pullhub-created fallback image files and the Pullhub-created folder named Pullhub Uploads. Pullhub does not intentionally browse unrelated Drive files.
A fallback image may be made readable by anyone with its link solely so Google Slides can retrieve and insert it. Pullhub does not automatically delete fallback images. They remain in the user's Drive until the user deletes them or another authorized deletion process removes them. Users can manage or delete these files from the Pullhub Uploads folder in Google Drive.
Google OAuth scopes
The Google presentations scope is used to read presentation structure and perform user-requested Slides changes. The drive.file scope is used for Pullhub-created fallback files and the Pullhub Uploads folder. The userinfo.email scope is used to show the signed-in Google account and support account state and optional Firebase sharing ownership.
Public Share
Public Share is optional. When enabled, Pullhub stores a snapshot of the board in Firebase/Firestore. The snapshot can contain the board name and color, item URLs, source-page URLs, notes, media types, captured image data where applicable, ownership identifiers, and timestamps.
Disabling Public Share makes the Firestore record non-public but does not necessarily hard-delete the Firestore document. Deleting a local board does not guarantee automatic deletion of every associated Firebase Authentication or Firestore record. Uninstalling Pullhub removes extension-local data through the browser, but cannot automatically clean up remote Google Drive or Firebase data.
Third-party services
Pullhub uses Google APIs for account, Slides, and Drive functionality; Firebase Authentication and Firestore for optional Public Share; and ExtensionPay/Stripe for subscription management. Pullhub does not claim or rely on ExtensionPay or Stripe receiving Google user data. Google user data is not transferred to unrelated third parties for advertising, data brokerage, lending, or AI/ML model training.
Google API Limited Use
Pullhub's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Pullhub also handles extension data in accordance with the Chrome Web Store User Data Policy.
Prohibited uses of Google user data
Pullhub does not sell Google user data; use it for targeted or personalized advertising; transfer it to data brokers; use it for creditworthiness or lending decisions; use it to develop, improve, or train generalized AI or machine-learning models; or transfer it to third-party services for AI or machine-learning model training.
Human access to Google user data is limited to situations necessary to provide support, investigate security or abuse, comply with law, or process a verified deletion request. Any such access must be limited to the minimum information necessary for that purpose.
Security
Pullhub uses HTTPS for Google and Firebase network requests, and OAuth tokens are used for authorized API access. Firestore access is intended to be controlled through authentication, ownership, and each record's public or non-public status. Locally stored information is protected within the browser extension storage environment. No method of storage or transmission is completely secure, and Pullhub does not guarantee absolute security.
Retention and deletion
Local boards, references, and settings remain until the user changes or removes them, clears extension data, or uninstalls Pullhub. Connected-account and token state is cleared during Pullhub sign-out as described above. Drive fallback files remain until the user deletes them from Google Drive.
Non-public Firestore sharing records and Firebase Authentication records may remain after sign-out, local board deletion, or uninstall until a verified deletion request is processed. Users may request deletion of Firebase Authentication and owner-associated Firestore sharing data by emailing support@debutt.studio. After account ownership is verified, Pullhub will manually delete Firebase account and sharing data that it can identify as belonging to the verified requester. This process does not delete unrelated records or files.
Drive fallback files remain under the user's control and should be deleted by the user from the Pullhub Uploads folder in Google Drive. Local extension data can be removed by deleting boards, clearing extension data, or uninstalling the extension. Revoking Google access or signing out does not by itself delete these local or remote items.
Changes
We may update this policy as Pullhub changes. Material changes will be reflected on this page.