TAS · Team Akshay Sharma
Last updated 25 September 2026 · Effective 25 September 2026
TAS is a private, invitation-only application used by the campaign team of Akshay Sharma to organise its own workers. It is not a consumer product: there is no public sign-up, and an account exists only because someone already on the team created it.
This policy explains what the application stores, who can see it, what the Android and iOS applications ask your phone for, and — in detail — exactly which Facebook and Instagram data it reads and what it does with it.
The application is operated on behalf of the campaign team by Humble Solutions, which acts as the data controller for the information described here. Questions, corrections and deletion requests all go to the address in section 12.
Because the application exists to organise a team, it holds records about the people on that team. Depending on the role, a record may include name, father's name, contact number, email address, date of birth, gender, the area or booth a person is responsible for, their voter identification number, a photograph taken at the doorstep, the names and numbers of the adults in their household, and who registered them. It also holds notes and records created by the team in the course of its own work, such as meeting summaries and event details.
These records are visible only to that person and to the people above them in the team structure. This is enforced on the server, not merely hidden in the interface.
Not everyone in the application is a user of it. The most junior role, Booth Member, has no password and no way to sign in. Such a person is a record — someone a team leader has canvassed and can contact — not an account holder. If that is you, the deletion route in section 9 still applies: ask the person who registered you, or write to us directly.
Every permission below is requested at the moment the feature is used, never on launch, and every one of them can be refused without losing access to the application.
| Permission | Why it is asked for | If you refuse |
|---|---|---|
| Camera | To take a photograph of a member at the time they are registered. The photograph is stored with that member's record. | The registration form saves without a photograph. |
| Location | To record where a registration was taken, so that booth visits can be planned from real doorsteps. A single point is captured when you tap the button; the application does not track you and does not run in the background. | The registration form saves without a location. |
| Microphone | The meeting recorder, and only when you press Record. The recording is saved first in the application's private storage on your phone and is then uploaded to the campaign's own Google Cloud storage when there is a connection. While a recording runs it carries on with the screen locked, and the phone shows that it is recording; it stops by itself after 1 hour 30 minutes. It is used only to produce a transcript and a written summary of the meeting for the team's leadership: the campaign's administrators, and the leaders above the person who recorded it. Every time one of them listens to a recording, reads its transcript or downloads either, it is logged. The phone's copy is deleted three days after the server confirms it has received all of it. | The recorder cannot be used. Nothing else is affected. |
| Notifications | To tell you when you have been invited to an event, and when an update has been assigned to you. | No notifications arrive. The application works normally. |
| Photo library | Only when you choose an existing photograph instead of taking one. | You can still take a photograph with the camera. |
The application also stores a device notification token against your record so that a notification can be delivered to your handset. It is removed when the token stops working or when your record is deleted. The application does not contain advertising, does not contain third-party analytics or tracking software, and does not use any advertising identifier.
This is the most sensitive information the system holds. To let a team leader register a voter without typing their details twice, the application holds rows imported from the published electoral roll for the constituency it works in: name, father's name, age, gender, house number, address, part and serial number, and voter identification number.
That data is published by the Election Commission of India and is used here only to identify and enrol members of the team. It is visible only to team leaders who register people, and only for the ward they themselves work in — enforced on the server. It is never sold, never shared, never used to contact anyone automatically, and never used for any purpose other than filling in a registration a leader is already making in person.
Where the roll is held on the phone so that a leader can work in a booth with no signal, it is stored in the application's own private storage, which other applications on the device cannot read, and is removed when the application is uninstalled.
The application reads one Facebook Page and one Instagram Business account: our own. No person using the application ever signs in to Facebook or Instagram, and the application never asks for access to anyone else's account, profile, friends, followers or messages.
A team member pastes a link to one of our own published posts. The application finds that post on our own account, reads its caption, and uses it to draft a short comment suggestion for each team member so that the comments left under our post are varied and relevant rather than a hundred copies of the same four words.
| Source | Fields read |
|---|---|
| Our Instagram Business account | id, caption, media_type, media_url,
thumbnail_url, permalink, timestamp of our own recent media |
| Our Facebook Page | id, message, full_picture,
permalink_url, created_time, attachments.media_type
of our own recent posts |
| Account lookup | The Page's id and name, and the linked Instagram account's
id and username |
The Meta access token is stored as a server-side secret in Google Cloud Secret Manager and is used only by our backend. It is never sent to a phone or a browser, never written to a database record, and never written to a log line. Error text returned by Meta is logged privately and is not passed back to the application, because it can contain the app id and the token's trailing characters.
When a post is shared to the team, the application stores the post's id, its caption, its permalink and the URL of its preview image alongside the update, together with the drafted comment suggestions. Nothing else from Meta is retained.
Information is not sold, rented, or shared with advertisers, data brokers or any other third party.
Team-member records are held to run the team and are created by agreement when someone joins it. Electoral roll data is public information published by the Election Commission of India and is used only for the enrolment purpose described in section 4. The Facebook and Instagram data is our own organisation's published content, read with our own credentials and our own consent.
Team records are kept while the team is operating and are removed on request. A meeting recording stays on the phone that made it until the server has received all of it, and for three days after that as a safety copy; on the server, recordings and the summaries made from them are kept while the team is operating and are removed on request. Posts shared to the team, and the comment suggestions drafted from them, are removed when the update itself is deleted. Server logs are retained for a short period for security and debugging and do not contain Meta tokens.
A deletion request submitted through the form described in section 9 is itself kept for up to twelve months after it is acted on, as the record that the request was made and honoured, and is then removed.
Anyone whose details are held in the application may ask for them to be corrected or deleted. There are two ways to do it, and both reach the same people:
We will confirm the request and act on it within 30 days. Deleting an account removes the sign-in credential and the personal record — name, contact details, photograph, date of birth, voter identification number, household contacts and recorded location. Records the team's own work depends on, such as who registered whom, are retained in a form that no longer names you where we are required to keep them; anything not required is deleted outright.
Because no third party's Facebook or Instagram account is ever connected to the application, there is no Meta account data belonging to anyone else for us to delete. To have our own account's post data removed from the application, delete the update inside the application or write to us.
Access requires an account created by the team. Data is transmitted over HTTPS and stored by Google Cloud with encryption at rest. Server-side rules decide what each account may read and write; credentials for Meta, Anthropic, OpenAI and ElevenLabs are held as server-side secrets and are never exposed to the client. Meeting recordings are uploaded over links that each allow one file to be written, only for fifteen minutes, and cannot be used to read anything.
The application is for members of the campaign team and is not directed at children. We do not knowingly create records for anyone under 18.
Write to executives@humblesolutions.in for any question about this policy, or to correct or delete information held about you.
If this policy changes, the date at the top of this page changes with it and the current version is always the one published here.