DILSE
Three things you are entitled to know before you put your work into someone else’s platform: what changed and when, who keeps order here, and what is kept about you. Back to DILSE
Newest first. Small fixes are left out; anything that changes what the platform does, or what it does with your data, is here.
Once DILSE’s Google settings are in place, the sign-in and sign-up pages offer “Continue with Google”. Google tells DILSE your name and the email address it has confirmed, and nothing else of your Google account. The first time, it signs you in to the account with that address, or makes you one with no password (you can set one later) and asks your age, as anyone is asked. If someone had made an account with your address without ever confirming it, its password stops working the moment you confirm the address with Google. Separately, DILSE can now send its email (codes, invitations, notices) from its own Google Workspace mailbox, encrypted on the way, with nothing installed to do it. Both stay switched off until the settings are added.
If you are in charge of an organisation on DILSE, you can now publish a course for it from DILSE Learn: what it is, what a learner can do after it, and its modules, each lesson with what it is (a video to watch, a reading, a question to reflect on). A person on the DILSE team checks that everything a learner needs is there, and never judges how it teaches; then it is in Explore for everyone, free. Signed in, Learn’s home is yours: the courses you are taking on DILSE and how far you have got, kept with your account, and the certificates you earn, each with its own number in your name that anyone can check on DILSE’s verification page. Organisations ask to join Learn’s Collective the same way. The team decides both from Learn’s desk in its console. Saathi can tell you what you are learning, and enrol you in a course on DILSE. The demonstration’s courses, cohorts and people are still there to explore, as before.
Signed in, what you share in these three apps is kept with your account on DILSE’s server, and a demo reset leaves it. A resource you share with the Library, as yourself or for an organisation you are in charge of, waits for a person on the DILSE team, who checks that everything is there and never judges what it argues; then it is in Browse and in Discovery’s answers, and its file can be downloaded or its link opened. A request to the India Impact Map’s steward is decided on the team’s desk, and an approved pin is on everyone’s map. A moment on Realising India is photographs only for now: each is redrawn before it leaves your device, and again as it is kept, so where your camera says it was taken is never stored; a person looks at every photograph before the moment is on the map. My Moments and the Library’s list of what you shared say where each stands, and you hear under From DILSE either way. Anyone can report a moment, and a report that someone is at risk is read first. The team decides all of this from desks in its console, where its role is checked on every decision; the apps’ own admin views now say they run the demonstration. Exploring without an account is unchanged.
Signed in, Saathi no longer speaks as the demonstration’s person, Ravindra, and there is no switch between people: it speaks to you by name and answers from your own work on DILSE, what the DILSE team wrote to you, the records offered to you and your applications on My Records, the answers to your listings on DILSE Youth and your tools on the Registry, and your posts in the Collective. “Start my day” is built from those. It does not answer from MyWork or DILSE Learn yet, and says so. What you ask it to remember, your conversations and the record of what it did for you are kept with your account, read only by you, in the copy of your data you can download, and gone with your account. Signing out clears it from that browser. On your WhatsApp line it answers the same way.
On your account page, “Confirm with WhatsApp” opens WhatsApp with a short code already written, addressed to DILSE. Send it, and the number you sent it from is confirmed for your account: nobody else could have sent it. Nothing waits for a code to arrive, and nothing costs anyone. That number is then your line to DILSE: write to DILSE on WhatsApp from it, and Saathi answers for you, as it does on the web. You are told under From DILSE whenever a number is confirmed this way, and taking it off your account ends the line.
On your account page you can now check your name, and whether you are 18 or older, against the QR on your Aadhaar card, e-Aadhaar or mAadhaar. You choose a photo or a screenshot; it is read in your own browser and never sent. Only the number the QR holds reaches DILSE, which checks UIDAI’s digital signature on it and compares the name with yours. DILSE keeps that it was checked, whether the name matched, whether you are 18 or older, and the date, never your Aadhaar number, photograph, address or date of birth. Your DILSE ID then shows your name as checked by Aadhaar, and your age on DILSE follows your Aadhaar’s. A parent or guardian saying yes for someone under 18 can show they are an adult the same way. DILSE’s sample QR shows how it works, and checks nobody.
Until now DILSE ID, your profile and the home page showed the demonstration’s person, Ravindra Singh, even to someone signed in. Now, signed in, DILSE ID is yours: made from your account the first time you open it, kept on DILSE’s server, and the same in any browser you sign in on. What you write about yourself, which app may read which part, who may see what, and the record of every read are kept there. A field is marked verified only where DILSE knows it: your email or number once a code proved it, your DILSE ID’s number, the organisation you belong to on DILSE, and the records organisations issued you. Your profile shows you, with your own Collective posts and your own record; the home greets you by your name; every app that reads DILSE ID reads you. If you are in charge of an organisation, you keep its DILSE ID with its other admins, and its team is everyone in it on DILSE. Exploring without an account is unchanged: the demonstration’s person, kept in your tab.
Everyone with an account can now bring people onto DILSE, and whoever joins through you is shown as brought by you. You have a card of your own: your name, your organisation, a line in your own words and a QR code of your link, to share as a picture in a WhatsApp group or status, or to print for a meeting. You can invite people by name, and set up their place with what you know (their organisation, their role, a note), so they check it and join in one step. You can make an open link for a group or an event, with an end date and a limit, and close it any time. If you are in charge of an organisation, the same links bring your colleagues into it. Nothing is ever sent unless you press send: the message opens in your own WhatsApp or mail, in words you can change. What you write about someone is seen only by the two of you, and is deleted when they join, say no, or after 30 days. Anyone invited can say it is not them, or ask never to be invited again, and then nobody can invite them. Your account page has the way in, under Bring people to DILSE.
DILSE used to ask you to be 18 or over to take part in DILSE Youth. Now there is no minimum age anywhere: a school student is as welcome as anyone, to explore and to join. DILSE asks once, when you make your account, whether you are 18 or older. If you are under 18, a parent or guardian says yes before you apply, sign up, message an organisation or post, as India’s data protection rules ask; you ask them from your account page and they answer through a link of their own, which also lets them take the yes back. Exploring and reading never need it. Organisations see your name and what you send, never your email or phone, and anything a young person reports is read first by the DILSE team.
The DILSE team’s look at every fundraising ask is a check that it is complete and keeps DILSE’s rules, nothing more. Nobody on the team decides whether a project is good or right: funders do. So an ask is published once everything it needs is there, sent back when something is missing, and declined only for breaking a rule, which its owner is told by name and can reply to. The checks that weighed how much an ask was for are gone. The same holds for a young team’s ask in DILSE Youth.
The DILSE team can now write to a group of people at once: everyone with an account, the people in charge of organisations, those in one state, or the team. Only the super admin sends one, and sees how many it reaches before sending it. You get it under From DILSE as a conversation of your own, and can reply; replies are read by the super admin and support. Nothing is emailed while DILSE has no mail sender connected: the email that says a message is waiting stays in the outbox. What people have told DILSE on each app’s “Why this exists” page, and under an answer, is now read by the super admin and support, in one place; a name or an address is there only where someone chose to give it. Every conversation that waits for the team, beyond requests for help, is now in one list for them, so a reply does not wait unseen.
Until now everything in the Registry belonged to the demonstration, a tool went on the shelf the moment it was listed, and nobody answered a request for access. Signed in, the Registry is now real. An organisation active on DILSE, or a person as themselves, lists a tool or posts a need, and a person on the DILSE team reads it first: is the builder real, does the link work, is the access claim true (an open-source claim names a licence), is it already listed. Asking a builder for their tool, for a hosted copy, or a question goes to the builder and nobody else; they grant it with how to get it, or decline and say why. Supporting a need says you need it too, and a pledge is a promise of money towards building it: nobody is charged. Once a week, when the team opens its desk, DILSE’s own server checks that each real tool’s link still works; nothing you do makes it follow a link. What people search for is kept without who searched, so the team can see what the sector looks for and cannot find; DILSE counts no views. The team can feature a tool, say one is no longer kept up and why, say what it checked about a builder, and nudge builders who leave people waiting two weeks. MyWork is now an organisation’s choice: its person in charge can switch it off in the Registry, and it leaves the organisation’s home. In DILSE Learn, a course sent for review and an organisation asking to join are now decided on the server, so a decision is kept. Not done yet: Learn’s courses and people are still the demonstration’s.
Until now everything in DILSE Youth belonged to the demonstration, a young person’s challenge appeared in the bank the moment it was written, and nothing anyone reported reached a person. Signed in, DILSE Youth is now yours, for real. Taking part asks one thing first: that you are 18 or over, by your own word, since DILSE cannot prove anyone’s age; anyone younger can explore the demonstration, where nothing is kept. Organisations active on DILSE post opportunities, challenges and events, and can ask to be listed as an incubator; anyone signed in can post a challenge or host an event. What young people read is read first when it should be: a challenge or an event a person posts always waits for a person on the DILSE team, and so do an organisation’s first three listings and anything that asks young people for money, for their ID or bank details, or to take things private. What you send goes to whoever posted the listing and nobody else; they move it on or close it with a word, and the two of you can write to each other. The DILSE team reads a message only when one of you reports it, and then that message alone; if the report needs more, someone who may decide reports can open the conversation from the report, and must write down why, which is kept in the team’s log. A report that a young person may be at risk, or is being abused, is read before anything else. An organisation that leaves young people waiting two weeks without a word is reminded. A young team’s ask for money is now read twice: first by the Youth review (has an incubator said yes, does the money add up, has a guardian consented for anyone under 18), and only then by DILSE Capital’s. In the demonstration, every listing, organisation and conversation can be reported, what its people post waits as it would for real, and its organisations no longer carry a check mark, because nobody checked them. Not done yet: funding asks and incubators are real only in the demonstration, and a guardian’s consent is not yet a signature.
Until now every record in My Records belonged to the demonstration, and nothing could withdraw one: /verify checked that a reference existed, not whether it still stood. Now an organisation active on DILSE can issue a real record to a person, by the email address they use here. It waits for them, and joins their record only when they accept it; nobody can put their own work on their own record. Anyone can check a record at /verify, which says who vouched for it and what the DILSE team has checked about them. The person a record names, or the organisation that issued it, can ask the DILSE team to withdraw it, and anyone can report one from its page. A withdrawn record is not deleted: /verify says it was withdrawn, when and under which rule, and both sides are told. An organisation that issues carelessly can have its right to issue suspended. In MyWork a finished milestone now asks the lead to sign it off, instead of going out in the lead’s name; in DILSE Youth an event you only say you attended goes on your record as self-reported. Organisations can post real openings, which are live at once unless they ask applicants for money or for their ID or bank details: then a person on the team reads them first. Applying sends a note and records from your own, each checked, so a record that is not yours never reads as yours; the organisation moves your application on, or says no with a word, and you can write to each other. If your account is removed, a record that named you stays with its organisation without your name, and /verify says the person has left DILSE. Not done yet: DILSE cannot prove an email address until a mail sender is connected, so a record’s name is the issuer’s word; and nobody can yet be found by their record.
Until now everyone in the Collective was the demonstration’s practitioner, and nothing anyone wrote was kept. Signed in, you now take part as yourself: your questions, polls, answers, replies, votes, poll answers, saves, event registrations and reflections are kept on the server and everyone sees them, on the demonstration’s own threads too, which are marked Demonstration so you know the people in them are made up. Signed out, you can still explore as the practitioner, for your visit alone. A question, an answer or a reply is up the moment you write it. A survey or an event that sends people to another site waits until someone on the DILSE team has looked at where its link goes, usually within two working days; you see where it stands, and hear under From DILSE. A survey can now be built in the Collective itself: its questions are answered in place, and whoever ran it reads what came back as counts and words, never names. Answers, replies, surveys, events and reflections can now be reported and hidden, not only questions and polls, and a link in an answer that hides where it goes is put in front of a person by the platform itself. The team speaks in its own voice, with a badge, without naming who wrote it; it can pin up to three posts, lock a thread with a reason you can read, mark the official answer, fold a repeated question into the first, put up a banner, and make, rename and archive Spaces with guidelines for each. Asking anonymously stays anonymous from the team too: a step about something asked anonymously is taken without the team being shown who asked. The team reads how alive the Collective is from what people did, never from what anyone looked at, and may ask someone who has answered questions like it to look at one nobody has answered. You can delete what you wrote, and a question takes its thread with it. Saathi posts a question or registers you for an event the same way: as you when you are signed in, for your visit when you are not. Not done yet: posting does not need a confirmed email address, because DILSE cannot send a code yet.
In DILSE Capital an ask used to go live the moment it was published, its documents were ticks with no file behind them, and a funder’s name was whatever they typed. Now every ask, from an organisation, an incubator, a project shared from MyWork or a young team’s pitch, goes to the DILSE team first, with its baseline and need assessment attached as real files. A person there reads it, usually within two working days, and approves it, sends it back with notes, or declines it and says why; you see where it stands on your dashboard and hear under From DILSE. A live ask can be paused, frozen, closed or taken down, and whoever committed to it is told. A funder’s name appears on a commitment only once the team has checked it. A tranche that is stuck can be brought to the team, which reads both sides and answers both; DILSE holds no money and moves none. An organisation that is active on DILSE now acts in Capital as itself, and shows funders what the team has checked about it, by name. Asks, updates and questions in Capital can be reported.
A report used to be read and nothing more. The DILSE team can now decide one: do nothing, and say why; hide the thing, which leaves it where it is and says in its place that it was hidden and under which rule; or take a step about whoever posted it. The steps are one ladder for every app: a word, which is not counted; a warning; posting paused for seven days; a suspension of thirty days; and a block until it is lifted, which only the super admin can give. A strike stops counting after twelve months, and an organisation’s strikes are its own. Whoever a step is about is told in a notice under From DILSE, a new page that holds everything the team writes to you: what happened, the rule, who decided, and until when. Replying to a notice is an appeal, and it is decided by someone who did not make the first decision; the server will not let the same person decide both. A blocked account can still sign in to read its notice, download its data and appeal. While posting is held, the post buttons on the home and in the Collective say why and until when, and the server refuses the post. There are two more rules than before: nothing that puts a person at risk, and nothing false or misleading in a record, a funding ask, an opening or a listing. There is also a Help page: anyone can ask the team something, with or without an account, and a signed-in person can download what DILSE keeps about their account at any time and ask for it to be corrected or removed, which is answered within thirty days. Your account page and your DILSE ID now show where you stand. What is not done yet: hiding works for questions and polls in the Collective only, and a Report control is on the Collective’s feed only; each other app gets both with its own admin view. The people in the ten apps are still the demonstration’s, so a step can be taken about a real account or organisation, and not yet about a seeded practitioner.
The DILSE team can now invite an organisation: it names the organisation, its person in charge, and an email address or a phone number. That makes a profile for the organisation that is not active and not public, and a link, good for thirty days, that belongs to the person in charge alone. When they open it, confirm their details and choose a password, the organisation is active. Nobody approves it. If you are invited and do nothing, DILSE holds only what the team typed, and the team can take the invitation back. The verified badge has also begun. It is not one tick: it says what was checked, by whom and when. An email address and a phone number are each confirmed by a code; an organisation’s NGO DARPAN, 12A, 80G, CSR-1 and FCRA numbers are each looked up in the public register by a person on the DILSE team, never by the platform itself. DILSE has no mail sender connected and cannot send a code to a phone yet, so for now the team passes an invitation on themselves and a contact cannot be confirmed for real; both are built and open when they are connected. Checking a government ID is not built. You can give your account a phone number, and a super admin can now remove an account for good when its owner asks.
Reports you send from the Collective were written down, and until now there was no screen where the team could read them. There is now an admin console for the DILSE team. It shows what is waiting for a person across the platform: requests to the India Impact Map’s steward, flagged resources in the Shared Library, flagged moments in Realising India, courses and member requests in DILSE Learn, and the reports members have sent, oldest first, with the two working days counted against each. Only a signed-in member of the team sees reports, and the server checks their role on every request. The team sees how many accounts exist; the super admin can read the log of sign-ins and password changes, and the super admin and support can read the mail DILSE has sent or is holding, with any code left out. In the demonstration anyone can look around as the team, and is shown the demonstration’s own data only: no account, no email address, and no report a real person sent. Acting on a report from the console (hiding a post, a warning, a strike) is not built yet, and the other five apps do not have an admin view yet.
Until now everyone explored DILSE as the same demonstration person. You can now create an account of your own, with your email and a password, and sign in to it; nobody has to approve it. It is real and kept on the server, apart from the demonstration data: your name, your email, your password as a hash, the browsers you are signed in on, and a log of sign-ins and password changes. You can change your name and password, see where you are signed in, and sign other browsers out. DILSE has no mail sender connected yet, so it cannot send a code to confirm your address or reset a forgotten password by email; both are built and open when mail is connected. The apps themselves still run on demonstration data and do not read your account yet.
The Collective shows your name and your work from your DILSE ID. It also uses what you work on (your themes, SDGs and places) to suggest Spaces when you set up your view and on the Spaces page, and to put posts about your work first under “For your work”. A Space is suggested only when your own words name it. Each read is on your activity list. Switch The Collective off in DILSE ID and it reads nothing, and says so.
Saathi’s rounds (asking the team whether they are free, proposing a call, asking which organisations publish on a topic) now belong to your visit. So does whatever your organisation’s agent proposes to you. Nobody else sees them, answers them, or gets them on WhatsApp. What you allow your agent to do lasts for your visit, and so does the record of what it did. Anything an agent does for you happens in your own browser, where your apps are, and never on the server’s shared copy.
Everyone exploring DILSE is the same demonstration person, and Saathi used to keep what it remembered under that person — so the next visitor could meet the last one’s conversation. What Saathi keeps now belongs to your visit alone: filed under your tab’s visit, read back only by it, and cleared with “Clear this browser”.
The control room and Prayogshala are now the DILSE team’s own space: everyone else sees them read-only and controls only their own agent. The team is a persona any visitor can switch to, and what is done as the team lasts for that visit only — nobody else sees it, and nothing is written to the server.
The ecosystem agent no longer writes to organisations on its own each week. It proposes plans in the control room, and Prayogshala proposes project briefs. When the DILSE team approves one, every organisation it names is told, and they answer together in one discussion: in, not sure, not interested, or a change they would make. Once at least half are in, the team launches it as a draft project in the lead organisation’s MyWork. In the demo, answers from organisations other than yours are samples, and are labelled as samples.
Shared Library, MyWork, My Records, the India Impact Map, Realising India, the Digital Tools Registry and DILSE Youth asked your DILSE ID for who you are and never used it. Each now shows it in one place — your name in its header, your organisation on a moment you share, your name in a request — and each read is on your activity list. Switch an app off in Data control and it shows its own default, and says it is not connected.
Across the apps, what you do — posts, votes, messages, applications, commitments, records — is kept in your own tab for the length of your visit. It survives a reload and a trip between apps, and is gone when you close the tab. It is no longer written to a server where the next person would find it, or left in the browser for whoever uses it next.
A record issued during a visit is no longer written to the server. Anyone can still check the records DILSE was set up with, at /verify; a record issued in your visit checks in that visit’s tab, and nowhere else.
A young person’s funding ask in DILSE Youth reaches funders in DILSE Capital, and what a funder commits there comes back to it. A project in MyWork can be shared to DILSE Capital as a funding proposal, and a funder there can ask for its financial disclosure, which your organisation grants or declines. All of it lasts for your visit.
Every record issued on DILSE now resolves at a public address — hand the reference to a funder and they can see who issued it, to whom and when, without an account. A record addressed to you also waits for you to accept it before it joins your record or becomes checkable.
When an app reads something from your DILSE ID, it is written down. Data control now shows how many times each app has read you and when it last did, and the activity list names the fields.
Your profile now shows what happened after you contributed: views of your photographs, answers to your questions. Counted where it happened, and seen only by you.
Everyone exploring DILSE arrives as the same demonstration person, in shared data. The home screen now says so on the first visit, and points at the page where you can erase everything you have done.
Saathi now answers with the role, place and focus areas you have shared, and forms in Capital and Learn fill your details from your identity instead of asking again. Revoke an app in Data control and it stops — the app says plainly that it is no longer connected.
Learn, Youth, the Tools Registry and My Records used to lose what you had done as soon as the page reloaded. They now remember, in your browser.
A finished milestone in MyWork can be added to your record. A project can open Capital’s fundraising with itself named. A Library resource can start a discussion in the Collective with the resource already in it.
Buttons that do nothing yet — publishing an instrument, broadcasting to backers, the map’s geospatial layers — now say Planned rather than Coming soon in five different wordings.
The Collective allows questions to be asked anonymously, because the most useful question in this sector is often the one a person cannot put their name to — a funder relationship going wrong, a programme that is not working. Anonymity without visible moderation is how such a room turns, so here is the rest of it.
The same rules in every app. A report names one of them, and so does any decision.
A person, not a model. Reports from every app go to one desk, where the DILSE team reads them in the order they arrive and aims to act within two working days. Something that puts a person at risk — an identifiable beneficiary, a photograph without consent, a young person in danger — is read first, and taken down first and discussed afterwards.
In DILSE Capital nothing reaches funders unchecked. Every fundraising ask, whoever it comes from (an organisation, an incubator, a project shared from MyWork, a young team’s pitch), is checked by a person on the DILSE team before any funder sees it, usually within two working days. The check is that everything the ask needs is there and that it keeps DILSE’s rules. Nobody on the team judges whether a project is good or right: that is for funders. So an ask is published once it is complete, sent back when something it needs is missing, and declined only for breaking a rule, which its owner is told by name. Whoever sent it is told under From DILSE and can reply. The platform points out what it notices, such as wording copied from another ask, money asked for outside DILSE, or a document said to be attached that is not. It decides nothing: a person does.
An ask that is live can be paused, frozen while something is looked into, closed, or taken down. Its owner is told why and can appeal; whoever committed to it or asked about it is told what happened. A funder’s name is not shown on a commitment or a question until the team has checked it, so nobody can pose as a known funder. And DILSE holds no money: a commitment is a recorded promise, paid by the funder to the organisation directly.
In the Collective, a question, a poll, an answer and a reply are up the moment they are written; the DILSE team meets them only if someone reports them. A survey or an event that sends people to another site waits until someone on the team has looked at where its link goes, usually within two working days, because once someone has followed a link nothing on DILSE can take it back. The team reads the address, and can have DILSE’s own server follow it, to public sites only, to see where it really ends. A survey built in the Collective has no link, so it is up at once. And where an answer carries a link that hides where it goes, such as a shortened link or a name dressed up as a known one, the platform puts it in front of a person by itself: nothing is held back, and nobody is accused.
In My Records an opening is live the moment an organisation posts it, unless the platform notices it asking the people applying for money (a fee, a deposit, a charge for a kit) or for their ID or bank details: then it waits for a person on the DILSE team, because no opening on DILSE may ask for those. One changed after it went live into something like that waits again. The team can pause a live opening, take it down or close it, and whoever applied is told.
In DILSE Youth what young people read is read first, whenever it should be. A challenge or an event that a person posts always waits for a person on the DILSE team, and so do an organisation’s first three listings, an incubator asking to be listed, and anything that asks young people for money, for their ID or bank details, or to take things private (to meet alone, to message privately, to send photographs). A listing changed after it went live waits again whenever a new one would. A young team’s ask for money is checked twice: first by the Youth review (has an incubator said yes to the team, does the money add up, has a guardian consented for anyone under 18), and only then by DILSE Capital’s, before any funder sees it. Neither judges the idea.
In the Digital Tools Registry every tool listed, and every need posted, is read by a person on the DILSE team before organisations see it: is the builder real, does the link work, is the access claim true (an open-source claim names a licence anyone can read), is it already listed. A need much like one already on the wishlist is folded into it, so the support behind both is in one place. A change to a listing that is live is read again. Once a week, when a person on the team opens the Registry’s desk, DILSE’s own server follows each real tool’s link, a few steps at most and to public sites only, to see that it still works; nothing a member or a visitor does makes it follow a link.
In DILSE Learn, a course an organisation publishes is checked by a person on the DILSE team before it is in Explore: every module has its lessons, and every lesson has what it says it is (a video that can be watched, a reading that is there, a question to reflect on). Nobody judges how it teaches, and it is declined only under a rule it breaks. Courses are free to learners. Signed in, what you learn is kept with your account, and finishing a course earns a certificate with its own number, in your name, which anyone can check on DILSE without an account. An organisation asking to join Learn’s Collective is decided the same way, and the decision is kept.
A resource shared with the Shared Library waits for a person on the DILSE team, who checks that everything is there: what it is and who it is for, its file or its link, and that whoever shares it said it is theirs to share or openly licensed. As with a funding ask, nobody judges what it argues, and it is declined only under a rule it breaks, which the decline names. A request to the India Impact Map’s steward (a pin for your work, a correction, data the map lacks) is decided by someone on the team who may decide what is published, never by the person who sent it; an approved pin is on everyone’s map.
A moment shared on Realising India waits until a person on the team has looked at every photograph in it: who is in it, whether a child can be identified, whether a home could be found from it. Before a photograph leaves your device it is drawn again, and DILSE draws it again as it is kept, so what a camera writes into a photograph, where it was taken above all, is never stored. Anyone can report a moment; a report that someone is at risk is read first, and the moment can be taken off the map at once and discussed afterwards.
DILSE has no minimum age. Anyone can explore everything and make an account. DILSE asks once whether you are 18 or older, and takes your word for it. If you are under 18, then before you apply, sign up, send an idea, message an organisation or post, a parent or guardian says yes, as India’s data protection rules ask. You ask them from your account page; they get a link of their own, read what DILSE is and what the yes lets you do, and answer. They can take the yes back the same way, and you are told each time under From DILSE. Organisations see your name and what you send, never your email or phone, and anything a young person reports is read first.
What you send (an application, a sign-up, an idea, a pitch) goes to whoever posted the listing, with your name, and nobody else reads it. What the two of you write to each other is yours and theirs. The DILSE team reads a message only when one of you reports it, and then that message alone. If the report needs more, someone on the team who may decide reports can open the conversation it is in, from the report and nowhere else, and has to write down why: every opening is kept in the team’s log with that reason, and shown to whoever opens it next. An organisation cannot close what you sent without saying something to you, and one that leaves young people waiting two weeks without a word is reminded.
A report that a young person may be at risk, or is being abused, is read before anything else. If anyone is in danger, call 112 first; for anyone under 18, Childline is 1098, day and night.
A record on DILSE is an organisation’s word about a person’s work. Only the person in charge of an organisation active on DILSE can issue one, and it joins a person’s record only when they accept it: until then it proves nothing about anyone. Nobody can put their own work on their own record, and in MyWork a milestone reaches a record only when the lead signs it off. What a young person only says they did is marked self-reported, everywhere it is read. Anyone can check a record at /verify, which says who vouched for it and what the DILSE team has checked about them.
A record can be withdrawn, and that is what makes it worth something. The person it names can ask the DILSE team to withdraw it (“I never did this”, “the details are wrong”, “it is not mine”), and so can the organisation that issued it; anyone can report one from its page at /verify. A person on the team reads the record and the reason and decides. A withdrawn record is not deleted: /verify says it was withdrawn, when, and under which rule, and both sides are told. An organisation that issues carelessly can have its right to issue suspended, with the reason.
A thing can be hidden. It is never deleted: its place says that the DILSE team hid it and under which rule, and it can be put back. And a step can be taken about whoever posted it. The steps are a ladder, the same in every app:
A strike stops counting 12 months after it was given. An organisation’s strikes are its own, apart from those of anyone in it. The ladder is what usually comes next; the person deciding may choose another step when the case calls for it, and says why. A block is decided by the super admin alone.
In the Collective the team can speak as itself. A post or an answer marked DILSE team was written by the super admin or a moderator, and says so; which of them wrote it is not shown, and is kept in the team’s own log. The team can pin up to three posts to the feed or to a Space, lock a thread (it stays readable, and says why), mark one answer as the official one, fold a question asked again into the first one so that the answers are in one place, and put up a one-line banner that leads only to a page on DILSE. It makes, renames and archives Spaces, and writes how each one is kept. Each of these shows where you see it, and each can be undone.
You are told, in a notice under From DILSE: what happened, the rule it fell under, who decided, and until when. Reply to it and that reply is an appeal: a second person, who was not part of the first decision, looks again and tells you what they found. If they withdraw the decision it no longer counts, and anything hidden because of it is put back. Even a blocked account can still sign in, to read the notice, download what DILSE keeps about it, and appeal. Your account page and your DILSE ID show where you stand and every step ever taken, and nothing is decided silently.
A Report control asks which rule the thing breaks and takes one line of context. Every question, poll, answer, reply, survey, event and reflection in the Collective carries one today, and so do an ask, an organisation’s update and a funder’s question in DILSE Capital, a record (from its page at /verify) and an opening in My Records, every listing, organisation and message in DILSE Youth, and every tool, need, comment and message in the Digital Tools Registry; each other app gets its own as its admin view is built. Who sent a report is never told to whoever it is about, and the desk is shown only whether it came from a member or a visitor. Asking anonymously stays anonymous from the team too: when a step is taken about something asked anonymously, the team decides without being shown who asked it, and the step is kept on that person’s file without saying which post it was about. In the Collective you can also hide everything from one person for yourself alone, which needs no report and tells them nothing. For anything else, ask the DILSE team.
Nobody approves you. An account is yours the moment you make it, and an organisation the DILSE team invites is active the moment its person in charge sets a password. The verified badge is separate, and earned.
It is not one tick. It names what was checked, by whom and when, so you can judge for yourself. An email address or a phone number is confirmed by a code that came back. An organisation’s NGO DARPAN, 12A, 80G, CSR-1 and FCRA numbers are each looked up in the public register by a person on the DILSE team; the platform never marks one checked by itself. A check is of one number: change it, and the check no longer stands until the new one has been looked up. DILSE does not check a government ID yet, and this page will say when it can.
The ten apps are still a demonstration, and the honest version of that is worth stating plainly: everyone who opens them arrives as the same person, in the same starting data, and what you do there is kept for your visit — in your own tab, not on a server with your name on it. One thing is now real: an account, if you choose to create one.
Something here not true to what you found? That is a bug, and worth telling us about — every page carries a way to say so. Check a record · Back to DILSE