Publishing spreadsheets on Google Sheets exposes contributor emails through API requests. Can any document or account settings prevent these email addresses from being displayed?
Considering similar issues in previous projects, I found that the best approach involves managing the data before it’s exposed via the API. Unfortunately, Google Sheets doesn’t offer a built-in option to completely hide contributor emails when publishing a spreadsheet. I implemented a workaround where sensitive columns are removed using an intermediary script that processes the API’s output. This way, the published data remains useful without revealing any personal email details. Though this adds some extra steps, it effectively protects user privacy while making the information accessible.
i dont think theres a built-in setting to hide contributor emails. you might need to preprocess your data, filtering out emails before sharing. a custom script or api endpoint could do the trick if you really need to keep them private.
Based on my experience, Google Sheets does not provide a native way to hide contributor emails directly. I resolved a similar issue by separating the raw data from the public output. I maintained a master sheet with all details and then used a secondary, sanitized version for public API access. Although it requires initial setup and maintenance to ensure both sheets are in sync, this method successfully prevents exposing personal email details without compromising overall functionality.
hey, i tried movin data to a new file to avoid showin emails, works ok though its a bit extra. google sheets doesnt natively hide emails so filtering before publishing seems the best workaround atm.
In a situation where I needed to share data via the Sheets API without revealing personal email addresses, I ended up working around Google Sheets’ limitations by creating an additional layer of data processing. I set up a separate script that retrieves data from the official sheet, removes any sensitive columns including contributor emails, and then publishes the modified data. While this approach necessitates an extra processing step, it guarantees enhanced data privacy. This method gave me control over exactly what information gets exposed, and it worked seamlessly with our existing API setup.