Skip to content

Question: is any design without "Access your data for sites in mail.google.com domains" permission possible? #702

@scscgit

Description

@scscgit

Hi, I'd like to ask anyone for their suggestions on a possible implementation without requiring the "Access your data for sites in mail.google.com domains" permission.

I understand that by design, it's practically impossible not to require this permission, due to the innate design flaw of all browser extension APIs. However, that still means we can never actually use this extension once we're no longer students, e.g. when we access sensitive work (or personal) e-mails. We'd need a thorough review of the source code after each update, before installing that update. Is there any plan to consider some kind of a workaround where the permission to basically read all our emails wouldn't be granted? I'm looking for any creative solutions. Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions