Export selected issue records
Exports the issue number, title, status, assignee, milestone, labels, and schedule fields for the records the user filtered and selected in the application.
Google OAuth Application
Pocket Exporter
Application purpose: Pocket Exporter lets authorized users export issue-tracking records they select and completed AI work results into a new Google spreadsheet owned by the Google account they authorize.
Pocket Exporter is a data-export utility for an issue-management application. It exports only the issue list or completed AI result that the user explicitly selects. The user chooses a Google account and grants access for every export.
APPLICATION FEATURES
What Pocket Exporter does
The application provides the following export features to authorized users of the issue-management system.
Export completed AI results
Exports only an AI schedule brief or work result that the user already generated and reviewed. Google user data is never used to train an AI model.
Create a new spreadsheet
Writes the selected data to a new file and applies headers, column widths, and table formatting. The authorized Google account owns and controls the resulting file.
HOW GOOGLE USER DATA IS USED
How Google user data is used
Data the application accesses
Pocket Exporter uses the short-lived OAuth access token authorized by the user, the new spreadsheet created for that export request, and that file's identifier.
Why the data is used
The data is used only to create the requested spreadsheet, write and format the selected records, and remove an incomplete app-created file if the export fails.
Data the application does not access
Pocket Exporter does not read existing spreadsheet content, the user's full Drive file list, Google profile, Gmail, or contacts.
Retention and user control
No refresh token is requested or stored. The encrypted access token is available for no more than 10 minutes and can be claimed only once. Users can revoke access at any time.
Pocket Exporter uses Google user data only to create, write, format, identify, and—if an export fails—delete the spreadsheet created by the user's current export request. It does not browse existing Drive files, read existing spreadsheets, or use Google user data for advertising, sale, profiling, or AI model training.
EXPORT WORKFLOW
How one export works
Authentication is separated from the business data being exported.
-
REQUEST
Pocket Exporter
The server validates the signed-in user, export permission, and selected issue records or completed AI result.
-
CONSENT
Google OAuth
The user selects a Google account and explicitly approves the Sheets and
drive.filepermissions. -
ONE TIME
OAuth Broker
The encrypted, short-lived access token is delivered once. No refresh token is requested or stored.
-
OWNERSHIP
User-owned spreadsheet
The main server writes validated data through Google APIs, and the authorized account owns the resulting file.
EXPLICIT BOUNDARIES
What Pocket Exporter does not do
Browse the user's Drive
The application does not request broad Drive access and cannot browse the user's complete file list.
Maintain long-term access
No refresh token is requested or stored. The user authorizes each export separately.
Advertising, sale, or AI training
Google user data is not used for advertising, sale, profiling, or AI model training.
Send business data to the OAuth Broker
The OAuth Broker never receives issue titles, assignees, labels, or AI result content.
POLICY DOCUMENTS