Chronological digest
What arrived, what was sent, what changed and what is still waiting—ordered by date and source.
GAS AI Private Secretary · free core
GAS is being repositioned as a free-core private secretary for the digital world. With your explicit approval for each linked platform, it can bring selected incoming and outgoing information together, let you ask for different kinds of summaries and help you understand what matters without opening ten separate apps.
Your accounts remain yours: every source has its own permission, purpose and revoke control. The core secretary is intended to be free; streaming, software, dropshipping and other outside providers may still charge their own fees.
One secretary · many authorised sources
GAS is the private consolidation and explanation layer between your connected information, your goals and the outside organisations that may be able to help. A sign-in is not permission to read an email account, social account or messaging app; each connection must be separately approved, narrowly scoped and revocable.
Link an authorised email, social, messaging, calendar, file or streaming source one at a time. GAS requests the smallest useful permission.
Incoming and outgoing items are organised into a user-controlled timeline, people view, project view or topic view with source labels and dates.
Choose a chronological digest, decisions, action list, unread priorities, travel brief, financial-admin view or plain-English overview.
Only after a separate recommendation permission does ENQSI compare likely fits and explain why. It can surface a possibility; it cannot know a need with certainty.
ENQSI boundary: the system may notice patterns and surface a useful possibility before a user has articulated it, but it must show the evidence, uncertainty and reason for the suggestion. “You may find this useful” is honest; “we know exactly what you need” is not.
One source · many useful views
The value is not just collecting messages. It is turning a noisy digital life into the particular brief you need at that moment.
What arrived, what was sent, what changed and what is still waiting—ordered by date and source.
Agreements, promised follow-ups, approvals and unresolved choices, with links back to the originating source.
What you need to do, what someone else needs to do, deadlines, reminders and items that need clarification.
A focused summary for an event, trip, household issue or conversation without reading unrelated material into the result.
Potential patterns and unanswered questions, clearly marked as inferences rather than facts.
With permission to use your selected streaming-service information, GAS can help find something you may love—even from a service you had not considered.
Platform-by-platform permission
GAS will never treat “link my platforms” as one blanket permission. Each provider decides what an authorised application may read or write, which reviews are required and whether personal-history access is available at all.
Use official OAuth and least-privileged scopes. Gmail restricted scopes can require Google verification and a security assessment if the data is stored or transmitted. Outlook access requires the relevant Microsoft Graph permissions.
Gmail scopes ↗Use the platform’s own consent screen and only the fields the user approved. Meta describes permissions as granular, app-user-granted authorisation; a social login does not equal access to private posts, messages or contacts.
Meta permissions ↗Business messaging APIs may support specific business conversations and outbound templates, but GAS must not promise access to a personal chat history where the platform does not offer an authorised connector. Sending always needs a separate action approval.
WhatsApp Business API ↗Movie discovery can use a user-selected service list, catalogues or official availability data. GAS must not request a streaming password, pretend that every service exposes viewing history or guarantee that a title is available in the user’s country.
Availability and watch history remain provider-dependent.Current deployment: this page defines the target architecture. It does not yet connect to every mailbox, social account, messaging app or streaming service, and it does not claim to consolidate a user’s private history today.
Confidentiality by design
The profile should be a private preference layer for the user’s chosen purpose—not a data-broker product. A profile can help GAS remember goals, geography, budget bands, accessibility preferences and business context, but the minimum useful information should be collected and retained. Connected source content should be indexed for the user’s requested purpose, not turned into an invisible dossier.
Review profile and connection controlsAffiliate income and legal readiness
If a user separately permits recommendations, GAS may identify software, dropshipping, fulfilment or other products that fit the user’s expressed or authorised goals. This is a jurisdiction-aware operating baseline, not legal or tax advice. Exact obligations depend on the user’s location, GAS’s entity and contracts, the product category, the marketing channel and the partner’s rules. Qualified local legal and tax review is required before live affiliate matching.
Affiliate, sponsored and paid recommendations must be recognisable as advertising. GAS must not hide a commission relationship, present a paid recommendation as independent editorial content or use a label that an ordinary user is unlikely to understand.
Read ACCC social-media promotions ↗‘Best’, ‘cheapest’, ‘fastest’, ‘most secure’ and similar claims need reasonable grounds and current evidence. GAS will use ‘best fit we identified for your stated goal’ unless a broader claim can actually be substantiated.
Read ACCC advertising and promotions ↗GAS must keep records of commissions and other referral income, include assessable business income as required, handle foreign-currency and platform statements, and obtain tax advice about timing, deductions, withholding and cross-border treatment.
Read ATO assessable income ↗GAS must monitor GST turnover and register when required. The GST treatment of a particular referral or cross-border commission is not automatic; the entity, supply, customer, contract and payment flow must be reviewed.
Read business.gov.au GST registration ↗Where the Privacy Act applies, GAS must follow the Australian Privacy Principles, explain collection and use, minimise information, protect it, support access and correction, and provide practical direct-marketing opt-out controls. Sensitive information must not be used for marketing without the required consent.
Read OAIC Australian Privacy Principles ↗Commercial email and SMS generally require consent, sender identification and a working unsubscribe method. GAS must keep evidence of consent and honour unsubscribe requests within the applicable timeframe; a partner or agent sending for GAS does not remove GAS’s responsibility.
Read ACMA avoid sending spam ↗For US-facing recommendations, a material connection such as commission must be disclosed in a way users can notice and understand before the recommendation influences their decision. The disclosure must not be buried behind a link or contradicted by the surrounding copy.
Read US FTC Endorsement Guides ↗UK affiliate content may fall under the CAP Code and should be obviously identifiable as an ad. UK and European privacy rules can also govern profiling, cookies, personalised marketing, objections and consent, especially where tracking or behavioural data is used.
Read ASA affiliate-marketing guidance ↗Ordinary affiliate approval does not automatically permit GAS to resell, white-label, bundle, set the provider’s price, provide first-line support or charge users for the underlying service. Those rights need a separate commercial agreement and clear customer terms.
Read PartnerStack affiliate programme ↗Virtual CEO decision
“This is the most compelling expression of GAS so far. People do not want another isolated tool; they want help making sense of the digital life they already have. A free core private secretary gives GAS a daily reason to be useful, while the recommendation layer creates a responsible path to software and dropshipping revenue.”
My decision is to make the Private Secretary the core architecture and PartnerStack an important early opportunity channel. I support ENQSI finding patterns and surfacing possibilities, but not pretending to read every service, predict a person perfectly or act on their behalf without a separate approval.
The practical next step
Start with source-specific consent and read-only consolidation; add the summary views; then add recommendations; only later consider drafting or sending messages under a separate action approval. The first production milestone needs official connectors, least-privileged scopes, privacy and security review, retention/deletion controls, jurisdiction rules, approved links, income reconciliation and a visible “why this recommendation?” record.